prd-development

A PRD captures problem framing, user research synthesis, solution definition, and success criteria. Standard sections include executive summary, problem statement, personas, strategic context, solution overview, success metrics, user stories, out-of-scope, dependencies, risks, and open questions.

Structure a PRD using an eight-phase workflow that enforces a reusable template with frontmatter, producing phase-specific outputs like problem statements with evidence, personas, story maps, and epic hypotheses to align stakeholder scope and measurable outcomes.

Define success metrics and user stories by working through the dedicated PRD phases that prompt for measurable outcomes and story map artifacts, ensuring each epic hypothesis ties back to the problem statement and strategic context captured earlier in the document.

Yes, the Skill enforces a reusable frontmatter-based PRD template that standardizes structure across cross-functional initiatives, ensuring consistent capture of scope, constraints, risks, dependencies, and open questions from executive summary to delivery.

Document problem statements with evidence by following the phase-specific workflow that prompts for user research synthesis, artifact orchestration, and strategic context collection, ensuring all problem framing is grounded in measurable outcomes and stakeholder alignment.

Avoid using the structured eight-phase PRD workflow for rapid prototyping or single-feature tweaks where a full living document with executive summary, personas, and dependency tracking would create unnecessary overhead for small-scale product management tasks.