Prd analysis
Use when analyzing PRDs, detecting requirement gaps, mapping dependencies, assessing risks, or prioritizing features in product requirement documents.From its SKILL.md
npx -y skills add Babalsaab/Project_Starter --skill prd-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
PRD Analysis Skill
When receiving a PRD or project requirement document, apply this structured analysis:
Step 1: Gap Detection
Scan the PRD for:
- Missing success metrics (every feature needs a measurable KPI)
- Undefined edge cases (what happens when X fails?)
- Ambiguous requirements (terms like "fast", "secure", "modern" need quantification)
- Missing user flows (happy path is defined, but what about error/edge paths?)
Step 2: Dependency Mapping
For each feature/requirement:
- List all technical dependencies (APIs, services, data)
- List all team dependencies (which other agents need to deliver first?)
- Identify blocking vs non-blocking dependencies
- Flag circular dependencies
Step 3: Risk Assessment
Rate each requirement:
- Complexity: Low / Medium / High / Very High
- Uncertainty: Known / Some unknowns / Many unknowns
- Dependencies: None / Internal / External / Third-party
Step 4: Output Enhancement
When producing outputs based on PRD analysis:
- Always reference the specific PRD section you're addressing
- Call out assumptions explicitly
- Flag items that need clarification with [NEEDS_CLARIFICATION] tag
- Suggest alternatives when requirements seem suboptimal
Priority Framework
- P0: Must have for launch (blocks everything)
- P1: Should have for launch (degrades experience if missing)
- P2: Nice to have (can ship without)
- P3: Future consideration (explicit not-now items)