kiro-spec-tasks

1# kiro-spec-tasks Skill
2 
3## Core Mission
4- **Success Criteria**:
5  - All requirements mapped to specific tasks
6  - Tasks properly sized (1-3 hours each)
7  - Clear task progression with proper hierarchy
8  - Natural language descriptions focused on capabilities
9  - A lightweight task-plan sanity review confirms the task graph is executable before `tasks.md` is written
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`
18- `{{KIRO_DIR}}/specs/{feature}/tasks.md` (if exists, for merge mode)
19- Core steering context: `product.md`, `tech.md`, `structure.md`
20- Additional steering files only when directly relevant to requirements coverage, design boundaries, runtime prerequisites, or team conventions that affect task executability
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 
23- Determine execution mode:
24  - `sequential = (sequential flag is true)`
25 
26**Validate approvals**:
27- If auto-approve flag (`-y`) is true: Auto-approve requirements and design in spec.json. Tasks approval is also handled automatically in Step 4.
28…