kiro-spec-tasks

# Implementation Tasks Generator <background_information> - **Success Criteria**: - All requirements mapped to specific tasks - Tasks properly sized (1-3 hours each) - Clear task progression with proper hierarchy - Natural language descriptions focused on capabilities - A lightweight task-plan sanity review confirms the task graph is executable before `tasks.md` is written </background_information> <instructions> ## Execution Steps ### Step 1: Load Context **Read all necessary context**: - `{{KIRO_DIR}}/specs/$1/spec.json`, `requirements.md`, `design.md` - `{{KIRO_DIR}}/specs/$1/tasks.md` (if exists, for merge mode) - Core steering context: `product.md`, `tech.md`, `structure.md` - Additional steering files only when directly relevant to requirements coverage, design boundaries, runtime prerequisites, or team conventions that affect task executability **Validate approvals**: - If `-y` flag provided: Auto-approve requirements and design in spec.json. Tasks approval is also handled automatically in Step 4. - Otherwise: Verify both approved (stop if not, see Safety & Fallback) - Determine sequential mode based on presence of `--sequential` ### Step 2: Generate Implementation Tasks **Load generation rules and template**: - Read `rules/tasks-generation.md` from this skill's directory for principles - If `sequential` is false: Read `rules/tasks-parallel-analysis.md` from this skill's directory for parallel judgement criteria - Read `{{KIRO_DIR}}/settings/templates/...