菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
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.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
| 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 | reproduce | debug | reflect-issue |
| 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.