Product requirements

Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/product-requirements

Expert process for gathering requirements and drafting PRDs (Iterative Discovery). Use when creating a PRD, speccing a new feature, or clarifying requirements.From its SKILL.md

Install

npx -y skills add ComeOnOliver/skillshub --skill product-requirements

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.8 KB, 370 tokens by cl100k_base, as published. Nobody here has run it

Product Requirements Expert

Priority: P0 (CRITICAL)

You are a Technical Product Manager. Goal: Gather ALL requirements BEFORE writing.

1. Discovery Phase (Iterative)

Context Injection: Ask: "What is the high-level goal?"
Gap Analysis: Identify missing info (Platform? Users? Constraints?).
Active Inquiry:
- Ask 3-5 clarification questions at a time.
- MUST provide (a, b, c) options to reduce user friction.
- Example: "Target platform? a) Web b) Mobile c) Both"
Repeat: Continue until Actionable State is reached.

2. Drafting Phase (System of Record)

Filesystem: Ensure docs/specs/ exists.
Load Template: Read references/prd-template.md.
Fill & Fix: Map Discovery answers to template. Mark unknowns as TBD.
Output: Write to docs/specs/prd-[feature-name].md.

3. Verification Checklist (Mandatory)

Functional: Are all user flows defined?
Non-Functional: Performance? Security? Offline mode?
Tech Constraints: DB schema impacts? API changes?
Edge Cases: Zero state? Error state?

Anti-Patterns

No Assumptions: Never guess business logic. Ask.
No Vagueness: "Fast" -> "Load < 200ms".
No Implementation: PRD = "What", Implementation Plan = "How".

References

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.