ABOUTME: Issue or in-session analysis to locked ExecPlan + implementation prompt + /goal line

ABOUTME: Deep code analysis, 3-lab second opinion, plan on disk, delegation prompt for opus subagents in a worktree

Plan Forge

Codifies the delivery-prep playbook proven on hikma-mirsad#576 (verify-after-rewrite) and the model-manifest task: the planning session (main loop, typically Fable) does analysis and planning; implementation is delegated to a FRESH session driving opus-4.8 software-engineer subagents in a separate worktree, held to the plan by a /goal line.

Quality Notes

• Every mechanic claimed by the issue or discussion gets verified in the actual code (file:line) before it enters the plan. Never plan from memory or from the issue text alone.
• The plan is the source of truth for a session that has NO chat context. Self-containment test: could a fresh session execute from the plan file alone?
• Locked decisions are locked: the implementing session must not relitigate them.

Step 0: Resolve the input

• Issue mode: gh issue view <N> --repo <org/repo> --json title,body,comments. Read refs it cites (ADRs, prior PRs).
• Analysis mode: the problem was already dissected in this session; consolidate that.
• If neither gives a crisp problem statement, ask at most 1-2 clarifying questions (AskUserQuestion), then proceed.