writing-prds
Create Product Requirements Documents. Use when defining new features, projects, or initiatives. Covers user stories, acceptance criteria, and scope definition.
When & Why to Use This Skill
This Claude skill automates the creation of comprehensive Product Requirements Documents (PRDs), enabling product teams to define clear project scopes, user stories, and acceptance criteria. By following industry-standard frameworks like INVEST and Given/When/Then, it ensures technical clarity and alignment between stakeholders from ideation to execution.
Use Cases
- New Feature Definition: Quickly generate structured PRDs for upcoming features, including business goals, success metrics, and stakeholder identification.
- Agile Backlog Refinement: Transform high-level ideas into detailed user stories with clear, testable acceptance criteria for development sprints.
- Scope Management: Establish a clear project boundary by defining 'Out of Scope' items and functional requirements to prevent scope creep.
- Standardized Documentation: Maintain consistency across product teams by using a unified template and saving formatted artifacts directly to project repositories.
| name | writing-prds |
|---|---|
| description | Create Product Requirements Documents. Use when defining new features, projects, or initiatives. Covers user stories, acceptance criteria, and scope definition. |
| allowed-tools | Read, Write, Glob, Grep |
Writing PRDs
Workflows
- Define Goals: Articulate business goals and success metrics
- Identify Stakeholders: List all relevant stakeholders
- Draft User Stories: Capture user needs
- Detail Requirements: List functional and non-functional requirements
- Save Artifact: Save to
./artifacts/prd_[feature].md - Review: Conduct stakeholder review
PRD Structure
- Overview: What and why
- Goals & Success Metrics: How we measure success
- User Stories: Who benefits and how
- Requirements: What must be built
- Out of Scope: What we're NOT building
- Timeline: Key milestones
User Story Format
As a [role],
I want [feature],
So that [benefit].
Example
As a registered user,
I want to reset my password via email,
So that I can regain access to my account if I forget it.
Acceptance Criteria
Use Given/When/Then format:
Given I am on the login page
When I click "Forgot Password"
Then I see a form to enter my email
Given I enter a valid registered email
When I submit the form
Then I receive a password reset email within 5 minutes
INVEST Criteria
Good user stories are:
- Independent: Can be developed separately
- Negotiable: Details can be discussed
- Valuable: Delivers user value
- Estimable: Can be sized
- Small: Fits in a sprint
- Testable: Has clear acceptance criteria