How it works

Two ways to use the Dev Kit.

Both modes use the same contract graph. Plan and deliver when the outcome is already understood. Explore through prototyping when you still need to see the experience. You review the working result. Sign-off completes what that acceptance left open.

Understood outcome

Plan and deliver.

Use this when you can already say what the work should achieve. /cg-plan agrees a sprint, or an epic made of several sprints. /cg-produce implements that scope. /cg-sign-off completes it. A sprint is one reviewable increment: the outcome, and what you will accept.

/cg-plan
/cg-produce
/cg-sign-off
  1. 01

    Plan

    /cg-plan agrees the goal, the acceptance criteria, and the scope. The agent locates the contracts the work will touch. Asking for a plan agrees that plan. Ask for the sprint or epic when you want it built.

  2. 02

    Produce

    /cg-produce builds the agreed scope and shows you a working result. Scope and review cadence are separate choices. The agent asks whether to review the selected work together, or to review each item. If either answer is missing, it collects those choices together, as separate selectable questions when the host supports them. Answers you already gave are reused. Agreed work that does not depend on an open decision can continue. A material decision that is still unresolved still needs you.

  3. 03

    Sign off

    After you accept the result, /cg-sign-off completes the outstanding implementation obligations, required tests, documentation, verification, and decision consolidation inside the authorized scope. Accepting what you tried is the review. Sign-off is the completion of what that review left open. It does not merge or publish the work.

Uncertain experience

Explore through prototyping.

Use this when you need to use the product to discover the result. /cg-prototype puts a working version in front of you. /cg-sign-off finishes the accepted scope. You do not need a complete implementation plan before the first preview.

/cg-prototype
/cg-sign-off
  1. 01

    Prototype

    /cg-prototype starts from the relevant contracts, launches the application, and changes it from your feedback. You say when the experience is right. Silence does not accept it. The agent can continue agreed changes that do not depend on an open decision.

  2. 02

    Sign off

    The same completion as plan and deliver. /cg-sign-off finishes outstanding implementation, required tests, documentation, verification, and decision consolidation for the accepted prototype. Liking the prototype leaves that work still to do.

Accepting a prototype records the experience you approved. Sign-off completes the remaining obligations in that scope. Merging or publishing stays your decision.

Your part

You decide the product. The agent carries the agreed work.

Inside a sprint, epic, or prototype you have already asked to complete, the agent can continue agreed work that stands on its own. Review, and any material decision the work cannot proceed without, still wait for you. Installation is npm install -g contract-graph and cg init. Then run /cg-warmup and confirm the project context before either path. Get started.