Implement

Goal

• All changes applied and committed.
• Verification pass.

Prerequisites

• Input already specifies exact code changes, not vague requirements.

Input

• Stages

  : ordered implementation stages (see the

  Stages

  shape). Each stage MAY carry

  id

  tag(s).

• fixup mode

  (optional): a stage may carry a

  fixup-of

  originating commit to fix up instead of committing fresh.

Steps

Step 1: Execute Plan

• Follow the

  Stages

  from the plan in order.
• Within each stage:
  • Apply the stage's code changes, lint/format, and verify against immediate scope.
  • Commit changes - if the stage is tagged for fixup mode, commit as

    git commit --fixup <originating-commit>

    instead of a plain commit.

Step 2: Verify

• Check all changes committed, each stage as a separate commit.
• Run relevant static checks.
• Run relevant runtime tests.
• Validate against Success Criteria if provided.

Step 3: Handle Deviations

1. Assess the deviation and determine the root cause.
2. Confirm it implies a simple fix. If it's suspected to be a significant change of the initial plan, or the same check has now failed 3 times in a row, stop and ask the user how to proceed.
3. Apply and commit the fix as

   git commit --fixup <hash>

   against the offending Stage's own commit from Step 1 (never the fixup-mode originating commit, even if the Stage itself was committed in fixup mode), then

   git rebase --autosquash <commit before Step 1's first Stage commit>

   once done.
4. Return to Step 2 and re-run - repeat until all pass.

Output

• Commits: per input

  Stage

  , its

  id

  tag(s) (if any), commit hash(es), message(s), affected files.
• Deviations: Unexpected changes from original plan and how they were resolved. Each entry echoes the

  id

  (s) carried by the

  Stage

  .
• Verification Results: Stages, commits, quality checks status. Entries echo the

  id

  (s) of the stages they cover, if tagged.