Workflows

Practical conversations and commands, with explicit human decisions along the way.

A normal change follows the same conversation every time. The agent gathers durable context, writes an intent, and waits. You answer numbered questions and approve the outcome. The agent reads real code and writes plans. You ask for execution after those plans exist. You authorize delivery when the work should leave the machine. You request completion so the knowledge that changed is reconciled.

None of those later requests is implied by the first one. “Add billing” is not approval of the derived intent. An earlier “implement this” does not start execution once plans appear. Delivery does not complete a plan. Completion does not delete working copies.

The human gates

Ground the request in accepted product knowledge. Contradictions become questions, not quiet assumptions.
Approve the written intent. That authorizes planning only.
Ask to execute after the plans can be seen.
Authorize delivery — push, pull request, merge, or publication — as a separate request.
Request completion. The agent records your note and updates the knowledge the change actually altered.

A person can bypass intent, planning, and worktree preparation for a change that is already its own specification. That still happens in the bound checkout, and commits, delivery, and deletion still need authorization.

The CLI records facts and prepares files. It does not call a model, execute a plan, commit, push, or supply consent.

Gather project context: Retrieve accepted knowledge before deriving an outcome.
Write and approve an intent: Present the outcome, wait for answers, record the approval.
Create plans: Investigate real code after approval and write the work.
Execute plans with workers: Prepare worktrees, implement, check, and optionally dispatch workers.
Deliver changes: Push, open a pull request, or merge only when asked.
Complete plans and update knowledge: Append the note and reconcile what actually changed.
Change lifecycle: The connected path from request through reconciliation.
Website content contracts: How this documentation stays tied to tagged product source.