create-prd

To turn user discovery notes into a PRD, provide interview transcripts and design artifacts to generate a structured prd.md. This document grounds validated user insights into concrete specifications including scope, success metrics, and non-functional requirements.

A PRD should include Contacts, Problem statements, Hypothesis, User Stories anchored to Jobs-To-Be-Done, Design, Scope, Success Metrics, and Non-Functional Requirements. This structure separates validated user problems from technical implementation details.

Writing user stories anchored to Jobs-To-Be-Done requires deriving JTBD from validated discovery artifacts like user interviews. The PRD traces these stories back to original evidence such as user quotes and impact counts to ensure traceability.

You can generate a PRD for both greenfield and brownfield initiatives. The process evaluates existing discovery artifacts and flags any gaps where discovery is incomplete, ensuring the resulting prd.md is grounded in validated evidence.

When discovery artifacts are incomplete, the PRD generation process flags those specific discovery gaps. It ensures traceability to evidence like quotes and impact counts, highlighting areas lacking validated user insights before finalizing the prd.md.