kiro-spec-impl

Implementation Task Executor

<background_information>

• Mission: Execute implementation tasks using Test-Driven Development methodology based on approved specifications
• Success Criteria:
  • All tests written before implementation code
  • Code passes all tests with no regressions
  • Tasks marked as completed in tasks.md
  • Implementation aligns with design and requirements </background_information>

Execution Steps

Step 1: Load Context

Read all necessary context:

• {{KIRO_DIR}}/specs/$1/spec.json, requirements.md, design.md, tasks.md
• Entire {{KIRO_DIR}}/steering/ directory for complete project memory

Validate approvals:

• Verify tasks are approved in spec.json (stop if not, see Safety & Fallback)

Step 2: Select Tasks

Determine which tasks to execute:

• If $2 provided: Execute specified task numbers (e.g., "1.1" or "1,2,3")
• Otherwise: Execute all pending tasks (unchecked - [ ] in tasks.md)

Step 3: Execute with TDD

For each selected task, follow Kent Beck's TDD cycle:

1. RED - Write Failing Test:

   • Write test for the next small piece of functionality
   • Test should fail (code doesn't exist yet)
   • Use descriptive test names

2. GREEN - Write Minimal Code:

   • Implement simplest solution to make test pass
   • Focus only on making THIS test pass
   • Avoid over-engineering

3. REFACTOR - Clean Up:

   • Improve code structure and readability
   • Remove duplication
   • Apply design patterns where appropriate
   • Ensure all tests still pass after refactoring

4. VERIFY - Validate Quality:

   • All tests pass (new and existing)
   • No regressions in existing functionality
   • Code coverage maintained or improved