kiro-debug

1# kiro-debug
2 
3<background_information>
4This skill is for fresh-context root cause investigation. It combines local evidence, runtime/config inspection, and external documentation or issue research when available. It is not a patch generator for guess-first debugging.
5</background_information>
6 
7<instructions>
8## When to Use
9 
10- Implementer reports `BLOCKED`
11- Reviewer rejection repeats after remediation
12- Validation fails unexpectedly
13- A task appears to conflict with runtime or platform reality
14- The same failure survives more than one attempted fix
15 
16Do not use this skill to speculate about fixes before gathering evidence.
17 
18## Inputs
19 
20Provide:
21- Exact failure symptom or blocker statement
22- Error messages, stack trace, and failing command output
23- Current `git diff` or summary of uncommitted failed changes
24- Task brief: what was being built
25- Reviewer feedback, if the failure came from review rejection
26- Relevant spec file paths (`requirements.md`, `design.md`)
27- Relevant requirement/design section numbers
28- Relevant `## Implementation Notes`
29- Runtime or environment constraints already known
30 
31## Outputs
32 
33Return:
34- `ROOT_CAUSE`
35- `CATEGORY`
36- `FIX_PLAN`
37- `VERIFICATION`
38- `NEXT_ACTION: RETRY_TASK | BLOCK_TASK | STOP_FOR_HUMAN`
39- `CONFIDENCE: HIGH | MEDIUM | LOW`
40- `NOTES`
41 
42Use the language specified in `spec.json`.
43 
44## Method
45 
46### 1. Read the Error Carefully
47Extract:
48- Exact error text
49- Stack trace or failure location
50- The command that produced the failure
51…