kiro-debug

Root-cause debugging identifies the underlying failure in an implementation workflow by combining local evidence, runtime inspection, and documentation to produce a structured remediation report.

When repeated validation failures block implementation, you should perform failure analysis to isolate the root cause and generate a structured fix plan with verification steps to unblock the task.

To stop a remediation loop after repeated rejections, conduct a deeper failure analysis to pinpoint the systemic root cause and generate actionable next steps rather than applying surface-level fixes.

The best way to document failure analysis is to produce a structured root-cause report containing category, fix plan, verification method, next action, and confidence level to guide rapid recovery.

You need a structured root-cause report when an implementer is blocked, a reviewer rejects tasks repeatedly, or validation reveals systematic issues requiring deeper investigation to resolve.

Yes, kiro-debug works without external dependencies to perform failure analysis, though it combines local evidence and runtime inspection with external documentation when needed to determine the root cause.