kiro-debug

Isolate implementation failure root causes via runtime inspection and documentation.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/miyamo2/braider --skill kiro-debug-miyamo2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-debug
Source: https://github.com/miyamo2/braider/tree/main/.gemini/skills/kiro-debug
Command: npx skills add https://github.com/miyamo2/braider --skill kiro-debug-miyamo2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and resolve implementation failures by combining local evidence, runtime/config inspection, and external documentation. It does not generate patches or fixes, but guides precise root-cause analysis to unblock progress.

Core Features & Use Cases

  • Fresh-context investigation that aggregates failure signals, stack traces, environment details, and relevant docs.
  • Non-patching diagnostic workflow focused on identifying root causes and actionable next steps.
  • Outputs structured triage data ready for escalation: ROOT_CAUSE, CATEGORY, FIX_PLAN, VERIFICATION, NEXT_ACTION, and CONFIDENCE.

Quick Start

Provide the exact failure symptoms, environment details, and affected components to begin root-cause-first debugging.

Frequently Asked Questions about kiro-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a software failure when my debugging cycle is stuck?

Root-cause debugging isolates implementation failures by aggregating local evidence, runtime inspection, and external documentation to unblock stalled work. It outputs structured triage data including the root cause, category, fix plan, and confidence level.

What is the best way to troubleshoot a blocked implementation when validations fail?

Troubleshooting blocked implementations involves aggregating failure signals, stack traces, and environment details to pinpoint the exact failure point. This diagnostic workflow generates a structured fix plan and verification steps without directly patching code.

Can I use a root-cause-first approach to generate code patches automatically?

No, a root-cause-first diagnostic approach intentionally does not generate patches or fixes. Instead, it guides precise failure analysis and outputs an actionable fix plan, verification steps, and next actions for manual implementation.

What information do I need to provide for effective failure analysis and root cause isolation?

Effective failure analysis requires providing exact failure symptoms, environment details, and affected components. This fresh-context investigation aggregates these signals with relevant external documentation to isolate the root cause.

How does a structured debugging workflow handle escalation for unresolved implementation blockers?

A structured debugging workflow handles escalation by generating standardized triage data including ROOT_CAUSE, CATEGORY, FIX_PLAN, VERIFICATION, NEXT_ACTION, and CONFIDENCE. This output ensures clear communication of failure analysis results for downstream resolution.