08 Debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
Install
/plugin marketplace add ai-driven-dev/frameworkThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add ai-driven-dev/framework --skill 08-debuggit clone --depth 1 https://github.com/ai-driven-dev/framework.git /tmp/framework
mkdir -p ~/.claude/skills
cp -r /tmp/framework/plugins/aidd-dev/skills/08-debug ~/.claude/skills/08-debugPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Skill: debug Diagnose and fix issues through structured hypothesis validation, root-cause analysis, and a test-driven fix. ## Actions | # | Action | When to use | | --- | --------------- | ----------------------------------------------------------------------------- | | 01 | `reproduce` | A known bug must be fixed end to end: reproduce, test-driven fix, branch, PR | | 02 | `debug` | Root cause unknown: enumerate hypotheses, validate each, confirm the cause | | 03 | `reflect-issue` | Stuck or prior fixes failed: reopen the search space, instrument logs first | Pick the one action matching the intent; never default to `01`. Triggers like "reproduce and fix" route to `01`, "why does this happen" to `02`, "I'm stuck" or "previous fixes didn't work" to `03`. Ask one question when the intent is ambiguous. Before running an action, read its file in `actions/`, not only the table or assets. ## Transversal rules - One action per run: follow only the matching action file. - Scope each fix to its bug: never bundle drive-by refactors. - Confirm the root cause before fixing; the diagnostic actions stop at a confirmed cause. ## Assets - `assets/task-template.md`: the per-hypothesis tracking file the debug action fills. ## References - `references/mermaid-conventions.md`: the project's Mermaid conventions for the action-path flowchart.
Details
- Skill name
08-debug- Repository
- ai-driven-dev/framework
- Path
plugins/aidd-dev/skills/08-debug/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the 08 Debug skill do?
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
How do I install the 08 Debug skill?
Claude Code plugin: /plugin marketplace add ai-driven-dev/framework. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is 08 Debug popular?
It lives in ai-driven-dev/framework, which has 564 GitHub stars and 65 forks.
Related skills
00 Async Dev
564ai-driven-dev/framework
Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.
00 Init
564ai-driven-dev/framework
Turn AIDD measurement on for a project after explicit consent, stop it, choose to be named on your own measurement, or delete what was measured. Use when the user wants to start or stop measuring what their work consumes, add or remove their name, or forget measured data. Not for answering what a period consumed.
00 Onboard
564ai-driven-dev/framework
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
09 Defect
564ai-driven-dev/framework
Produces or refines a backlog Defect from an observed product mismatch. Use when the user wants to report, assess, link, order, transition, or verify a defect. Not for incident response, debugging, or implementation.
07 Refactor
564ai-driven-dev/framework
Improve code across four axes (cleanup, performance, security, architecture) by scanning and fixing, or applying a pushed audit report. Use when the user wants to refactor, optimize, harden, or remove code. Not for read-only diagnosis or adding tests.
Framework
564ai-driven-dev/framework
Owns the installation record and everything done to a project, under src/contexts/framework/ — the manifest aggregate, and the setup/install/restore/uninstall/doctor orchestration built on top of it. This is the only context allowed to reach `translate` and `distribution`. Use when adding a use-case that touches the manifest, a setup/doctor/sync/uninstall flow, a new top-level CLI orchestration, or a launcher that runs an external binary (kanban-shaped). Do NOT use for a tool's own profile or capability classes — use `tools`. Do NOT use for the translation pipeline — use `translate`. Do NOT us
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.