Prompt cookbook
What to say for the supported Context Circuit cases, in ordinary project language.
You do not need Context Circuit commands, record IDs, branch names, or internal vocabulary. Tell the coordinator the project outcome or decision in ordinary language. It chooses the matching procedure and runs the pinned CLI through the workspace's launcher for exact bookkeeping.
This cookbook covers the supported v2 conversation surface. The wording is illustrative: replace names, paths, repositories, branches, providers, and outcomes with your own.
Learn what you opened
Explain this workspace
PromptWhat is this project, which repositories belong to it, and what does the workspace already know?
The agent reads workspace identity, relationships, local bindings, and relevant knowledge. It explains the project without changing anything.
Show current work
PromptWhat changes are currently planned or in progress, and which repositories do they affect?
The agent resolves records and checks real branches and diffs before describing implementation state. status shows your own work first: intents awaiting approval, approved intents without plans, open plans, and finished records not yet archived.
Check workspace consistency
PromptCheck this Context Circuit workspace and explain every finding. Do not repair anything that needs my decision.
check is diagnostic. A finding names the command, edit, or human decision that discharges it.
Create or join a workspace
Create a new project workspace
PromptCreate a Context Circuit workspace for “Acme Billing.” Its purpose is subscription billing for small businesses. Add me as Maya.
Initialization happens only on request. Add your preferred language and writing tone if intents and plans should use them.
Every workspace has at least one member, and every member holds an allocation band, even when you work alone. The agent suggests band 1 for you; say so if you want another, or add roles such as maintainer or docs, which say what you contribute and authorize nothing.
Join an existing workspace on another machine
PromptThis is an existing team workspace. Set this machine up for member
maya, connect the workspace checkout, and obtain the repositories already recorded here.
The agent selects the existing member and binds this machine. It does not initialize the shared workspace again.
Add a member
PromptAdd Alex to this workspace with band 2 and the role docs. Write Alex's intents and plans in Indonesian with a semi-formal tone and keep technical terms in English.
Every member gets a band; without one, the agent offers the next free band. Roles are optional, and the question may be skipped.
Select a member before changing the workspace
PromptI am Maya, who is already listed in this workspace. Select me on this machine, then continue the change I requested.
If you are new, say so and ask the agent to add and select you. A workspace can still answer questions before selection, but it waits for a listed member, with a band, before making changes. If a member has no band, the agent offers the band status suggests for you to confirm or change. The selection attributes work; it does not verify identity.
Change an allocation band
PromptMove Alex to band 3 so Alex's new records start at
i300andp3000.
Every member holds a distinct band, and each member's reservations live in their own ID file, so members can create records from offline clones without choosing the same IDs. Changing a band never renumbers existing records. Bands reduce one collision class; they are not distributed locking. Workspace commits still need synchronization before separate clones allocate.
Connect repositories
Connect an existing checkout
PromptConnect
../billing-apiasapi. It owns billing rules and starts work frommain.
Clone a repository already described by the workspace
PromptClone the
webrepository recorded in this workspace and userelease/24.4as this machine's base branch.
The shared default branch and this machine's base branch are different facts.
Register a new remote repository
PromptAdd the existing checkout at
../notificationsasnotifications, record its origin, and describe it as the service that sends billing emails.
Initialize an empty repository
PromptCreate a new local repository called
reporting, connect it to the workspace, and usemainas its initial branch.
Record a relationship
PromptRecord that
webconsumes theapibilling endpoints and thatapipublishes invoice events tonotifications.
Describe the workspace repository
PromptConnect this workspace's own Git repository so team members know where the shared records travel.
The workspace repository is not a work repository and is not named by plans.
Install and update Context Circuit
Install the pinned CLI
PromptInstall the Context Circuit CLI version this workspace pins and verify the installed binary.
The agent runs every later command through the workspace's launcher, which runs exactly that pinned version.
Update only the CLI
PromptUpdate the CLI used by this workspace to version
2.5.0. Do not change the workspace template or existing records.
An update stays on the workspace's own release line.
Update the workspace template
PromptUpdate this workspace from its recorded template version to
2.5.0. Show me the upstream delta and preserve our project-owned files and records.
The agent applies the version-to-version delta. It does not recopy a release over the workspace, and it reads, rather than applies, a delta that deletes the shared ID file or changes the schema version, because the CLI migrates those. When the upgrade migrates the workspace — the schema 3 ID split, or the 2.5.0 rename of archive/ to _archive/ — the agent tells you first: one person on a team makes that change, commits and pushes it, and everyone else installs the new CLI and pulls before changing anything.
Configure agent roles
PromptShow the explorer, planner, worker, and reviewer settings in force for Cursor on this machine.
PromptConfigure the Cursor planner to use
<supported-model>with high effort, then refresh the native role definitions without overwriting customized definitions.
Settings express host preferences. A generated definition does not prove the host loaded it.
Build project knowledge
Gather from named evidence
PromptRead
sources/billing-rules.mdandsources/customer-interviews.md. Turn the durable product rules into project knowledge, update the catalog and glossary, and keep raw evidence separate.
Only the exact named sources are read. The resulting notes describe the project, not those source files.
Gather from repositories
PromptDocument how invoices move from draft to paid by reading the relevant
apiandwebcode. Add durable knowledge with repository anchors.
Query knowledge
PromptWhat does this project already know about invoice cancellation, credit notes, and overdue reminders?
The agent retrieves the smallest relevant set through the catalog instead of scanning every note.
Add actor knowledge
PromptDocument what a freelance seller and an accounts-payable reviewer each need from the invoice approval flow today.
Actor notes describe current needs, not a future backlog.
Clarify vocabulary
PromptWe use “void” and “cancel” differently. Record the project meaning and the code identifiers each repository uses.
Mount organization knowledge
PromptMount our
platform-knowledgerepository as read-only shared knowledge, usingindex.mdas its catalog.
Retrieve borrowed knowledge
PromptFind what our project and the mounted platform knowledge say about idempotency.
Matches identify which side owns each note. Borrowed knowledge is never copied into this workspace.
Reconcile stale knowledge
PromptCheck which owned knowledge may be stale against the code. Walk me through the findings and update only notes you actually re-read.
Design before deciding an outcome
Use a system design when a large change needs its shape settled before it can be expressed as bounded outcomes.
PromptDesign the end-to-end subscription billing system: actors, domain boundaries, repository responsibilities, data flow, failure behavior, and rollout constraints. Write it as source material; do not create intents or start implementation.
A design has no status and grants no approval. It is evidence an intent may cite when the outcome genuinely rests on it.
Request a normal product change
Start an intent
PromptAdd recurring billing to the API and web app. Existing customers must remain on their current plans.
The agent retrieves relevant knowledge, writes the outcome it understood, asks numbered questions, and stops before detailed code investigation.
Answer open questions
Prompt
- Monthly and annual plans only.
- Existing subscriptions keep their price until manually changed.
- Failed renewals retry for seven days.
Approve the written outcome
PromptThe intent matches what I want. I approve it.
Approval records your exact words and stops: the agent recommends planning as the next step. No code is read and no plan ID is reserved.
Ask for plans
PromptCreate the plans for this intent.
The agent then reads real code and writes linked plans without asking for approval again.
Approve and plan in one message
PromptThe intent matches what I want. I approve it. Create the plans.
Once you have read the intent, approval and the planning request may come together. Asking for an intent to be written and planned in one go is not approval, because nobody has read it yet.
Answer the commit question
PromptCommit and push.
PromptCommit only.
After approval, completion, or archiving, the agent asks whether to commit and push the records and ID files it left uncommitted, or commit only. Your answer authorizes those files, that once. After "commit only", the agent says other clones cannot see them yet. If the push is refused because the remote moved on, the agent rebases the record commits, keeps what Git combines, brings any record conflict to you, and never force-pushes.
Request a standalone plan
PromptThe outcome is already specified. Investigate the current code and write a detailed plan for adding an invoice CSV export. Present the plan before implementation.
The agent can create a grounded plan folder without an intent. It still waits for a separate execution request.
Correct the outcome before approval
PromptDo not include annual plans in this change. Update the intent and show it again.
Change an approved outcome
PromptThe success criteria must now include prorated upgrades. Update the intent and ask me to approve the changed outcome.
A material outcome change returns to the intent. An implementation detail inside the approved outcome does not.
Make a direct change
Explicitly bypass records and worktrees
Prompt
/cc-directFix the incorrect support email in the website checkout. Work on its current branch and leave the change uncommitted.
Direct code change with an exact outcome
PromptMake this validation message say “Workspace name is required.” Change it directly in the bound
webcheckout, run the relevant test, and do not commit.
If the request turns out to need a product decision, the agent stops and offers the intent path.
Explore without changing code
Ask a bounded codebase question
PromptFind where invoice numbers are allocated, which database constraint makes them unique, and which tests cover collisions. Return evidence only.
Compare repositories
PromptTrace how the
webapp submits an invoice and howapivalidates it. Identify mismatched assumptions without proposing a new outcome.
Investigate feasibility before changing the intent
PromptBefore I decide whether offline invoice creation belongs in the outcome, investigate the current synchronization model and tell me what is feasible.
Exploration is read-only. It cannot approve, plan, or implement a change by itself.
Execute planned work
Run one plan
PromptExecute
p0007. Prepare its worktrees, implement the approved outcome, run the repository checks, and report what remains unverified.
Run all plans for an intent
PromptExecute all plans for the recurring-billing intent. Derive their dependency order and recommend waves or a linear chain with the cost of each.
Choose the execution shape
PromptUse waves for this run.
PromptUse a linear chain for this run.
Resume interrupted work
PromptResume
p0007. Inspect the actual branches and diffs before trusting the plan record, preserve partial work, and continue from what Git shows.
Handle a blocked run
PromptExplain which plans finished, which one is blocked, and which dependents are waiting. Preserve every branch and do not invent a repair for anything that needs my decision.
An execution request covers worktree preparation, implementation commits on the plan branches, and local integration merges required by that run. It does not authorize delivery.
Use subagents
Delegate exploration
PromptUse explorers to investigate the API retry policy and the web cancellation flow in parallel. Return evidence; do not edit either repository.
Delegate implementation
PromptDispatch one worker per ready plan, wait for every result, and integrate their reported checks. Stop if a worker is blocked.
Use several workers in one worktree
PromptSplit this plan into bounded worker tasks inside the same worktree. Make every worker preserve the others' edits.
One worker per plan owns a whole worktree. Several workers inside one worktree share files; the briefs must say which form is being used.
Review
Ordinary review
PromptReview the current branch diff for correctness, regressions, security risks, and missing tests. Do not change code.
Independent review
PromptIndependently review the changes for
p0007against the intent's success criteria. Use a fresh read-only reviewer and report any limit on independence.
Review a pull request
PromptIndependently review pull request
<url>and give me findings with locations. Do not post comments or launch fixes.
Independent review is optional, manually requested, and never an automatic delivery gate.
Deliver work
Each outward action must be requested explicitly.
Commit direct work
PromptCommit the direct website changes using the repository's commit convention. Do not push.
Worktree implementation commits are covered by execution; commits in a bound checkout are not.
Push a branch
PromptPush the branch for
p0007. Do not open a pull request.
Open pull requests
PromptOpen pull requests for the recurring-billing work against each machine's recorded base branch. Use only the chain-end branch for each repository.
Update a pull request
PromptUpdate the API pull request description to reflect the revised retry behavior.
Merge
PromptMerge pull requests
<api-url>and<web-url>into their current targets.
Deploy or publish
PromptDeploy the merged website revision to
<environment>and report what was actually observed.
Delivery does not mark plans complete.
Complete the circuit
Complete one plan
PromptThe change from
p0007has landed. Mark the plan complete with these exact words: “Recurring billing shipped in the API.”
Complete several plans
PromptThe recurring-billing pull requests have landed. Mark all of its plans complete and reconcile the durable knowledge once across the set.
State that knowledge did not change
PromptComplete
p0008. This was a presentation-only correction; confirm whether any durable knowledge changed and record the result honestly.
Completion is the note plus knowledge reconciliation. Most completions change no durable concept.
Organize and clean up
Delete records after reviewing a preview
PromptPreview every intent and plan created by member
maya, including archived records. Show me the exact list and IDs that would become reusable. Do not confirm deletion yet.
When the roster lists only you, you can ask to preview all records instead. After seeing the list, explicitly agree to that list before deletion. The CLI refuses when a record outside the selection or a local worktree would be left referring to deleted work, and the agent shows that refusal with the records blocking it. Deletion must later be committed and synchronized across clones.
Delete specific records
PromptPreview deleting intent
i104and its planp1007— I changed my mind about that change. Show me who wrote them, whether they are approved or completed, and any leftover branches. Do not confirm yet.
Deletion by ID reaches exactly the records you name, whoever wrote them, or a reserved number no record holds. A deleted plan is taken out of its intent's list; any other link refuses and names the IDs to add.
Archive records
PromptYes, archive my finished records.
PromptArchive the completed recurring-billing intent and plans. Preserve every ID reservation and repair relative links.
After completion the agent offers to archive your finished records under _archive/; a no changes nothing. Archival is optional organization, not a lifecycle stage, keeps every ID reserved, and asks the commit question afterwards.
Remove a worktree
PromptRemove the worktree for
p0007if it is safe. Preserve dirty, untracked, and ignored files, and keep the branch.
Discard a worktree explicitly
PromptRemove the
p0007worktree and discard its dirty, untracked, and ignored files. Keep the branch.
Delete a branch
PromptDelete the local
cc/p0007/apibranch after confirming its work is preserved elsewhere.
Worktree removal and branch deletion are separate requests.
Recover and repair local mechanics
Inspect worktrees
PromptList the real Git worktrees and explain any stale Context Circuit association.
Move a worktree
PromptMove the worktree for
p0007to<new-path>using Git and update the local association.
Repair an association
PromptRepair the local worktree association for
p0007from Git's inventory. Do not reset or recreate its branch.
Prune stale associations
PromptI removed the
apiworktree forp0007by hand. Drop the stale association.
worktree prune drops associations of worktrees Git no longer lists and touches no worktree, branch, or file. Repair is for a checkout Git still lists that only moved.
Change this machine's base
PromptChange the
apicheckout's base branch on this machine torelease/24.4. Do not change the shared repository default.
Ask for honest limits
These prompts are useful when evidence is incomplete:
PromptReport only checks you actually ran and observations you actually made. Call everything else unverified.
PromptPreserve partial work and tell me the smallest decision or external action needed to continue.
PromptDo not call the implementing session's own inspection independent.
PromptDo not print environment contents, credentials, provider payloads, or machine-specific paths into shared records.
Requests that should not be combined
Keep these decisions explicit even if they happen in one conversation:
| Do not conflate | Why |
|---|---|
| Initial request and intent approval | The approved object is the written outcome |
| Intent approval and planning | Approval records the decision; planning follows a request, which may come with it |
| Planning and execution | Execution waits for a request after the plans exist |
| Execution and independent review | Review is optional and read-only |
| Execution and delivery | Push, PR, merge, and deploy are outward actions |
| Delivery and completion | Landing code does not reconcile knowledge |
| Completion and worktree removal | A completed branch may still be useful |
| Worktree removal and branch deletion | They preserve different artifacts |