domains / families / software-engineering / kiro-debug

kiro-debug

authentic

Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.

When to use

• Implementer reports `BLOCKED`
• Reviewer rejection repeats after remediation
• Validation fails unexpectedly
• A task appears to conflict with runtime or platform reality
• The same failure survives more than one attempted fix

When not to use

• Speculate about fixes before gathering evidence
• Patch generator for guess-first debugging
• Propose a multi-fix shotgun plan
• Propose brute-force code fix as substitute for revising tasks.md

Skill page

Source