What problem does it solve? Writing a PRD from scratch often skips critical discovery steps, leading to unexamined assumptions, scope creep, and rework. This Skill enforces a structured brainstorming process that grounds every PRD in codebase context, market research, and explicit user decisions before any document is written. ## Core Features & Use Cases - Parallel Context Discovery: Runs codebase exploration and web market research simultaneously before asking any questions, so the PRD reflects real constraints and competitive landscape. - Structured Clarification Protocol: Asks one multiple-choice question at a time, focused strictly on WHAT users need and WHY, never on technical implementation. - Decision Traceability: Creates Architecture Decision Records (ADRs) for each approved product approach and links them in the final PRD. - Use Case: A product manager wants to spec a new notification feature. The Skill researches the codebase and market, asks targeted questions about user needs, presents 2-3 product approaches with trade-offs, then generates a complete PRD at .compozy/tasks/<slug>/_prd.md following the canonical template. ## Quick Start Ask the agent to create a PRD for your feature idea, for example: create a PRD for team activity feeds.
