Audience guide

The CLI installs and verifies. The skills do the delivery work.

After cg init, day-to-day work is the /cg-* skills. The CLI does not plan or write product code. It inspects the same disk state the next session will trust.

Install Architecture

Lifecycle skills

Warmup for existing code. Plan or prototype for new work.

Those are the two starts. Both then share prepare → produce → sign-off. Unblock and auto-run sit beside that stack.

Existing code

/cg-warmup

Run first. Discover boundaries and write or extend their contracts, then continue with plan or prototype.

New repository

/cg-plan or /cg-prototype

Plan if the outcome is clear. Prototype if you still need to feel the experience.

  • /cg-warmupAdoption or additive reseed on existing code: discover boundaries, write or extend their contracts.
  • /cg-planTurn an outcome into ordered phases.
  • /cg-prototypeLaunch and refine a working prototype with your feedback, then prepare the accepted result for delivery.
  • /cg-prepareTurn one phase into a queue of steps.
  • /cg-produceRun the next ready step: code, tests, and contracts together.
  • /cg-sign-offFinish a selected prototype’s production work, or verify and close a delivery phase.
  • /cg-unblockRecord a fork so other work can continue.
  • /cg-auto-runOpt-in: Manager coordinates one Engineer per phase and asks unresolved decisions; never auto-runs warmup.

On disk

One contract per governed directory.

<unit>/.agents/cg/contract.yaml

The repository root owns .agents/cg/contract.yaml. Parent, dependency, and routing edges live in that node. Markdown projections are not a second source of truth.

cg verify cg modules cg graph show cg contract route --task "…" cg next cg status --programme <slug> cg residue

A, P, and E stay distinct. Structural A bindings fail cg verify. Product P rules bind only the contracts that list them. Engineering E guidelines are advice, not compliance. Architecture lists what each family actually requires.

Honest limits

Verify the graph you authored. Do not claim the source scan you do not have.

Built

Schema-backed contracts, task routing, brownfield discovery, the eight skills, and verification that the authored graph is connected.

Not claimed

That every implementation import matches the graph, that every exported symbol is declared, or that two work areas are safe to edit in parallel.

Day-to-day rule

A behaviour or structure change owns its implementation, tests, contract updates, and detectors in the same Step. Do not defer the graph to sign-off.

Lifecycle Public schemas