prd-and-vision
Writing the two structured product documents — a PRD for one capability, and a VISION for the product its capabilities belong to. Covers the guided conversation for each, why their headings decide how content is filed, which sections block the readiness gate, and the filing traps. Use when asked to write, review, or extend a PRD, a product spec, requirements, or a product vision.
Pinned to revision a1094a81fd52, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.