write-drplisted

# write-drp — detailed requirements & plan (Stage 3) Produce `docs/<NAME>_DRP.md` from `docs/templates/DRP.template.md` (copied into the project by new-project; fall back to the ONBOARDING repo if absent). **A DRP is not a PRD.** It is the *engineering* requirements spec — an SRS for the requirements half plus design detail for the rest, carrying the layout, the pinned libraries, the integrations with their failure policies and the cross-cutting concerns (R10). Engineering owns it, and the same people write the RFC — which is why the two are co-authored. If the user says "PRD" and means personas, user stories, success metrics and release criteria, that is a **different, product-owned document that sits upstream as an input** to the RFC, never beside it. Say so rather than writing one document that tries to be both. ## Reuse first Reuse the capability, keep the house format (template, section order, mermaid house rule): - **Existing code?** Run the **`Explore`** agent for the R10 inventory below — read-only fan-out that returns the conclusion, so a large repo doesn't eat the context the requirements need. "medium" breadth, or "very thorough" on an unfamiliar codebase. - If the RFC already inventoried the repo, **read its layout/dependency section instead of re-running Explore** — the DRP details that agreement, it doesn't re-litigate it (R7). - No diagramming skill here: a DRP illustrates with **mermaid**, which renders natively. (`artifact-diagramming` and `dataviz