plan-consensus

plan-consensus

Claude Code skill that automates iterative review of plan/spec/design markdown files by looping between Claude and Codex CLI until both agree — or surface an unresolvable impasse for you to decide.

What it does

Instead of manually ping-ponging your plan between Claude and Codex, this skill does it automatically:

1. Codex reads the plan and critiques it (BLOCKING / IMPORTANT / NITS / VERDICT)
2. Claude reviews the critique — accepts valid points (edits plan), rejects invalid ones (writes rebuttal)
3. Loop repeats until:
   • Codex outputs CONSENSUS → done
   • Max rounds reached → lists unresolved items
   • Impasse detected (same disagreement 2+ rounds) → surfaces both arguments for you

All artifacts land in plan-consensus/ next to your plan file:

plan-consensus/
  plan.original.md       ← original backup
  round-1-codex.md       ← Codex critique round 1
  round-1-claude.md      ← Claude response round 1
  ...
  discussion.log.md      ← full transcript
  final-verdict.md       ← CONSENSUS / MAX_ROUNDS / IMPASSE

Requirements

• Claude Code with Codex plugin installed
• Codex CLI installed and logged in (codex login)

Installation

Add to your ~/.claude/settings.json:

{
  "extraKnownMarketplaces": {
    "plan-consensus": {
      "source": {
        "source": "github",
        "repo": "senojed/plan-consensus"
      }
    }
  },
  "enabledPlugins": {
    "plan-consensus@plan-consensus": true
  }
}

Usage

/plan-consensus path/to/plan.md

With options:

/plan-consensus path/to/plan.md max_rounds=8
/plan-consensus path/to/plan.md max_rounds=3 model=o4-mini

How it works

• Codex runs with --sandbox read-only — it only reads, never writes
• Claude is the sole editor of the plan file
• Each round Codex gets a summary of Claude's previous response so it doesn't repeat resolved points
• Impasse triggers when plan hash is unchanged 2 rounds in a row and Codex still wants changes

License

MIT