Plan Review

This automates the back-and-forth of getting a design doc ready by having Codex review your plan file, then Claude applies the feedback and kicks off another round until consensus is reached. You run `/plan-review plans/my-feature.md` and it handles the loop: Codex raises at least 10 concrete issues per round (architecture, feasibility, edge cases, tech choices), Claude evaluates which suggestions are valid and revises the plan in place, then decides whether to continue based on status flags like NEEDS_REVISION or APPROVED. It tracks review history across rounds in a separate file and reuses session context so Codex remembers what was already discussed. Useful when you want your plan stress-tested before implementation without manually shuttling feedback between tools.

skills.sh installs: 247
GitHub stars: 81
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add longranger2/claude-gpt-workflow --skill plan-review --agent claude-code

Installs into .claude/skills of the current project.

Files

Plan Review Skill

Purpose

When the user runs /plan-review {plan-file-path}, start the "adversarial plan iteration" workflow:

I (Claude Code) ask Codex to perform a critical review of the specified plan.
I read the review produced by Codex and evaluate whether its suggestions are sound.
I revise the plan based on valid suggestions and write changes back to the original plan file.
If the review status is NEEDS_REVISION, I automatically ask Codex to review again.
Repeat until consensus is reached as MOSTLY_GOOD or APPROVED.

Usage

/plan-review plans/my-feature-plan.md

Session Reuse

After each Codex invocation, extract session_id=xxx from the script output and save it as the session ID for the current task. In later Codex calls for the same task, pass --session <id> to reuse context so Codex remembers prior review history and can stay consistent across multiple rounds.