Context Circuit
Workflows

Create plans

Ground a plan in real code after intent approval or a direct planning request.

Template 2.5.0CLI 2.5.0

Investigate real code

Planning starts on a request for it: a request to plan an approved intent, which may arrive with the approval, or a direct request to plan an already specified outcome. Approval alone does not start it. The agent then reads relevant code, repository instructions, and setup requirements. It chooses useful plan boundaries, tasks, dependencies, risks, and checks. A planner or narrow explorers may help; the coordinator writes the records.

sh .context-circuit/cli record create --kind plan --slug invoice-api --title "Invoice download API" --intent i001 --repo api
sh .context-circuit/cli record create --kind plan --slug invoice-web --title "Invoice download UI" --intent i001 --repo web --depends-on p0001
sh .context-circuit/cli record order --intent i001 --mode waves

For a direct planning request, omit --intent. For an exact run, select its plans explicitly:

sh .context-circuit/cli record create --kind plan --slug specified-change --title "Specified change" --repo api
sh .context-circuit/cli record order --plan p0003 --mode waves

These IDs are illustrative; a member holding band 0 writes i001 and p0001, and band 1 writes i100 and p1000. Substitute the IDs returned in your workspace. The CLI creates each new plan as a folder with plan.md. Link any detail files from that entry and assign them to shared or repository-specific reading.

Present, then wait for execution

The plans explain what will be built and how it will be checked. Reading them is optional; there is no extra approval stage. A new request to execute, made after plans exist, starts implementation.

A dependency is an execution constraint, not a repository relationship. The CLI derives ordering and starting references; it does not execute the plans.

On this page