prdlisted

# /prd. Structured spec generator Transforms vague ideas → a structured spec with verifiable success criteria, explicit blast radius, and ship-or-park gates BEFORE writing any code. Replaces the failure mode where vague-idea → impl skips the intermediate spec and you ship the wrong thing. **When to use**: any new substantive build. a new skill, a new cron task, a new infra change, a new process, a content-pipeline change, anything that touches multiple files or spans >1 turn. NOT for: bug fixes, micro-edits, single-line corrections, casual Q&A. **When NOT to use**: when scope is already obvious + 1-step (e.g. "kill these 4 orphan procs"). Don't bloat single-step work with PRD ceremony. ## Lifted from `wwwazzz/senior-pm-prompt` (GitHub, MIT-spirit). Pattern lift, not a full ship. adapted to the stack with helicopter-check + sycophancy-guard + scope-discipline native. Source patterns: aggressive first-pass mining / slot-filling / consistency PASS-FAIL / opinionated defaults marking `_TBD_` explicitly (vs fabricating). ## 4-Phase procedure ### Phase 1. AGGRESSIVE FIRST-PASS MINING When the user surfaces a vague idea ("we should build X" / "let's spec out Y"), extract whatever structure is implicit in their phrasing BEFORE asking questions. Do NOT immediately ask "what do you want?". mine first. Extract: - **Title** (slug-form). what to call this - **Goal** (1-sentence outcome). what it accomplishes when done - **Stakeholder** (who cares). The operator? A persona? A sub-