implement-plan

Implement Plan

Carry a plan from docs/plans/ to landed commits on the base branch, with no human turn between phases. Progress is durable only once committed and ticked.

With two or more plan paths, follow programme.md instead. Open lead.md before the first dispatch, on a stop and before landing.

Gotchas

• Invoking this skill arms a session-long Stop hook. It blocks a stop once per commit while plan/<slug> holds an unticked criterion. Commit ## Run state before a genuine stop.
• The plan copy on the base branch is stale during the run by design. Read and tick it in the run worktree.
• Redoing finished work is the most expensive failure. Resume first, on every invocation.
• The log outranks the checkbox. A tick without a trailer commit is unticked; a trailer commit without a tick is re-verified, then ticked.
• Pass the plan to every agent as a path. Pasted phase text goes stale on the first tick.
• Pin the base once as a sha and target it in every dry run, rebase and merge.
• Only the lead writes the plan file.

Steps

1. Resume. Finish or abort a half-open rebase or merge only from its owning worktree.
2. Read the plan. Detect the base from origin/HEAD, else git ls-remote --symref origin HEAD; ask if neither resolves.
3. Review the unmet phases in one pass: ambiguous or unverifiable criteria, missing files, commands the allowlist lacks.
4. Phases passing the concurrency test run as parallel lanes, up to the writer cap in lead.md. Set each phase's review tier.
5. State the run contract once and start: base sha, phase grouping and tiers, worktrees, verify command. Only open forks and missing allowlist commands wait for the user.
6. Create ../<repo>-wt/plan/<slug> on branch plan/<slug> from the pinned base. Confirm the verify command passes on unchanged code.
7. Run sequential phases in the run worktree. A concurrent phase gets its own worktree, branch and agent.
8. Commit per criterion with the trailer Plan: <slug> phase <N> criterion <M>. One targeted check per criterion, reusing an existing test or gate before writing one; the full gate once per phase.
9. Tick a phase's criteria in one commit when it closes, only what a tool result proves. An existing test, lint, typecheck or command output counts.
10. Fold each lane into plan/<slug> in phase order: rebase onto the run tip, merge --ff-only, re-verify.
11. Delete ## Run state in its own commit, then land as lead.md says. git rm the plan only when every criterion is ticked.
12. Report phases complete and blocked, criteria ticked, commits landed, dropped agents and the plan file's fate.