Skip to content

How delivery would work

Give the coding agent an approved change

A direct Claude Code session can be enough for a contained change. When a story crosses repositories or review boundaries, the team needs a durable record of what was approved and the exact code it was based on.

Spec-driven coding with Claude Code

Where the handoff sits

See what an AI coding harness would give the assigned developer, how it checks scope, and what happens when approved inputs change.

The coding agent works inside the Plan and Implement steps, from an approved brief pinned to a source version.

  1. Understand

    Read the twin around the area you want to change: paths, rules, data and gaps.

    AI drafts · you read

  2. Define

    Write the use case, stories and acceptance criteria against the current model.

    AI drafts · lead edits

    Approve requirement
  3. Plan

    Propose files, symbols, tasks and the impact map. Every criterion needs a task.

    AI proposes · dev reviews

    Approve plan
  4. Implement

    The coding agent gets an approved, version-pinned brief and stops if inputs change.

    Agent writes · dev guides

    Review and merge
  5. Verify

    Test cases trace back to criteria. Results name the build they ran against.

    QA reviews · tests run

    Accept results
  6. Refresh

    The merge becomes a new commit. The twin rebuilds and old approvals are rechecked.

    Automatic

Every push starts the loop again from a fresh twin. Approvals built on the old code are flagged, not silently kept.

Walkthrough

Step by step.

  1. Build the handoff

    Include the current requirements set, approved plan, ordered tasks, source version, relevant evidence and criteria. Name the behaviour to preserve and the questions the agent should leave open. Keep human approval separate from generated suggestions.

  2. Check before starting

    The specified Start action binds current approvals and source inputs to an immutable specification. It checks assignments and prerequisites. A replaced plan or changed source needs reconciliation before an old approval can be used for a new run.

  3. Keep history when scope changes

    If a requirement changes mid-run, the planned workflow stops further dispatch and waits for an observed pause. Saved work and the original specification remain linked. The team replans and reviews before the assigned developer starts again.

What goes into the handoff

The agent receivesPinned toA change that needs review
Goal, boundaries and criteriaApproved requirement revisionScope expands to support overrides
Proposed edits, tasks and dependenciesReviewed plan and captured sourceShipping guard moves into a shared service
Checks and workspace constraintsApproved task set and applicable environmentThe previous tests ran against a different build