菜单
Use for bugs, regressions, failing tests, broken scripts, or mismatches between expected and actual behavior. Start from a concrete anchor, form one falsifiable local hypothesis, make a small grounded fix, and validate immediately.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Local fallback entrypoint for the Superpowers plugin. Use when the user mentions Superpowers, the plugin is unavailable, or you need to route non-trivial engineering work in this repository into the local brainstorming, planning, debugging, and verification skills.
Use before implementing new behavior, refactors with meaningful design choices, or changes that alter user-visible behavior. Clarify intent, propose approaches, write a short spec, and only then transition to planning.
Use when a written plan exists and implementation should proceed in small validated slices. Carry out one plan slice at a time, keep scope tight, validate immediately after edits, and do not drift away from the approved plan without calling it out.
Use when starting non-trivial engineering work in this repository, when the user mentions Superpowers, or when the plugin is unavailable and you need to route the task into the local skill suite before acting.
Use when about to claim something is fixed, complete, passing, reviewed, or ready. Require fresh command output and report the observed result rather than the intended result.
| name | systematic-debugging |
| description | Use for bugs, regressions, failing tests, broken scripts, or mismatches between expected and actual behavior. Start from a concrete anchor, form one falsifiable local hypothesis, make a small grounded fix, and validate immediately. |
Use this skill when behavior is wrong and you need to find the root cause instead of patching symptoms.
The hypothesis should name:
Exit this skill only after fresh validation evidence shows the actual state of the bug or fix.
Before any success claim, route into .claude/skills/verification-before-completion/SKILL.md.
