What problem does it solve?
Product teams and developers often receive vague feature requests that lack clear goals, acceptance criteria, and scope; this skill turns a feature idea into a precise, actionable Product Requirements Document so work can be implemented reliably.
Core Features & Use Cases
- Clarifying Questions: Prompts the user with 3–5 targeted, lettered questions to resolve ambiguity before drafting.
- Structured PRD Output: Produces a markdown PRD with Introduction, Goals, User Stories with verifiable acceptance criteria, Functional Requirements, Non-Goals, Design/Technical Considerations, Success Metrics, and Open Questions.
- Artifact Saving: Guides saving the resulting PRD to tasks/prd-[feature-name].md for immediate tracking.
- Use Case: Turn a stakeholder note like "add recurring billing" into a scoped PRD with user stories, acceptance checks, and measurable success metrics.
Quick Start
Create a PRD for a feature that lets users duplicate and share project templates across teams.