Agent-skills-standard common-product-requirements

Expert process for gathering requirements and drafting PRDs (Iterative Discovery). Use when creating a PRD, speccing a new feature, or clarifying requirements. (triggers: PRD.md, specs/*.md, create prd, draft requirements, new feature spec)

install

source · Clone the upstream repo

git clone https://github.com/HoangNguyen0403/agent-skills-standard

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/HoangNguyen0403/agent-skills-standard "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.github/skills/common/common-product-requirements" ~/.claude/skills/hoangnguyen0403-agent-skills-standard-common-product-requirements-57af79 && rm -rf "$T"

manifest: .github/skills/common/common-product-requirements/SKILL.md

source content

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".