Context Circuit
Workflows

Change lifecycle

Human decisions connect preparation, implementation, delivery, and completion.

Template 2.5.0CLI 2.5.0

A change that begins with an intent follows these decisions:

  1. Ground the request in product knowledge.
  2. Write an intent the person can approve.
  3. Approve the written outcome.
  4. Ask for plans; the agent investigates real code and writes them.
  5. Request execution after the plans exist.
  6. Implement in prepared worktrees and run checks.
  7. Authorize delivery.
  8. Request completion and reconcile the knowledge that changed.

When the outcome is already specified, a person can request a grounded plan directly. The agent presents that standalone plan, and implementation still waits for a separate execution request. Optional workers and cleanup sit beside either path.

Request through execution

The agent grounds a request in product knowledge and writes an intent. You read it and approve the outcome; the agent records that and recommends planning. When you ask for plans — later, or in the same message as the approval — the agent investigates real code and writes them. Once plans exist, you request execution; the agent prepares worktrees, implements, and runs checks.

Delivery through reconciliation

You authorize outward delivery. After the work lands, you request completion. The agent appends the note, reconciles the knowledge affected by the implementation, asks whether to commit and push the records, and offers to archive finished records. That knowledge feeds the next request.

Neither a CLI diagnostic nor an editable approval field supplies consent. Delivery does not mark completion, and completion does not delete working copies. See human control boundaries for the full decision table.

On this page