Plan Arbiter
Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing...
Install
npx skills add BuilderIO/skills --skill plan-arbiter -g -a claude-code -y- Repository
- BuilderIO/skills4.6k
- Category
- AI and agents
- Updated
- 7d ago
- License
- MIT
- Context cost
- Lightabout 920 tokens
- Runs scripts
- No, instructions only
What it does
Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies; or when the user wants one recommended execution plan after agents review each other's proposals.
Plan Arbiter
Turn competing plans into one executable direction. Preserve the best ideas, reject weak assumptions, and produce a clear handoff instead of a blended mush.
Workflow
- Collect the source plans.
- Normalize each plan into comparable claims.
- Cross-review the plans against each other and the real codebase or task context.
- Choose a winner, merge a better hybrid, or send the plans back for revision.
- Produce one execution handoff with verification gates and rejected alternatives.
Planning is read-only unless the user explicitly asks you to implement after the decision.
Collect Source Plans
Accept plans as pasted text, local files, session IDs, transcript paths, PRs, comments, visual-plan links, or chat history. Resolve the original artifacts when possible so you can see prompt changes and assumptions that may be missing from a final summary.
If a plan is still being written and the user asked you to wait, monitor it until it is done or blocked. If a plan cannot be resolved, continue with the available plan text and mark the missing source as a risk.
Normalize
For each plan, extract:
- Objective and scope.
- Key assumptions and unresolved questions.
- Proposed files, modules, APIs, data shapes, UI states, or workflows.
- Implementation sequence.
- Validation strategy.
- Rollback or migration concerns.
- Cost, complexity, and expected executor fit.
Do not reward verbosity. Prefer plans that are concrete, grounded in real code, and honest about tradeoffs.
Cross-Review
Review each plan as if another capable agent wrote it:
