prd-development

Gather upstream artifacts like a problem statement, proto-personas, lean UX canvas, and user story map, then draft the PRD one section at a time. Ground each section in cited evidence, label gaps as assumptions, and gate with stakeholders after each section rather than writing it alone.

This template uses 14 sections: executive summary, problem statement, personas, strategic context, solution overview, success metrics, user stories, non-functional requirements, technical architecture, ADRs, out of scope, dependencies and risks, open questions, and appendices. Sections 8-10 and 14 can be dropped for small features.

The skill checks for upstream discovery artifacts and stops if none exist, because a PRD written from priors is the failure it prevents. If you insist on proceeding, every unevidenced section is visibly tagged as an assumption rather than presented as fact.

Use ADRs with explicit statuses: Proposed, Accepted, Superseded, or Rejected. A decision that has not been made stays Proposed with a named owner and needed-by date; it is never promoted to Accepted just to make the document look finished.

If you would drop half of the 14 sections, a full PRD is the wrong tool. Use a lighter spec-writing skill for small features where architecture records, appendices, and formal NFR tables add overhead without adding clarity.