# Product Requirements

Standardize PRD discovery and drafting for product scope, user outcomes, requirement...

- Repository: https://github.com/HoangNguyen0403/agent-skills-standard (582 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add HoangNguyen0403/agent-skills-standard --skill product-requirements -g -a claude-code -y`
Codex: `npx skills add HoangNguyen0403/agent-skills-standard --skill product-requirements -g -a codex -y`
Cursor: `npx skills add HoangNguyen0403/agent-skills-standard --skill product-requirements -g -a cursor -y`
Gemini CLI: `npx skills add HoangNguyen0403/agent-skills-standard --skill product-requirements -g -a gemini-cli -y`

## Description

Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Product Requirements Expert

## **Priority: P0 (CRITICAL)**

**Role**: PM-owned product spec owner. Define the product "What" before technical design or implementation.

## 1. Discovery Phase (Iterative)

- **Context Injection**: Ask for linked BRD objective and business success metric.
- **Delivery Mode**: Carry `delivery_mode: brief | standard | extended` separately from `snc_tier`. `brief` applies only to approved low-risk, nonsensitive work carrying outcome, scope fence, owner, observable criteria, approval reference, and verification lane; it mints no new formal IDs and needs no separate PRD/SRS. `standard` uses this focused PRD; `extended` adds risk-triggered detail. Missing mode is a routing decision from approved evidence and risk, never automatic brief permission; a sensitive change is always `extended` with its technical design and human gate.
- **Conditional Sections**: Fill the core sections; add an extension only when its trigger applies. Omit irrelevant sections instead of writing repeated "none" paragraphs; omitting an applicable extension is an owned blocker.
- **Scope Gate**: For substantial scope, load [requirements modeling](references/requirements-modeling.md) for decomposition stop rules and completeness review; each in-scope leaf maps to a `REQ-*`/`AC-*` or owned gap.
- **Question Discipline**: Draft from supplied evidence; ask at most 3 consequential questions per round (`common-decision-discipline`) with recommended defaults and 2, 3 concrete options. Never re-ask settled facts.

## 2. Drafting Phase (System of Record)

The rest: https://github.com/HoangNguyen0403/agent-skills-standard/blob/HEAD/.agents/skills/product-management/product-requirements/SKILL.md