kiro-debug

by gotalab3.7k

Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add gotalab/cc-sdd --skill kiro-debug -a cursor -y

Download skill tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-debug/SKILL.md on GitHub

Related skills

View all

Questions

How do I install kiro-debug?: Download tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-debug/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does kiro-debug live?: The publisher keeps it at https://github.com/gotalab/cc-sdd.
Which agents can use kiro-debug?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: kiro-debug description: Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.

kiro-debug

<background_information> 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. </background_information>

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

Rationalization	Reality
“This probably just needs a quick patch”	Patch-first debugging creates rework.
“Let’s try a few fixes”	Multi-fix guessing hides root cause.
“The spec is probably wrong, I’ll adapt it”	Spec conflicts must be surfaced explicitly.
“The docs search is optional”	For runtime/dependency issues, docs and version issues often contain the shortest path to root cause.

kiro-debug

Install

Related skills

Questions

name: kiro-debug description: Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.

kiro-debug

Inputs

Outputs

Method

1. Read the Error Carefully

2. Inspect Local Runtime and Repository State

3. Search the Web if Available

4. Classify the Root Cause

5. Determine the Smallest Safe Next Action

6. Determine Whether the Task Plan Is Still Valid

Critical Rule

Stop / Escalate

Common Rationalizations

Output Format