write-prdlisted

# Write PRD: objectives before features, a kill switch before launch Ask this operating system for a PRD before this release and the router had nothing general enough to hand you: ai-prd assumes the implementer is a model, and every other skill assumed you already knew which document you needed. This skill is the ordinary case: a human engineering team building something real. The moment that stops being true, this skill stops too and hands the whole document to [ai-prd](../ai-prd/SKILL.md), explained below in step 2. Past that fork, it exists to stop three more specific failures: a spec written to avoid doing the discovery work, a features table with no objective above it, and a document that can start work but never says how to stop it. ## Files this skill drives - [../../templates/definition/prd.md](../../templates/definition/prd.md), the primary artifact, run from section 0 (the one-read summary) through section 13 (companion documents), then the sign-off block - The rest of the requirements stack, at whichever weight applies: [one-pager.md](../../templates/definition/one-pager.md), [brd.md](../../templates/definition/brd.md), [frd.md](../../templates/definition/frd.md), [nfr.md](../../templates/definition/nfr.md), [business-rules.md](../../templates/definition/business-rules.md), [prfaq.md](../../templates/definition/prfaq.md), and [assumptions-register.md](../../templates/definition/assumptions-register.md), which section 11's index points into by row ID - Reads [../