write-a-prd

To compile a PRD from planning artifacts, the skill reads existing UX, data, and infra decision records on disk, enforcing DEC-NNN traceability for every claim and flagging untraced items as assumptions before output. It transforms scattered grill logs into a single build contract.

Decision-tracing in product requirements documents ensures every claim within the PRD maps directly back to a specific decision ID (DEC-NNN). This mechanism flags untraced claims as assumptions, guaranteeing downstream builders have verifiable rationale without re-interviewing.

You can generate a build-ready PRD without re-interviewing by reading existing decision artifacts from disk. The skill assembles a session-safe, self-contained document that a new agent can read cold, requiring no reliance on prior conversation or implicit context.

To enforce scope discipline when creating buildable stories, the skill applies vertical slicing and anti-rationalization checks. It gates finalization on a prerequisite verification round, ensuring the compiled PRD maintains strict scope discipline for downstream builders.

Before generating a PRD, you need existing decision artifacts on disk, including grill logs, decision indexes, and context files covering UX, data, UI, infra, and competitive research. These records provide the verifiable foundation required for compilation.