kiro-spec-tasks

1# Implementation Tasks Generator
2 
3<background_information>
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</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`
19- `{{KIRO_DIR}}/specs/$1/tasks.md` (if exists, for merge mode)
20- Core steering context: `product.md`, `tech.md`, `structure.md`
21- Additional steering files only when directly relevant to requirements coverage, design boundaries, runtime prerequisites, or team conventions that affect task executability
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 
24**Validate approvals**:
25- If `-y` flag provided: Auto-approve requirements and design in spec.json. Tasks approval is also handled automatically in Step 4.
26- Otherwise: Verify both approved (stop if not, see Safety & Fallback)
27- Determine sequential mode based on presence of `--sequential`
28 
29### Step 2: Generate Implementation Tasks
30 
31**Load generation rules and template**:
32…