.claude/skills/prd/SKILL.md
Product Requirements Document generation and management with INVEST-compliant user stories
npx skillsauth add alfredolopez80/multi-agent-ralph-loop prdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
~/.claude/settings.json or CLI/env varsANTHROPIC_DEFAULT_*_MODEL env varsGenerate and manage Product Requirements Documents (PRDs) with INVEST-compliant user stories for structured task breakdown.
| 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 |
ralph prd create "Implement OAuth2 authentication"
ralph prd create "Add real-time notifications" --priority high
Creates file in tasks/prd-<feature>.md
ralph prd convert tasks/prd-auth.md
Creates actionable user stories in tasks/prd-auth.json
ralph prd status
Shows progress across all PRDs
ralph prd next
Returns next uncompleted story
As a {{persona}},
I want to {{action}},
So that {{benefit}}.
Acceptance Criteria:
- [ ] {{criterion_1}}
- [ ] {{criterion_2}}
- [ ] {{criterion_3}}
INVEST Principles:
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
/clarify - Intensive questions (populate PRD details)/iterate - Execute PRD stories iteratively/orchestrator - Full workflow with PRD integration/plan - Plan-state management for execution trackingdevelopment
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
testing
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
testing
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
development
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.