prd-writing

A PRD structures product ideas into documented requirements that teams can execute against. Use initial requirements as input, apply a PRD template covering user stories, acceptance criteria, priorities, and KPIs, then produce a review-ready document that clarifies success metrics and keeps stakeholders aligned.

PRDs need KPI definitions and success metrics alongside functional requirements. Include user stories with acceptance criteria, priority levels, non-functional requirements, and optional CLI interfaces. This ensures teams understand not just what to build, but how to measure whether it worked.

Start with initial-requirements.md documenting your raw ideas. Apply a PRD template with structured sections for scope, user stories, acceptance criteria, priorities, KPIs, and constraints. The result is a baseline document others can reference and execute against without ambiguity.

PRD templates provide consistent structure across projects. The template accommodates user stories, acceptance criteria, KPI definitions, and non-functional requirements for most product work. Include CLI interface specifications when applicable to your project type.

Initial requirements capture raw ideas and goals; a PRD formalizes those into structured sections with user stories, measurable success criteria, priorities, and acceptance criteria. The PRD becomes the authoritative specification teams reference during execution.