Plan Review
Get Codex's review of an implementation plan before the user starts building — trigger when they want Codex (or a named GPT model like gpt-6.2-sol) to review, critique, or pressure-test a plan. Applies to any plan-shaped artifact — a plan file, plan-mode plan, a migration/rearchitecture/integration/checkout write-up, or a doc describing how they intend to do something (pasted, at a repo path, or just described). Fire on any second-opinion phrasing — "poke holes in it", "sanity-check my plan", "run this past Codex", "get Codex's take", "flag the biggest risks", "look this over before I start",
Install
/plugin marketplace add robbyt/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add robbyt/claude-skills --skill plan-reviewgit clone --depth 1 https://github.com/robbyt/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/codex/skills/plan-review ~/.claude/skills/plan-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Plan Review via Codex
Use Codex to critique implementation plans for gaps, risks, and better alternatives. Codex consults; Claude writes.
## Transport
**Always use the MCP tool.** The plugin's MCP server (`scripts/codex-mcp-server.mjs`, started from `.mcp.json`) runs `codex exec` for each call. Tool name: `mcp__plugin_codex_cli__codex`. If the example below errors with an unknown-tool error, run `/mcp` and substitute the actual prefix (e.g., `mcp__codex_cli__codex`).
## Model
**Pin `model: "gpt-6.2-sol"` with `config: { "model_reasoning_effort": "medium" }`** on the opening call. Plan review benefits from flagship reasoning — don't downgrade to `gpt-6-luna` here. Set both on the first `codex` call only; `codex-reply` reuses them unless you escalate. Honor an explicit user-named model if given. See `../references/patterns.md` → Models and Reasoning effort. **Escalate to `gpt-6.2-astra`** (pass `model` + `config` on the `codex-reply`) from round 3, when a disagreement survives a round, or when re-reviewing the same plan in a fresh thread — see `../references/patterns.md` → Escalating to Astra.
## Flow
Codex reads files from the project root. For plans living outside the repo (e.g., `~/.claude/plans/...`), **read them with Claude's `Read` tool first and embed the content in the prompt** — Codex can't see paths outside its `cwd`.Details
- Skill name
plan-review- Repository
- robbyt/claude-skills
- Path
plugins/codex/skills/plan-review/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Plan Review skill do?
Get Codex's review of an implementation plan before the user starts building — trigger when they want Codex (or a named GPT model like gpt-6.2-sol) to review, critique, or pressure-test a plan. Applies to any plan-shaped artifact — a plan file, plan-mode plan, a migration/rearchitecture/integration/checkout write-up, or a doc describing how they intend to do something (pasted, at a repo path, or just described). Fire on any second-opinion phrasing — "poke holes in it", "sanity-check my plan", "run this past Codex", "get Codex's take", "flag the biggest risks", "look this over before I start",
How do I install the Plan Review skill?
Claude Code plugin: /plugin marketplace add robbyt/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Plan Review popular?
It lives in robbyt/claude-skills, which has 42 GitHub stars and 2 forks.
Related skills
Actions
42robbyt/claude-skills
GitHub Actions workflow management using GitHub CLI. Trigger when user wants to check CI status ("check CI", "is the build passing"), view workflow runs ("show recent runs", "view action logs"), watch running workflows ("watch CI"), or rerun failed workflows ("rerun the build").
Adversarial Review
42robbyt/claude-skills
Have Codex try to break a change before it ships — a skeptical review that challenges the design, assumptions, and failure modes of a diff or branch and returns structured findings (verdict, severity, file:line, confidence). Trigger on "adversarial review", "challenge this change/design with Codex", "pressure-test this before I ship", "have Codex try to break this", "is this safe to merge", or a review focused on a risk area (auth, data loss, rollback, race conditions, retries). Do NOT use for a routine bug/style pass over a diff (that's diff-review), for critiquing a plan before code exists (
API Review
42robbyt/claude-skills
This skill should be used when reviewing API designs, auditing REST or gRPC endpoints, designing backend APIs, evaluating BFF architecture, or discussing API best practices. Also triggers on: "review this API", "API design review", "is this API correct", "REST API audit", "gRPC API review", "PATCH vs PUT", "etag", "idempotency", "pagination design", "API error handling", "backward compatibility", "BFF architecture", "resource-oriented design", "TOCTOU", "race condition", "optimistic concurrency", "field mask", "long-running operation", "custom method", "soft delete", "API naming conventions",
Plan Review
42robbyt/claude-skills
Get Gemini's review of Claude's implementation plans. Trigger when user wants a second opinion on a plan ("have Gemini review this plan", "get second opinion", "critique this plan"), or after Claude creates a plan file that needs validation before implementation.
Plan Review
42robbyt/claude-skills
Get Google Antigravity's (`agy`) review of Claude's implementation plans. Trigger when user wants a second opinion on a plan ("have agy review this plan", "get a second opinion from Google Antigravity", "critique this plan with agy"), or after Claude creates a plan file that needs validation before implementation. Replaces the deprecated gemini-cli plan-review workflow.
Reflect
42robbyt/claude-skills
Analyze recent conversation to identify improvements for CLAUDE.md memory files. Trigger when user says "reflect on this session", "reflect on this conversation", "reflect on this code", or "improve CLAUDE.md by reflecting on this session". The verb "reflect" combined with a session/conversation/code subject is the key trigger.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.