Diagnose implementation failures using root-cause-first debugging with structured debug reports.
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-debug-j5ik2o
Please help me install this Agent Skill. Skill: kiro-debug Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-debug Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-debug-j5ik2o
High-intent search queries and answers about installing and using this skill.
Start with the exact error text, stack trace, and failing command, then inspect repository state such as package.json, tsconfig, and git diff. Classify the root cause before proposing any fix, and produce the smallest safe fix plan with verification commands.
Root-cause-first debugging gathers evidence from errors, runtime config, and documentation before proposing fixes, rather than trying multiple patches. It prevents multi-fix guessing that hides the true cause and creates rework.
Escalate with STOP_FOR_HUMAN when the blocker requires product or requirements decisions, external credentials, unavailable hardware or services, or re-scoping due to a spec or platform conflict. Repo-fixable issues inside the current task plan should not be escalated.
Repeated failures usually mean the true root cause was never identified, such as a runtime mismatch, missing dependency, or task ordering problem. Patch-first attempts treat symptoms, so the same failure survives each remediation.
Yes, spec conflicts are an explicit root cause category. When the failure stems from contradictory requirements or design, the report surfaces the conflict directly instead of proposing a code workaround.
ryu-satoDiagnose software implementation failures by consolidating evidence and runtime state.
shakedfbAggregate task stacks, queues, inbox pressure, health, and goals to generate one executable next action.
ByronWilliamsCPADiagnose failing pytest tests using root-cause-first analysis before changing application code.
swat9013Diagnoses software errors by analyzing logs, stack traces, and reproduction steps.
