Name: Plan
Author: jamesacarr

Essential Principles

Codebase map = hard gate. The planner reads the codebase map, not raw source files — without it, plans lack convention awareness, correct file paths, and architectural alignment. Stop and direct user to /jc:map. No exceptions.
Research = hard gate. Plans without research are guesswork. Stop and direct user to /jc:research. No exceptions.
Acceptance criteria = hard gate. Generate ACCEPTANCE-CRITERIA.md before planning — planning without criteria undermines the verification chain. Acceptance criteria define what the plan must achieve; without them, success criteria are invented by the planner without traceability to requirements.
Critique loop is mandatory. The orchestrator lacks the planner's codebase map cross-referencing and research gap detection — every plan gets adversarial critique by a second planner invocation. Never skip critique.
Max 2 revision rounds. Plan → Critique → (if objections) Revise → Re-critique → (if still objections) Revise → Re-critique → done. Changes during revision can introduce new issues, so a second round catches cascading problems. 6 planner invocations worst case.

Codebase map = hard gate. The planner reads the codebase map, not raw source files — without it, plans lack convention awareness, correct file paths, and architectural alignment. Stop and direct user to /jc:map. No exceptions.
Research = hard gate. Plans without research are guesswork. Stop and direct user to /jc:research. No exceptions.
Acceptance criteria = hard gate. Generate ACCEPTANCE-CRITERIA.md before planning — planning without criteria undermines the verification chain. Acceptance criteria define what the plan must achieve; without them, success criteria are invented by the planner without traceability to requirements.
Critique loop is mandatory. The orchestrator lacks the planner's codebase map cross-referencing and research gap detection — every plan gets adversarial critique by a second planner invocation. Never skip critique.
Max 2 revision rounds. Plan → Critique → (if objections) Revise → Re-critique → (if still objections) Revise → Re-critique → done. Changes during revision can introduce new issues, so a second round catches cascading problems. 6 planner invocations worst case.

Check	Condition	Action
Missing	`.planning/codebase/` does not exist or has no files	Hard gate. Stop. Tell user to run `/jc:map` first
Stale	>50 source commits since last map (heuristic for significant drift)	Soft prompt. AskUserQuestion: "regenerate map?" or "proceed with current map"
Recent	≤50 source commits since last map	Proceed

Mode	`{action}`
`plan`	Create an implementation plan
`critique`	Adversarially critique the plan
`revise`	Revise the plan to address critique objections
`replan`	Replan remaining work preserving completed tasks

Step	Mode	Action	Output
6a	`plan` (or `replan`)	Create plan from research + codebase map + acceptance criteria	`PLAN.md`
6b	`critique`	Adversarially review the plan	`CRITIQUE.md` + PASS/OBJECTIONS
6c (if objections)	`revise`	Address critique objections	Revised `PLAN.md`
6d (if revised)	`critique`	Re-review revised plan	Updated `CRITIQUE.md` + PASS/OBJECTIONS
6e (if objections)	`revise`	Address remaining critique objections	Revised `PLAN.md`
6f (if revised)	`critique`	Re-review revised plan	Updated `CRITIQUE.md` + PASS/OBJECTIONS

Excuse	Reality
"The planner can read the codebase directly"	The planner reads the codebase map, not raw source files. Without the map, it produces plans with wrong file paths, missed conventions, and broken verification commands
"Critique is overkill for a small plan"	Small plans still have wrong test runners, missed conventions, and file overlap. Critique catches these systematically. Cost: one extra planner invocation. Cost of skipping: executor failures at runtime
"I can review the plan myself instead of critique"	You lack the planner's codebase map cross-referencing. You will miss convention violations and research gaps that the critique mode specifically checks

Plan