What problem does it solve? Writing a high-quality PRD requires structured elicitation, disciplined scoping, and rigorous review — most teams either skip discovery or produce template-filler documents that fail downstream UX, architecture, and story workflows. ## Core Features & Use Cases - Three intent modes: Create a new PRD from a brain dump, Update an existing PRD against a change signal, or Validate a PRD with a seven-dimension quality rubric and consolidated HTML/Markdown report. - Guided discovery with working modes: Choose a Fast path (batched questions, tagged assumptions) or Coaching path (Vision + Features or Journey-led entry points) calibrated to project stakes. - Auditable run workspace: Every decision, change, and override is logged to an append-only memlog, with an addendum capturing depth that belongs downstream. - Reviewer gate: Parallel subagent reviews against a quality rubric produce tiered findings and a synthesized validation report. - Use Case: A product manager with rough notes and customer research invokes the skill, narrates user journeys, and receives a finalized PRD with stable FR/UJ/SM IDs ready for architecture and epic breakdown. ## Quick Start Ask the assistant to help you create a PRD for your product idea and answer the discovery questions it asks.
