What problem does it solve? Teams often jump from a rough basic design straight into coding, which leads to invented schemas, undocumented assumptions, and mismatches between documentation and actual code. This Skill turns an approved BASIC_DESIGN.md into a precise, implementable DETAIL_DESIGN.md that planning can consume safely. ## Core Features & Use Cases - Doc reality check: Re-verifies documentation claims against actual code before writing contracts, and stops to ask the user when blocking mismatches appear. - Structured design artifacts: Produces contracts (HTTP/RPC/events/CLI), data models with known/inferred confidence labels, sequences for happy and error paths, validation rules, operations, and optional client mapping. - Assumption and gap tracking: Records assumptions with confirmation status and lists gaps instead of inventing missing details, then hands off explicitly to planning. - Use Case: After agreeing on feature boundaries in BASIC_DESIGN.md, run this Skill to produce a DETAIL_DESIGN.md with verified API contracts, a confidence-labeled data model, Mermaid sequence diagrams, and a clean handoff to the planning stage. ## Quick Start Use the detail-design skill to turn my BASIC_DESIGN.md into a DETAIL_DESIGN.md with verified contracts, data model, and sequences before planning.