What problem does it solve?
Product teams often struggle to transform vague feature ideas into detailed, shared requirements. This skill automates that process by generating a structured PRD from user input, clarifying questions, and a defined format that can be handed to engineering and design.
Core Features & Use Cases
- Generate a complete PRD with sections like Introduction, Goals, User Stories, Acceptance Criteria, Functional Requirements, Non-Goals, etc.
- Ask 3-5 clarifying questions to resolve ambiguity before drafting the PRD.
- Save the PRD to a file at /tasks/prd-[feature-name].md for traceability and handoff.
- Use cases: planning a new feature, starting a new project, or responding to a request for PRD.
Quick Start
Provide a feature description to generate a complete PRD saved at /tasks/prd-[feature-name].md.