What problem does it solve? Teams often jump from a rough discussion straight into coding or detailed contracts, only to discover later that the documentation did not match the actual codebase. This Skill turns an approved DISCUSSION.md recommendation into a verified system-level design, catching doc-versus-code mismatches before architecture decisions are locked in. ## Core Features & Use Cases - Doc reality check: Compares up to five vital design claims against real repository code, assigning verdicts (Match, Mismatch, Stale, Unknown) and blocking design work until conflicts are resolved with the user. - System-level design artifact: Produces a BASIC_DESIGN.md covering goal, architecture overview, components, happy-path flows, data ownership, external interfaces, and open questions, with a Mermaid diagram when it clarifies boundaries. - Structured handoff: Ends with an explicit next-step pointer to detail-design, research, or investigate so downstream work continues without re-asking questions. - Use Case: After stakeholders approve a direction for a new API feature, run this Skill to verify the wiki spec against the actual modules, define component boundaries and data ownership, and hand off a BASIC_DESIGN.md ready for detail design. ## Quick Start Ask the agent to use the basic-design skill on the approved DISCUSSION.md to produce a BASIC_DESIGN.md with a doc reality check before any architecture work.
