kiro-spec-taskslisted

# kiro-spec-tasks Skill ## Core Mission - **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 ## Execution Steps ### Step 1: Gather Context If steering/spec context is already available from conversation, skip redundant file reads. Otherwise, load all necessary context: - `.kiro/specs/{feature}/spec.json`, `requirements.md`, `design.md` - `.kiro/specs/{feature}/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 - Determine execution mode: - `sequential = (sequential flag is true)` **Validate approvals**: - If auto-approve flag (`-y`) is true: 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) ### Step 2: Generate Implementation Tasks - Read `rules/tasks-generation.md` from this skill's directory for principles - Read `rules/tasks-parallel-analysis.md` from this skill's directory for parallel judgement criteria - Read `.kiro/settings/templates/specs/t