kiro-debug

Root-cause debugging with evidence consolidates runtime state, error messages, and external references to identify why software implementations fail. It triangulates local inspection with documentation research to pinpoint deterministic causes when remediation does not converge.

Structured root-cause analysis requires exact failure symptoms, error messages, stack traces, failing commands, current git diff, task brief, reviewer feedback, and relevant spec or design references to investigate the root cause accurately and reproducibly.

Evidence-based debugging is applicable when an implementer is blocked, verification fails, or remediation does not converge across repeated attempts. It guides engineers through structured root-cause analysis combining local evidence, runtime checks, and external references.

No, this approach is not a patch generator. It emphasizes evidence-based diagnosis and reproducibility, focusing on structured root-cause analysis and identifying why failures occur rather than automatically producing code fixes.

Root-cause debugging integrates external documentation and issue research to triangulate the cause of failures. By combining local runtime and config inspection with external references, it supports deterministic debugging workflows across repeated remediation attempts.

The best way to debug repeatedly failing verification is consolidating evidence, runtime state, and external references for structured root-cause analysis. This approach ensures deterministic debugging workflows across multiple remediation attempts to converge on the actual cause.