SPM
Diagrams · Stage

PRD ↔ Spec

What it's for vs. how it's built — same artifact, two voices.

PRD ↔ Spec — same artifact, two voicesPRD — user voice"what it's for"Personas + JTBDUser outcomes (3–5)Acceptance scenarios (Given/When/Then)Out-of-scope listOpen questionsSpec — engineering voice"how it's built"Data model + ERDAPI contract (OpenAPI / tRPC)Acceptance tests (executable)Non-functional reqs (perf, sec, SLOs)Migration / rollback planThey live next to each other in the repo. If they disagree — spec wins for code, PRD wins for review.
What it shows

The PRD names the user outcomes; the spec names the interfaces, data shapes, and acceptance tests. They live next to each other in the repo. If they disagree, the spec wins for code and the PRD wins for review.

Where it fits

Stage prd in the master Ultimate AI PM workflow.

Run by the SPM Agent. Configured per project.