Tools to generate and manage PRDs with INVEST-compliant user stories and structured technical requirements.
Install
mkdir -p .claude/skills/prd-alfredolopez80 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11873" && unzip -o skill.zip -d .claude/skills/prd-alfredolopez80 && rm skill.zipInstalls to .claude/skills/prd-alfredolopez80
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Product Requirements Document generation and management with INVEST-compliant user storiesKey capabilities
- →Generate Product Requirements Documents (PRDs) for new features or enhancements.
- →Break down complex projects into INVEST-compliant user stories.
- →Convert PRDs into actionable implementation tasks.
- →Track progress across multiple PRDs.
- →Retrieve the next uncompleted user story.
How it works
The skill creates a PRD markdown file based on a feature description, then converts this PRD into a JSON file containing actionable user stories.
Inputs & outputs
When to use prd
- →Plan a new product feature
- →Break down complex projects into user stories
- →Document requirements for team collaboration
- →Convert PRD to implementation tasks
About this skill
v2.88 Key Changes (MODEL-AGNOSTIC)
- Model-agnostic: Uses model configured in
~/.claude/settings.jsonor CLI/env vars - No flags required: Works with the configured default model
- Flexible: Works with GLM-5, Claude, Minimax, or any configured model
- Settings-driven: Model selection via
ANTHROPIC_DEFAULT_*_MODELenv vars
PRD System
Generate and manage Product Requirements Documents (PRDs) with INVEST-compliant user stories for structured task breakdown.
When to Use
- Planning new features or major enhancements
- Breaking down complex projects into user stories
- Creating structured task lists for Ralph Loop execution
- Documenting requirements for team collaboration
- Converting PRDs into actionable implementation tasks
PRD Structure
| Section | Purpose |
|---|---|
| Overview | Brief description and business value |
| Goals | Measurable objectives |
| User Stories | INVEST-compliant stories with acceptance criteria |
| Technical Requirements | Architecture, stack, dependencies, security |
| Success Criteria | Metrics and targets |
| Out of Scope | What's explicitly NOT included |
| Implementation Plan | Phased tasks breakdown |
| Risks & Mitigations | Potential issues and solutions |
Commands
Create PRD
ralph prd create "Implement OAuth2 authentication"
ralph prd create "Add real-time notifications" --priority high
Creates file in tasks/prd-<feature>.md
Convert to Stories
ralph prd convert tasks/prd-auth.md
Creates actionable user stories in tasks/prd-auth.json
Show Status
ralph prd status
Shows progress across all PRDs
Get Next Story
ralph prd next
Returns next uncompleted story
User Story Format (INVEST)
As a {{persona}},
I want to {{action}},
So that {{benefit}}.
Acceptance Criteria:
- [ ] {{criterion_1}}
- [ ] {{criterion_2}}
- [ ] {{criterion_3}}
INVEST Principles:
- Independent: Can be completed standalone
- Negotiable: Details can be adjusted
- Valuable: Provides user/business value
- Estimable: Complexity can be estimated
- Small: Fits within iteration limits
- Testable: Clear acceptance criteria
Integration with Ralph Loop
0. PRD CREATION → ralph prd create "feature"
1. /clarify → Intensive questions (populate PRD)
2. /classify → Complexity routing
3. PLAN → User approval (review PRD)
4. PRD CONVERSION → ralph prd convert tasks/prd-feature.md
5. EXECUTION → ralph loop --prd tasks/prd-feature.json
6. /gates → Quality validation per story
7. /retrospective → Propose PRD improvements
→ VERIFIED_DONE
Best Practices
- Start with Overview - Clear problem statement before solutions
- Measurable Goals - Use specific metrics (e.g., "reduce load time by 30%")
- INVEST Stories - Ensure each story is independent and testable
- Scope Management - Explicitly document "Out of Scope" items
- Risk Assessment - Identify risks early with mitigations
- Stakeholder Review - Get approval before converting to stories
- Iterative Execution - Execute one story at a time with validation
Related Skills
/clarify- Intensive questions (populate PRD details)/iterate- Execute PRD stories iteratively/orchestrator- Full workflow with PRD integration/plan- Plan-state management for execution tracking
When not to use it
- →When the project does not require structured task breakdown.
- →When user stories do not need to be INVEST-compliant.
- →When detailed documentation for team collaboration is not necessary.
Limitations
- →The skill's output is limited to the defined PRD structure.
- →User stories are generated based on the INVEST principles.
- →The skill manages PRDs and user stories, not other project documentation.
How it compares
This workflow automates the creation and conversion of structured PRDs and user stories, unlike manual documentation processes.
Compared to similar skills
prd side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| prd (this skill) | 0 | 4mo | No flags | Intermediate |
| spec-to-backlog | 8 | 4mo | No flags | Intermediate |
| iterate-retrospective | 0 | 2mo | No flags | Beginner |
| fc-assistant | 0 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
spec-to-backlog
atlassian
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When Claude needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
iterate-retrospective
product-on-purpose
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of a sprint, project, or milestone to reflect and improve team practices. To bank individual learnings into organizational memory afterward, use iterate-lessons-log.
fc-assistant
wam-leadclic
Main orchestrator for the Salesforce functional consultant engagement lifecycle. Detects the current project phase, guides the consultant through the full engagement (from pre-workshop preparation to training materials), and invokes the appropriate skill at each stage. Entry point for all functional
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
postmortem-writing
wshobson
Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.