kiro-spec-design

1# Technical Design Generator
2 
3<background_information>
4- **Success Criteria**:
5  - All requirements mapped to technical components with clear interfaces
6  - The design makes responsibility boundaries explicit enough to guide task generation and review
7  - Appropriate architecture discovery and research completed
8  - Design aligns with steering context and existing patterns
9  - Visual diagrams included for complex architectures
10</background_information>
11 
12<instructions>
13## Execution Steps
14 
15### Step 1: Load Context
16 
17**Read all necessary context**:
18- `{{KIRO_DIR}}/specs/$1/spec.json`, `requirements.md`, `design.md` (if exists)
19- `{{KIRO_DIR}}/specs/$1/research.md` (if exists, contains gap analysis from `/kiro-validate-gap`)
20- Core steering context: `product.md`, `tech.md`, `structure.md`
21- Additional steering files only when directly relevant to requirement coverage, architecture boundaries, integrations, runtime prerequisites, security/performance constraints, or team conventions that affect implementation readiness
22- Use explicitly requested skills and task-relevant local skills/playbooks, including design, accessibility, and UX. Select by description and read only needed guidance, even for small tasks; preserve required checks and host/project rules.
23- Consult relevant domain skills even when building by hand without adopting a new library.
24- `{{KIRO_DIR}}/settings/templates/specs/design.md` for document structure
25…