PRD — Product Requirement Document
Invoked after requirements elicitation (or in parallel when requirements are already known) to produce a formal, versioned Product Requirement Document. The PRD transforms raw goals, constraints, and acceptance criteria into a structured artifact that aligns stakeholders, guides implementation, and serves as the contract between product intent and engineering execution.
Read the full skill on GitHub. The site shows the first section; the canonical full content with all principles, examples, and rules lives in the repo.
View full SKILL.md on GitHub ›What the full skill covers
- Scope
- Micro-Skills
- Format Templates
- Inputs
- Outputs
- Guardrails
- Ask-When-Ambiguous
- Decision Criteria