kiro-debug

To find the root cause of an implementation failure, collect failure symptoms, error messages, and failing command output to guide a deterministic investigation spanning local runtime, configuration, and external documentation.

Troubleshooting failed remediation cycles requires structured problem framing that applies root-cause-first debugging to systematically gather evidence across logs and runtime state, producing an actionable fix plan and verification steps to unblock the task.

Debugging blocked tasks with validation failures involves systematic evidence gathering and structured problem framing to identify the root cause, then producing a structured fix plan, verification steps, and next actions to unblock progress.

Yes, root-cause debugging spans local runtime, configuration, and external documentation to investigate implementation failures, systematically gathering evidence across logs, runtime state, and environment to identify the exact cause.

A root-cause investigation produces structured ROOT_CAUSE, CATEGORY, FIX_PLAN, VERIFICATION, NEXT_ACTION, and CONFIDENCE outputs, along with NOTES for reproducibility to ensure clear handoffs and unblock progress.

Use systematic root-cause debugging when an implementer is blocked, verification fails, or remediation cycles repeat, applying structured problem framing and evidence gathering to deterministically identify the exact cause rather than guessing.