implement-plan

Implement Plan

Purpose and authority

Implement the exact approved plan as the smallest complete patch. The plan limits behavior changes; repository evidence determines local form; the v3 implementation contract proves the result.

Accept finalized plan-contract v6 plans with either the legacy request binding or the enriched typed-handoff kind, version, and selected-item binding. Reject ambiguous, unfinalized, unsupported, receipt-mismatched, or materially contradicted plans. Route semantic gaps to plan-change; never reinterpret product intent during implementation. Preserve unrelated dirty work byte for byte, never edit a dirty target without explicit authorization, and stop on a concurrent target change.

Start

Resolve skill-root to this directory and pass the exact sealed plan plus an agent-owned implementation bundle:

python /absolute/skill-root/scripts/cli.py --repo-root /absolute/repo \
  --input plan_file=/absolute/final-plan.md \
  --input bundle=/absolute/implementation.json --format json doctor

Run each returned next_command.argv with its returned cwd. Read only required_reads, write only allowed_writes, and stop on every blocking_reason.

Next-step loop

1. Apply the intake, snapshots, dependency order, propagation, verification, and reconciliation rules in Implementation Contract.
2. Use Bounded Delegation Protocol for optional read-only review; the primary retains authority.
3. Treat Implementation Contract as authoritative for fields, statuses, plan versions, and safety policy.
4. Apply the quality and compatibility checks in Implementation Contract.
5. Use Safety and Recovery at the matching stop condition; never restore a whole file, worktree, or branch automatically.

Implement every planned branch, error, side effect, blueprint, and test. Allow unplanned edits only through the Mechanical Propagation Gate. Attribute a failure as pre-existing only when the identical check failed in the recorded baseline.

Completion and recovery

Complete only when sealing returns a validator-passing implementation.json with status complete and a matching v3 SHA-256 receipt. Report the plan version, changes, propagation, exact checks, residual risks, and unresolved records.

On failure, preserve the bundle and agent-owned snapshots, follow the hazard's recovery rule, and reverse only positively identified agent-owned hunks whose context still matches. Never weaken plan or quality evidence to pass validation.