What problem does it solve? Turning approved requirements into a concrete, reviewable technical design is slow and error-prone, especially when the design must align with existing codebase patterns, steering context, and project memory. This Skill automates that translation, producing a design.md with explicit boundaries, file structure plans, and traceability back to requirements. ## Core Features & Use Cases - Discovery-driven design: Classifies the feature (greenfield, extension, simple addition, complex integration) and runs full, light, or minimal discovery, including web research and codebase analysis via subagents. - Boundary-first design documents: Generates design.md with explicit ownership boundaries, file structure plans, testing strategy, and requirement traceability IDs. - Review gate and learning capture: Runs a bounded design review gate before finalizing, and records directional user feedback as durable decisions and learnings in the spec directory. - Use Case: After approving requirements for a notifications feature, run the design phase to produce an architecture document with component interfaces, integration points, and a file-by-file implementation plan ready for task generation. ## Quick Start Ask the agent to generate the technical design for a feature whose requirements are already approved, for example by running the kiro-spec-design command with the feature name.
