| name | prd-authoring |
| description | Standard for authoring product PRDs in docs/prd/: state the problem, users, requirements, and success; assign PRD-{AREA}-{NN} IDs; link down to specs. |
| version | 1.0.0 |
| category | documentation |
| agent_types | ["product","product-owner","pm"] |
| tags | ["prd","product","requirements","authoring","standards"] |
| effort | medium |
| user-invocable | true |
| progressive_disclosure | {"entry_point":{"summary":"Author product PRDs in docs/prd/ using the PRD-{AREA}-{NN} grammar, a product-owned template (problem, users, requirements, acceptance, metrics), and a product lifecycle. PRDs are realized by engineering specs.","when_to_use":"When defining a product problem and its requirements, creating a docs/prd/{area}.md file, adding PRD-{AREA}-{NN} requirements, running product/user/market research, or mapping requirements to implementing specs.","quick_start":"1. Read docs/prd/README.md for ID grammar 2. Pick/create the area file from TEMPLATE.md 3. State problem, users, requirements 4. Add acceptance criteria + success metrics 5. Fill the Linked Specs table"},"references":["prd-template.md","prd-research-practices.md","prd-lifecycle.md","prd-to-spec-linkage.md","ia-and-categories.md"]} |
PRD Authoring
Overview
This skill is the agent-facing entry point to the Product PRD Standard: how to write
Product Requirements Documents in docs/prd/. A PRD answers what problem, for which users,
what requirements, and what success looks like — and is owned by Product (Product Owner /
PM).
It has a distinct engineering companion — keep the roles separate:
prd-authoring (this skill) = authoring product PRDs. State the problem, target users,
goals, user stories, requirements, acceptance criteria, and success metrics; assign stable
PRD-{AREA}-{NN} IDs; run product/user/market research; map requirements down to implementing
specs.spec-authoring = engineering specs (a separate, engineering-owned standard —
docs/specs/, SPEC-{SUBSYSTEM}-{NN}~{rev}). Specs implement PRD requirements.spec-linked-docs = traceability between specs and source code.
PRD ≠ SPEC. A PRD is a product requirements doc (PRD-{AREA}-{NN}, in docs/prd/,
owned by Product). A SPEC is an engineering behavior contract (SPEC-{SUBSYSTEM}-{NN}~{rev},
in docs/specs/, owned by Engineering). A PRD requirement is realized by one or more
specs; list them in the Linked Specs table. Do not put inputs/outputs/error contracts in a
PRD — that is the spec's job.
Full standard: docs/prd/README.md.
This skill orients and links; README.md is the authoritative, portable standard, and
docs/prd/TEMPLATE.md is the copy-pasteable document.
Use this skill, do not duplicate it. SKILL.md is a concise router. The detailed rules live
in docs/prd/README.md and the five reference files below. Read the reference you need.
When to Use
- Defining a product problem and turning it into stable requirements.
- Creating a new
docs/prd/{area}.md file for a product area.
