What problem does it solve?
Product teams and engineers often lack a concise, actionable specification when starting a feature, which causes misaligned expectations, rework, and slow implementation. This Skill formalizes feature intent into a single, structured document that developers and stakeholders can act on.
Core Features & Use Cases
- Guided Clarification: Prompts 3-5 essential, lettered clarifying questions to resolve ambiguous requirements before drafting.
- Structured PRD Output: Produces a markdown PRD with Introduction, Goals, Prioritized User Stories with verifiable acceptance criteria, Functional Requirements, Non-Goals, Technical considerations, Success Metrics, and Open Questions.
- Developer-Friendly Artifacts: Formats user stories and requirements explicitly for junior developers or AI agents and saves the result to a tasks folder for integration into workflows.
- Use Case: Product manager needs a scoped PRD and user stories for a new onboarding flow; the Skill asks clarifying questions, accepts answers like "1A,2C", and outputs tasks/prd-onboarding-flow.md.
Quick Start
Ask the skill to create a PRD by saying: Create a PRD for a passwordless login feature and answer the clarifying questions when prompted.