What problem does it solve?
Writing a complete, consistent PRD is time-consuming and often results in vague requirements that designers, developers, and testers cannot act on. This Skill provides a standardized PRD structure that ensures every requirement is clear, testable, and traceable.
Core Features & Use Cases
- Standardized PRD Template: Covers 11 sections including overview, requirement penetration analysis, competitive research, user personas, functional and non-functional requirements, user stories, success metrics, scope, risks, and milestones.
- Acceptance Criteria Enforcement: Every functional requirement includes testable acceptance criteria, priority levels (P0/P1/P2), and edge case handling.
- Quality Checklist: Built-in pre-delivery checklist verifying completeness of requirement analysis, scope definition, and risk identification.
- Use Case: After completing requirement analysis for a new feature, invoke this Skill to produce a Markdown PRD file (prd-{feature}-{date}.md) that downstream design, engineering, and QA agents can directly consume.
Quick Start
Ask the PM agent to write a PRD for your feature after requirement analysis is complete, and it will output a structured Markdown document following the standard template.