What problem does it solve? Starting implementation without a documented design leads to inconsistent deliverables, rework when design errors surface late, and lost rationale for architectural choices. This Skill standardizes what a design document must contain so any engineer or AI agent produces the same structure. ## Core Features & Use Cases - Mode-based deliverables: Defines which artifacts (class diagrams, ER diagrams, API specs, non-functional design tables) are required per workflow mode (light, operation, legacy-refactor, standard) and per touched area. - Structured design template: Provides a document template with sections for components, structure, data, interface contracts, decisions, and test design, each mapped to downstream implementation tasks. - Design review workflow: Guides issuing a design Pull Request before implementation for standard-mode changes, including internal consistency checks across document sections. - Use Case: When adding a new API with persistent storage, use this Skill to produce an ER diagram, table definitions, an OpenAPI contract, and a decision record before writing any code. ## Quick Start Use the design skill to write the design document for this change, covering the data structures, interface contracts, and key decisions.