spec-writerlisted

# Write a Product Requirements Document This skill turns a clarified idea into a **structured PRD** using conversation and repository context. It assumes that major ambiguities have already been grilled out (for example with `/grill-me`), but it can also perform its own lightweight clarification when needed. ## When to Use Use this skill when the user: - Asks to "write a PRD", "product spec", "requirements doc", "feature specification", or similar. - Wants to document a new feature, change, or system in a structured way before implementation. - Has already clarified the idea and now needs a single, coherent document you can file as an issue, share with stakeholders, or feed into `/slice-the-spec`. If the idea is still fuzzy or underspecified, recommend using `/grill-me` first and then come back to this skill. ## Overall Workflow You may skip or compress steps that are clearly already complete (for example, if the user pastes a detailed problem statement or user story list). 1. **Collect a rich problem description** - Ask the user for a long, detailed description of: - The problem they want to solve - Who it is for - Why it matters now - Any initial solution ideas or constraints they already have - Encourage them to paste existing context (docs, tickets, research) instead of re‑typing everything. 2. **Explore the repo and verify assumptions** - Inspect the codebase to understand current behavior, relevant modules, data models, and existing