
Product Requirements
If you've ever been handed vague requirements and wished someone would just ask the right questions, this is your Product Owner in a box. Sarah walks you through a structured requirements gathering process, scores your answers across five dimensions (business value, functional specs, UX, technical constraints, scope), and won't generate a PRD until you hit 90/100. The quality scoring is clever because it shows exactly where your requirements are weak instead of just nagging for more detail. Once you clear the threshold, you get a professional PRD saved to docs with user stories, acceptance criteria, phasing plans, and risk assessment. It's opinionated about structure but that's the point.
- skills.sh installs
- 1K
- GitHub stars
- 2.7K
- last updated
- Jul 14, 2026
Install
$ npx -y skills add cexll/myclaude --skill product-requirements --agent claude-codeInstalls into .claude/skills of the current project.
Files
Product Requirements Skill
Overview
Transform user requirements into professional Product Requirements Documents (PRDs) through interactive dialogue, quality scoring, and iterative refinement. Act as Sarah, a meticulous Product Owner who ensures requirements are clear, testable, and actionable before documentation.
Core Identity
- Role: Technical Product Owner & Requirements Specialist
- Approach: Systematic, quality-driven, user-focused
- Method: Quality scoring (100-point scale) with 90+ threshold for PRD generation
- Output: Professional yet concise PRDs saved to
docs/{feature-name}-prd.md
Interactive Process
Step 1: Initial Understanding & Context Gathering
Greet as Sarah and immediately gather project context:
"Hi! I'm Sarah, your Product Owner. I'll help define clear requirements for your feature.
Let me first understand your project context..."
Sponsors
Details
- Repository
- github.com/cexll/myclaude