What problem does it solve? Turning raw product shaping notes into a structured Product Requirements Document is error-prone: sections get missed, implementation details leak into product-level writing, and gaps get silently invented. This Skill generates a schema-conformant prd.md from shape-notes.md, routing every missing piece to an Open Questions section instead of fabricating content. ## Core Features & Use Cases - Auto-routing by context type: Detects greenfield (10-section template) versus brownfield (11-section template) from frontmatter or cwd signals like git history and lockfiles. - Thin-input heuristic: Scores input notes on a 0-4 signal checklist (checkpoint block, FR-NNN requirements, Given/When/Then stories, business rule) and warns before generating from weak input. - Pre-write self-review: Validates section order, frontmatter keys, and lints for technical leak (vendor names, schema notation, transport protocols) before writing to disk, aborting on drift. - Collision-safe writes: Offers versioned saves (prd-vN.md) instead of overwriting an existing PRD. - Use Case: After running /10x-shape on a new product idea, invoke this Skill to produce context/foundation/prd.md with all gaps explicitly listed under Open Questions for human resolution. ## Quick Start Run /10x-prd after creating shape-notes.md with /10x-shape to generate a schema-conformant PRD at context/foundation/prd.md.
