菜单
Use when encountering test failures, bugs, or unexpected behavior - requires root cause investigation before any fix attempt
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when ready to implement - selects a GitHub Issue, creates worktree, implements with TDD, verifies, reviews 5x, and creates PR. Numeric argument (e.g. pick-issue 3) is the issue number, not a parallelism count.
Use when you want to be exhaustively questioned about a plan or design until shared understanding is reached - asks one question at a time, traverses the design tree, and proposes a recommended answer for each question
Use to delegate all hands-on work to Codex - plan-writing, implementation, and refactoring. Opus reads, thinks, reviews, and writes docs only.
Use after a PR is opened and you want it merged - waits for CI to pass, marks draft PRs ready, removes the worktree, then merges and cleans up
Use when starting new feature work, adding functionality, or modifying behavior - explores design before implementation, creates plan, PR, and GitHub Issues
Use when creating implementation plans from specs or design documents - decomposes work into concrete TDD tasks with file paths and code examples
| name | debugging |
| description | Use when encountering test failures, bugs, or unexpected behavior - requires root cause investigation before any fix attempt |
Systematic root cause investigation before attempting fixes. No guessing, no random changes.
Rule: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
The investigation and the root-cause hypothesis above are Opus's read-and-think work. The fix itself is code, so Opus does not write it — delegate the edits to Codex (via the codex skill), carrying the root cause and the hypothesis down. Opus reviews the result.
After 3 failed fix attempts, stop and escalate:
