10x-prd

A product requirements document generated from thin or incomplete notes preserves unknowns as explicit TODOs and numbered open questions rather than fabricating missing requirements, ensuring gaps remain visible for later resolution.

Generating a PRD for an existing product versus a new product triggers automatic context-type routing that detects brownfield change-definition versus greenfield product-definition workflows and applies the correct schema-conformant template.

When product notes lack enough detail for a full PRD, the system applies thin-input safeguards that score completeness, warn about weak inputs, and preserve unknowns as TODOs and numbered open questions without inventing missing requirements.

To ensure your PRD follows a strict schema with correct section ordering and required frontmatter, the system applies pre-write validation against a locked PRD schema before writing the finalized document to the context foundation directory.

You can use shaped notes to write a PRD with collision-safe versioning by routing greenfield or brownfield notes through the schema-locked generation process that validates exact headings and outputs structured markdown.