SkillAgentSearch skills...

plan-arbiter

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 recommend…

Install / Use

npx skills add BuilderIO/skills --skill plan-arbiter

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Automation

Supported Platforms

Claude Code
OpenAI Codex

Our assessment of plan-arbiter

plan-arbiter scores 86/100 on our quality scale, 1780th of 2,790 Automation skills we index.

Its SKILL.md is 4.0 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.

With 4,394 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so plan-arbiter is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

plan-arbiter compared with similar skills

All 4 of these similar skills score higher than plan-arbiter; compare them before choosing.

SkillScoreStarsUpdatedFormat
plan-arbiter (this skill)by BuilderIO864.4k54d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install plan-arbiter?
Run npx skills add BuilderIO/skills --skill plan-arbiter. The install tabs above show the steps for each supported agent.
Which AI agents does plan-arbiter work with?
It is written for Claude Code and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
Is plan-arbiter safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is plan-arbiter still maintained?
The repository was last updated about 2 months ago, so plan-arbiter is actively maintained.

name: plan-arbiter description: 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

  1. Collect the source plans.
  2. Normalize each plan into comparable claims.
  3. Cross-review the plans against each other and the real codebase or task context.
  4. Choose a winner, merge a better hybrid, or send the plans back for revision.
  5. 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:

  • Check whether it satisfies the user's actual request.
  • Verify claims against the repo, docs, tests, screenshots, or external systems when those are relevant and available.
  • Identify hidden dependencies, missing tests, risky sequencing, vague steps, unnecessary scope, and hard-to-reverse decisions.
  • Notice complementary strengths: one plan may have the better architecture while another has the better migration or validation path.
  • Separate plan quality from executor preference. A cheaper/faster executor can be the right choice for implementation even when another model produced the best critique.

Use subagents for independent review when the plans are large, the codebase is wide, or the decision would benefit from separate technical and product passes.

Decide

Choose one of three outcomes:

  • Adopt: pick one plan mostly as written.
  • Hybrid: combine specific pieces into a stronger execution plan.
  • Revise first: request another planning pass because both plans miss a key constraint or depend on an unresolved decision.

Use this tie-break order:

  1. Correctness and fit to the user's request.
  2. Grounding in real files, APIs, tests, data, and UI behavior.
  3. Simpler first implementation that does not block the intended future.
  4. Better validation and rollback story.
  5. Lower token/time cost for execution once quality is acceptable.

Handoff

Return a compact decision memo:

Decision
- Adopt Plan A / Hybrid / Revise first.

Why
- The deciding evidence and tradeoffs.

Execution Plan
- Ordered steps with files or surfaces to touch.

Borrowed From Other Plans
- Useful pieces kept from non-winning plans.

Rejected
- Ideas intentionally not taking, with reasons.

Verification
- Tests, browser checks, screenshots, CI, review, or deploy checks needed.

Executor Recommendation
- Which agent/model should implement and why.

When the user already asked for execution and the chosen path is clear, proceed with the selected plan after reporting the decision briefly. Otherwise stop at the handoff and ask for approval.

Related Skills

View on GitHub
GitHub Stars4.4k
CategoryAutomation
Updated1mo ago
Forks220

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions