メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ai-driven-dev/framework --skill 08-debugコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
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.
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.
Capture durable project learnings. Use when the user wants to remember, record, or formalize a decision, convention, lesson, pitfall, reusable workflow, or review finding. Not for preferences or temporary notes.
| name | 08-debug |
| description | 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. |
| argument-hint | bug | symptom |
| model | opus |
Diagnose and fix issues through structured hypothesis validation, root-cause analysis, and a test-driven fix.
| # | 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.
assets/task-template.md: the per-hypothesis tracking file the debug action fills.references/mermaid-conventions.md: the project's Mermaid conventions for the action-path flowchart.