Plan

Answer HOW. do-brainstorm answered WHAT, when it ran. A prior requirements file is optional. This skill does not implement, dispatch research agents, render HTML, or raise a model tier.

Done: the plan file is written, do-doc-review has finished or the run is blocked because it did not, and Next was shown or a caller return was sent.

Intake

Strip mode:return-to-caller if present and remember caller mode. Input is a requirements path, a feature description, or an existing plan path. If none, ask what to plan and wait.

Read a passed requirements file. Do not invent product behavior, scope, or success it does not contain. If those are missing, name the gap, write no units that depend on a guess, and set status needs-human.

An existing plan path is revised in place. Otherwise write a new file. Read the code the units will touch yourself. No subagent research pass.

Write

Location: project AGENTS.md override for plan paths, else docs/plans/. Create it if missing.

New file: YYYY-MM-DD-<topic>-plan.md in that directory. Local date, short lowercase hyphenated topic. If the path exists, append -2, then -3. Do not overwrite a requirements file.