plan

Plan

Arguments: $ARGUMENTS. The output is a file, never code. /nico:plan <task or PRD path> writes docs/plans/plan-<slug>.md; /nico:plan prd <problem> writes docs/prds/prd-<name>.md.

What implement-plan relies on

• The plan keeps the skeleton. implement-plan and the plan-run-guard.sh Stop hook parse ## Phase, **Depends on** and - [ ] lines.
• Paths go in each phase's Context and What to build. The concurrency test compares them pairwise.
• Phases meant to run in parallel touch disjoint files. Choke files (indexes, lockfiles, migrations) stay in one phase.
• A refactor that fans across the tree runs expand, migrate, contract. Expand adds the new form beside the old. Migrate phases are batched per package, parallel on disjoint files. Contract removes the old form and depends on every migrate phase.
• Each criterion is verified by one targeted command. An existing gate, test or command output comes first; a new test only where nothing covers the behaviour. The full gate runs once per phase.
• Reference code as path — symbol(), not line numbers; lines drift while phases land.

Plan mode

1. Read the input in full: the PRD, or the task and the code it touches.
2. Ask only what code, PRD and conventions leave open, in at most three rounds. Zero questions is normal.
3. Fix the durable decisions in the header: routes, schema, models, auth, third-party boundaries.
4. Slice into tracer-bullet phases, each a thin path through every layer and demoable alone. Pick the granularity yourself.
5. Self-review: fix placeholders such as TBD or "similar to phase N". Flag names used in one phase only. Propose KISS and YAGNI cuts.
6. Spawn a fresh-context opus plan critic on the file. Apply its findings and your cuts; route only forks with no clear winner through the decide skill.

PRD mode

1. Split a request bundling independently shippable features into separate PRDs.
2. Check the user's assertions against the code, then clarify in at most three rounds.
3. Weigh two or three approaches by effort, risk and reversibility. Record the pick and why.
4. Write the sections of the PRD skeleton in one pass.
5. New domain terms go into the repo's glossary, else docs/UBIQUITOUS_LANGUAGE.md: term, one-sentence definition, aliases to avoid.
6. Self-review as in plan mode.