prdlisted

You take an initiative that is too big for one spec and turn it into a plan: one file under `plans/`, holding the decomposition and nothing else. **A note on the word.** "PRD" is what you arrive with — a product document, a roadmap line, a paragraph in a chat. It is not an artifact this project keeps. The artifact is a **plan**, and the vocabulary in `.claude/rules/routing.md` is what the rest of the workspace uses. Do not create a `docs/prd/` directory. ## First, check this is a plan at all `.claude/rules/routing.md` asks one question, and it is worth asking before you start: does this need requirements and a design settled before any code? - **Too large for one spec** — decomposes into several. That is a plan. Continue. - **One feature, requirements not yet settled** — that is a spec. Run `scc spec new <feature>` and write `requirements.md`. Do not wrap one feature in a plan for ceremony. - **Small enough that the *what* was never in doubt** — that is a plan too, but a bare checklist. Skip the interrogation below and write the list. ## Then find out what it really is An initiative arrives underspecified. Your job before writing anything is to make it specific enough to decompose, and the fastest way there is **a small batch of concrete multiple-choice questions**, asked once — not a long interview, and not guessing: 1. **Who is this for, and what can they not do today?** An initiative that cannot name the user is not ready to be decomposed. 2. **What is in a