Agent-Skills.md

Agent Skills: Product Requirements Expert

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)

UncategorizedID: hoangnguyen0403/agent-skills-standard/common-product-requirements

Repository

hoangnguyen0403/agent-skills-standard
HoangNguyen0403License: Apache-2.0
362103

Install this agent skill to your local

pnpm dlx add-skill https://github.com/HoangNguyen0403/agent-skills-standard/tree/HEAD/.agent/skills/common/common-product-requirements

Skill Files

Browse the full folder contents for common-product-requirements.

Download Skill

Loading file tree…

.agent/skills/common/common-product-requirements/SKILL.md

Skill Metadata

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

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