agentleFS
dgrissen2dgrissen2/persona-review-kit/skills/codex-plan-review/SKILL.md

codex-plan-review

Skill0 starsChanged 3 months agoMITView on GitHub

Run an independent Codex plan review using GPT-5.6 Sol with xhigh reasoning. Use for milestone roadmaps, implementation plans, architecture/design docs, and specs before implementation. Generic by default; flexible for optional persona lenses resolved from the persona registry.

  • Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    test adequacy: whether tests cover the actual risks in the plan

    line 24
  2. Very specific:

    Run without personas for a generic review.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Codex Plan Review

Independent plan review using Codex (gpt-5.6-sol, model_reasoning_effort=xhigh). This is for plans, roadmaps, specs, and design docs, not ordinary code diffs.

Requires the codex CLI (npm install -g @openai/codex, then codex login). Persona listing/resolution works without it.

Focus

The generic review checks:

  • spec fidelity: missing requirements, invented scope, ambiguous acceptance criteria
  • internal consistency: formulas, thresholds, score ranges, naming, and definitions
  • dependency ordering: milestones that depend on unbuilt or underspecified pieces
  • data contracts: fields, enums, units, return shapes, schemas, and file paths
  • feasibility: work estimates, validation budgets, operational assumptions
  • edge cases: empty inputs, boundaries, NaN/None, rollback and failure modes
  • test adequacy: whether tests cover the actual risks in the plan

Personas

Personas are optional lenses, not a fixed enum. Decide which to use up front when the review is initiated. Example lenses: architect, cto, red-team, software-architect, quant — or pass a direct path to a persona .md file.

Run without personas for a generic review; pass --personas a,b,/path/to/persona.md for a panel.

List what's available via the shared resolver (works even without Codex):

python3 ~/.claude/skills/persona-registry/scripts/persona_registry.py --list

Model & reasoning effort

Defaults: model gpt-5.6-sol, reasoning effort xhigh. To change (no reinstall): pass --model / --effort, or edit DEFAULT_MODEL / DEFAULT_EFFORT at the top of the script.

Workflow

Generic review:

python ~/.claude/skills/codex-plan-review/scripts/codex_plan_review.py \
  <plan_file> \
  [context_file ...]

Generic review plus persona overlays:

python ~/.claude/skills/codex-plan-review/scripts/codex_plan_review.py \
  <plan_file> \
  [context_file ...] \
  --personas architect,red-team,/path/to/custom_persona.md

The script writes review artifacts next to the plan file and prints the combined output. Persona passes are independent; synthesis sees only completed outputs.

Output Contract

Generic:

## Codex Plan Review — Verdict: PASS / CONDITIONAL PASS / FAIL (N findings)

Persona:

## Codex Plan Review — <Persona Name>

Synthesis:

## Codex Plan Review — Panel Synthesis

Persona resolution

Personas resolve via the shared resolver (persona-registry/scripts/persona_registry.py), which is installed regardless of Codex. The Codex script locates it automatically. Search order (first existing wins):

  1. $PERSONA_REGISTRY_DIR (explicit override, if set)
  2. co-located with the Codex script
  3. the skill dir / skills root (repo layouts)
  4. the sibling persona-registry skill (in-repo layout)
  5. ~/.claude/skills/persona-registry/scripts (installed canonical resolver)

Persona discovery (which .md files are available) is governed by the persona-registry skill: PERSONA_PATHS / --persona-dir, then the installed kit library (~/.config/persona-review-kit/personas/), then project-local folders, then ~/.claude/personas/.

Intent and focus (automatic)

Derive these from the user's request — they should not need to type flags. From how they phrase the ask, infer intent (what the work is trying to do) and focus (what to weight) and pass them as --intent / --focus. For example, "review the auth refactor on this branch, focus on whether the logic is right and skip style" -> --intent "auth refactor" --focus "logic correctness, skip style".

The text is appended to the prompt as author framing, never as another reviewer's findings (the review stays independent). A guardrail still surfaces every CRITICAL/HIGH finding even when it falls outside the focus.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.