kiro-debuglisted

# kiro-debug ## Overview This 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. ## When to Use - Implementer reports `BLOCKED` - Reviewer rejection repeats after remediation - Validation fails unexpectedly - A task appears to conflict with runtime or platform reality - The same failure survives more than one attempted fix Do not use this skill to speculate about fixes before gathering evidence. ## Inputs Provide: - Exact failure symptom or blocker statement - Error messages, stack trace, and failing command output - Current `git diff` or summary of uncommitted failed changes - Task brief: what was being built - Reviewer feedback, if the failure came from review rejection - Relevant spec file paths (`requirements.md`, `design.md`) - Relevant requirement/design section numbers - Relevant `## Implementation Notes` - Runtime or environment constraints already known ## Outputs Return: - `ROOT_CAUSE` - `CATEGORY` - `FIX_PLAN` - `VERIFICATION` - `NEXT_ACTION: RETRY_TASK | BLOCK_TASK | STOP_FOR_HUMAN` - `CONFIDENCE: HIGH | MEDIUM | LOW` - `NOTES` Use the language specified in `spec.json`. ## Method ### 1. Read the Error Carefully Extract: - Exact error text - Stack trace or failure location - The command that produced the failure - Whether the failure is deterministic or intermittent ### 2. Inspect L