What problem does it solve? Turning approved requirements into a concrete, implementation-ready technical design is slow and error-prone, often producing vague component boundaries and untraceable requirement coverage. ## Core Features & Use Cases - Discovery-Driven Design: Classifies features as new, extension, or simple addition and runs full, light, or minimal research (including web research and codebase analysis) before designing. - Boundary-First Design Documents: Produces design.md with explicit ownership boundaries, component contracts, file structure plans, Mermaid diagrams, and requirement traceability. - Review Gate: Validates requirements coverage, architecture readiness, and executability with up to two repair passes before finalizing the design. - Use Case: After approving requirements for a new API feature, run the skill to research dependencies, synthesize architecture decisions into research.md, and generate a reviewed design.md ready for task generation. ## Quick Start Run the kiro-spec-design skill on my approved spec to generate the technical design document.
