From superpowers
Use immediately after writing-plans completes and a plan document exists — sends the plan to Codex for independent external review before implementation begins
How this skill is triggered — by the user, by Claude, or both
Slash command
/superpowers:codex-plan-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
After `writing-plans` produces a plan, send it to Codex for independent review.
After writing-plans produces a plan, send it to Codex for independent review.
Codex runs externally and returns only its findings — a second opinion before you commit to implementation.
Announce at start: "I'm using the codex-plan-review skill to get an external review of the plan from Codex."
docs/superpowers/plans/ or the user's preferred plan location/codex:rescue --wait with the plan content and review instructionswriting-plans skill again with the original spec + Codex feedback as additional contextUse this exact pattern to invoke /codex:rescue:
/codex:rescue --wait Review this implementation plan for risks, gaps, missing edge cases, incorrect assumptions, and overlooked dependencies. Be specific about what's wrong and suggest concrete fixes. Here is the plan:
[full plan content]
- Do NOT skip the Codex review step. The whole point of this skill is external validation.
- Do NOT modify or summarize Codex's output. Present it verbatim.
- Do NOT auto-apply feedback without human partner confirmation.
If /codex:rescue fails or Codex is not installed:
/codex:setup to install, or skip this review."Once the final plan is confirmed (with or without Codex feedback), the next skill in the pipeline is subagent-driven-development or executing-plans.
npx claudepluginhub sikwon0704-cmyk/superpowers --plugin superpowersProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.