AGENT SKILL
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)
适用职业产品经理
- License 许可
- MIT
- 最近更新
- 2026-06-24
- Stars
- ★ 67
- Forks
- 24
01 前言 Front Matter
- name
- common-product-requirements
- description
- 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)
02 资源文件 2
- 参考文档evals/evals.json10.6 KB
- 参考文档references/swag-cli.md4.5 KB
03 SKILL.md 正文
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 Stateis 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".
