writing-planslisted

# Writing plans Plans are short, dated, and checkable. One file per feature. Lives in `docs/llm-orchestrator/plans/`. ## When to use After `brainstorming` writes a spec and the user approves it. Or when the user hands you requirements directly. Skip for trivial work (under ~15 minutes of editing). Just do it. ## Steps 0.5. **Research gate (Trigger B).** Before re-reading the spec, scan its `## Approach` section. If the approach names libraries or version-specific APIs that the spec's `## Research` section doesn't already cover (i.e. brainstorming's Trigger A didn't catch them, or the user wrote the spec directly), invoke `research-classifier` against the approach text. If `RESEARCH_NEEDED` fires, dispatch `orch-researcher` with the eight-field envelope in `templates/researcher-prompt.md` (it returns `BLOCKED` on a missing field) and act on its outcome BEFORE writing any plan tasks. `CONTRADICTED` halts the plan write — revise the spec's approach first. 1. **Read the spec.** Re-read every section. Note any "TBD". Confirm `## Research` section is populated (verdict + brief path) or explicitly "none". 2. **Map files.** List every file you will create or modify, with line ranges if obvious. If you can't list them, the spec isn't ready. 3. **Order tasks.** Each task is independent enough to dispatch, or explicitly marked sequential. Where independence matters, declare an `Interfaces:` block per task — `introduces:` (symbols/endpoints/files the task creates) and `consumes:`