kiro-spec-design

1# kiro-spec-design Skill
2 
3## Core Mission
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 
11## Execution Steps
12 
13### Step 1: Gather Context
14 
15Reuse steering/spec context already available from conversation; load missing context below.
16Select skills for the current task even when steering/spec context is already available:
17- `{{KIRO_DIR}}/specs/{feature}/spec.json`, `requirements.md`, `design.md` (if exists)
18- `{{KIRO_DIR}}/specs/{feature}/research.md` (if exists, contains gap analysis from `/kiro-validate-gap`)
19- Core steering context: `product.md`, `tech.md`, `structure.md`
20- 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
21- 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.
22- Consult relevant domain skills even when building by hand without adopting a new library.
23…