What problem does it solve? Turning raw product notes into a structured Product Requirements Document is slow and error-prone, and hand-written PRDs often invent missing details or leak implementation decisions. This Skill converts shape-notes.md (or raw notes) into a schema-locked prd.md, routing every gap to an Open Questions section instead of fabricating content. ## Core Features & Use Cases - Auto-routing by context type: Detects greenfield (10-section) vs brownfield (11-section) templates from frontmatter or cwd signals like git history and lockfiles. - Thin-input heuristic: Scores input on 4 signals (checkpoint block, FR-NNN requirements, Given/When/Then stories, business rule) and warns before generating from weak notes. - Schema self-review with technical-leak lint: Validates section order, frontmatter keys, and scans for forbidden vocabulary (vendor names, schema notation, transport protocols) before any disk write. - Collision-safe writes: Offers versioned saves (prd-vN.md) instead of overwriting existing PRDs. - Use Case: After running /10x-shape on a new product idea, invoke this Skill to produce context/foundation/prd.md with all unresolved gaps listed as numbered Open Questions, ready for downstream tech-stack selection. ## Quick Start Run /10x-prd with the path to your shape-notes file to generate a schema-conformant PRD at context/foundation/prd.md.