菜单
Walk every review through the same checks in the same order. Use on every Reviewer task; skipping steps is the
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Pick the right worker class for each Issue. Use every time you assign an Issue; wrong routing wastes tokens and creates rework.
Break a Company Goal into 3-10 atomic Issues. Use when a Goal arrives with no pre-existing plan and you need to produce a shippable work list.
Ship the smallest change that solves the Issue. Use on every implementation task; scope creep is the default failure mode of executors.
Run build/test/lint and read the actual output before claiming done. Use on every implementation task, at the end.
Start implementation with a red test. Use on any bugfix or new behavior — not on refactors or style changes.
Report research results in a form other agents can act on. Use at the end of every Explorer session.
| name | methodical-review-checklist |
| description | Walk every review through the same checks in the same order. Use on every Reviewer task; skipping steps is the |
A Reviewer's job is to break the implementation, not to confirm it. The checklist exists so you cannot shortcut past the adversarial steps.
End with VERDICT: PASS / FAIL / PARTIAL. Use PARTIAL only for environment limitations (can't run Docker on this host) — never for "I'm unsure". If you are unsure, that is a FAIL pending clarification.
