What problem does it solve? When implementation tasks fail, verification breaks, or repeated fixes do not converge, teams often fall into guess-first patching that hides the real cause. This Skill enforces evidence-driven root cause analysis before any fix is proposed, preventing rework and premature escalation. ## Core Features & Use Cases - Root Cause Classification: Categorizes failures into ten classes such as MISSING_DEPENDENCY, RUNTIME_MISMATCH, CONFIG_GAP, and SPEC_CONFLICT. - Evidence Gathering Workflow: Reads error output, inspects repository state (package.json, tsconfig, git diff), and searches official documentation and issue trackers when web access is available. - Structured Debug Report: Produces ROOT_CAUSE, FIX_PLAN, VERIFICATION commands, and a NEXT_ACTION decision (RETRY_TASK, BLOCK_TASK, or STOP_FOR_HUMAN) with a confidence level. - Learning Capture: Records generalizable traps into spec learnings and cross-spec pattern files so future specs avoid the same dead ends. - Use Case: An implementer is blocked after two failed remediation attempts on a module import error; this Skill investigates, classifies it as MODULE_FORMAT, and returns a minimal repo-fixable plan. ## Quick Start Invoke the kiro-debug skill with a failure summary such as the exact error message and failing command to receive a root cause analysis and fix plan.
