course-correct

Course Correct

Step back from a PRD issue mid-build and ask what per-PR review can't: does the merged work plus the remaining plan still reach the goal — and if not, what to add, remove, or re-scope?

Judges the plan, not the code — reviewer and critic own quality; this never writes code or PRs, only edits the plan in place, behind a gate. Checkpoint-aware — each run digests only what merged since the last; re-run it each time a wave of PRs lands.

/course-correct [--issue=N] [--since=<git-ref>]

  1. Find the issue; read goal + plan + the checkpoint
  2. Gather what landed since the checkpoint (merged PRs + diffs)
  3. Read the merged diffs against the goal   (read-only subagents)
  4. Judge drift; draft a Status refresh + plan edits
  5. Discuss and approve                       (gate)
  6. Apply to the SAME issue; post an audit comment; advance the checkpoint

Phase 1 — Find the issue and read the checkpoint

Use --issue=N if given; else scan the conversation for the last PRD published: ... (issue #N) line, or ask. Confirm an auto-detected number.

The body must have ## Build plan and ## PR breakdown — if either is missing, stop and run /to-issues then /pr-breakdown first.

Read, and keep separate:

• The goal — the PRD prose (The problem / What we're building / decisions / scope). Re-read it fresh each run — it's the yardstick; if the goal itself was rewritten, re-judge the whole plan against the new one.

• The plan — the ## Build plan slices and ## PR breakdown rows.

• The checkpoint — the marker left in the Status block:

  <!-- course-correct baseline=<sha> checked=<iso-date> -->
  

  baseline is the commit last reconciled. Resolve it into BASELINE, in order:

  1. --since=<ref>, if given.
  2. the marker's baseline=<sha>, if still in history (git cat-file -e "<sha>^{commit}" succeeds).
  3. otherwise — first run, missing marker, or a force-pushed sha — reconcile the whole build from the parent of its earliest merged PR: