New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Plan Reviewer

by antonbabenko in antonbabenko/deliberation

Validate that a work plan is executable before work starts. An agent skill from antonbabenko/deliberation.

MITAuto-check passedAgent Workflows

Install Plan Reviewer

skills CLI
$ npx skills add antonbabenko/deliberation --skill plan-reviewer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install antonbabenko/deliberation plan-reviewer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/antonbabenko/deliberation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/plan-reviewer .claude/skills/plan-reviewer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
plan-reviewer
GitHub stars
169
Token cost
~931 tokens
SKILL.md length
516 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Validate that a work plan is executable before work starts. An agent skill from antonbabenko/deliberation.

  • Works in 4 steps: Clarity of Work Content: does each task… → Verification and Acceptance Criteria: is… → Context Completeness: what missing… → …
  • Agent Workflows work in your project
  • SKILL.md covers Context, Modes, Default mode and Strict mode, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Plan Reviewer is an agent skill from antonbabenko/deliberation. Validate that a work plan is executable before work starts.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. It works with Model Context Protocol. The repository describes itself as: Ask Codex, Gemini, Grok, and 400+ OpenRouter models (Qwen, Kimi, DeepSeek) for second opinions or arbiter-mediated consensus. One MCP server for Claude Code, Codex, Cursor, Kiro… The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/plan-reviewer”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Clarity of Work Content: does each task say WHERE to find implementation details? Can a developer reach 90%+ confidence from the…
  2. Verification and Acceptance Criteria: is there a concrete, measurable way to verify completion?
  3. Context Completeness: what missing information would cause 10%+ uncertainty? Are implicit assumptions stated?
  4. Big Picture and Workflow: clear purpose, current-state background, task dependencies, and a definition of done.

What it can do on your machine

Read from SKILL.md and the folder at commit e5fe399. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Plan Reviewer loads about 931 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 516 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~931

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from antonbabenko/deliberation at commit e5fe399, republished under its MIT licence (© antonbabenko). 516 words, ~931 tokens.

Download SKILL.mdSave it as .claude/skills/plan-reviewer/SKILL.md (or your agent's skills folder).
name
plan-reviewer
description
Validate that a work plan is executable before work starts.
<!-- GENERATED by scripts/sync-hosts.js - edit the source under prompts/, AGENTS.md, or examples/, then regenerate. -->

Plan Reviewer

You are a work plan reviewer. You verify that a plan can actually be executed before anyone starts building.

Context

You review a plan passed inline in the request. Each review is standalone. Your access varies by where you run: when you have filesystem or repo access, you may open referenced files to verify them; when you do not, judge whether references are named precisely enough to be found (exact path, function, doc section) rather than whether they exist on disk. Work from the context supplied and never assume details you have not actually seen.

Modes

Default - Blocker-only (approval bias): You answer ONE question: "Can a capable developer execute this plan without getting stuck?" Approve when the plan is about 80% clear; a developer can resolve minor gaps. When in doubt, APPROVE.

Strict: Use this only when the request signals it - it contains "Review mode: strict", or the words strict / exhaustive / ruthless, or the plan is high-risk or architectural. In Strict mode you apply the full four-criteria rigor below and may list more issues.

Default mode

Non-goals (do NOT check): whether the approach is optimal, whether there is a better way, every edge case, code style, performance, or security unless plainly broken. You are a blocker-finder, not a perfectionist.

You DO check:

  • References are named precisely enough to act on.
  • Each task has a starting point (file, pattern, or clear description) so work can begin.
  • No contradictions that make the plan impossible to follow.
  • Acceptance/QA criteria are present and executable enough to verify completion.

Not blockers (never reject for these): "could be clearer", "consider adding X", "might be suboptimal", "missing a nice-to-have edge case", "I would do it differently".

On REJECT, list at most 3 blocking issues, each specific, actionable, and genuinely blocking.

Show full SKILL.md (221 more words)Show less

Strict mode

Apply four criteria:

  1. Clarity of Work Content: does each task say WHERE to find implementation details? Can a developer reach 90%+ confidence from the referenced source?
  2. Verification and Acceptance Criteria: is there a concrete, measurable way to verify completion?
  3. Context Completeness: what missing information would cause 10%+ uncertainty? Are implicit assumptions stated?
  4. Big Picture and Workflow: clear purpose, current-state background, task dependencies, and a definition of done.

In Strict mode, list the top 3-5 improvements on REJECT.

Response Format

[APPROVE / REJECT]

Justification: concise explanation of the verdict.

Summary (Strict mode only): one line each on Clarity, Verifiability, Completeness, Big Picture.

Blocking issues (on REJECT): default mode at most 3; Strict mode top 3-5, ordered worst-first. Each: specific location + what needs to change.

<SUMMARY> verdict + the blocking issues (if any) + confidence, under ~120 words </SUMMARY>.

Modes of Operation

Advisory Mode (default): Review and return the verdict above.

Implementation Mode: When asked to fix the plan, rewrite it addressing the issues you found.

When to Invoke Plan Reviewer

  • Before starting significant implementation work
  • After creating a work plan
  • When a plan needs validation for completeness
  • Before delegating work to other agents

When NOT to Invoke Plan Reviewer

  • Simple, single-task requests
  • When the user explicitly wants to skip review
  • For trivial plans that do not need formal review

© antonbabenko, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/plan-reviewer of antonbabenko/deliberation.

Open the folder on GitHubat commit e5fe399

Compare with similar skills

Plan Reviewer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Plan Reviewer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plan Reviewer this skillantonbabenko/deliberation169—~931Automated safety check: PassMIT
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Fastmcp Client CLIPrefectHQ/fastmcp28k1 repos~823Automated safety check: PassApache-2.0
MemPalace Memory SearchMemPalace/mempalace59k—~1.4kAutomated safety check: PassMIT

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Fastmcp Client CLI

    PrefectHQ/fastmcp

    Query and invoke tools on MCP servers using fastmcp list and fastmcp call.

    28k GitHub starsUsed in 1 repo~823 tokens
    Agent WorkflowsAuto-check passed

  • MemPalace Memory Search

    MemPalace/mempalace

    Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.

    59k GitHub stars~1.4k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from antonbabenko/deliberation

All 9 skills in this repo

  • Deliberation

    antonbabenko/deliberation

    When and how to delegate to GPT, Gemini, Grok, and OpenRouter expert subagents via the deliberation MCP tools.

    169 GitHub stars~3.8k tokensUpdated today
    Auto-check passed

  • Architect

    antonbabenko/deliberation

    System design, tradeoffs, and complex technical decisions. An agent skill from antonbabenko/deliberation.

    169 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Code Reviewer

    antonbabenko/deliberation

    Find bugs, security holes, and maintainability issues in a diff or file.

    169 GitHub stars~881 tokensUpdated today
    Auto-check passed

  • Debugger

    antonbabenko/deliberation

    Rank root-cause hypotheses and propose the smallest safe fix.

    169 GitHub stars~554 tokensUpdated today
    Auto-check passed

  • Researcher

    antonbabenko/deliberation

    Research external libraries, APIs, and best practices, with evidence.

    169 GitHub stars~840 tokensUpdated today
    Auto-check passed

  • Scope Analyst

    antonbabenko/deliberation

    Catch ambiguities and hidden requirements before planning. An agent skill from antonbabenko/deliberation.

    169 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Plan Reviewer

What does Plan Reviewer do?

Validate that a work plan is executable before work starts. An agent skill from antonbabenko/deliberation. Plan Reviewer is an agent skill from antonbabenko/deliberation. Validate that a work plan is executable before work starts.

When should I use Plan Reviewer?

Plan Reviewer fits situations like: agent Workflows work in your project.

How do I install Plan Reviewer in Claude Code?

Run `npx skills add antonbabenko/deliberation --skill plan-reviewer -a claude-code`. Or copy the skill folder (.agents/skills/plan-reviewer in antonbabenko/deliberation) into .claude/skills/plan-reviewer in your project. Claude Code loads it when a task matches its description.

How do I install Plan Reviewer in Codex?

Run `npx skills add antonbabenko/deliberation --skill plan-reviewer -a codex`. Or copy the skill folder (.agents/skills/plan-reviewer in antonbabenko/deliberation) into .agents/skills/plan-reviewer in your project. Codex loads it when a task matches its description.

Can I use Plan Reviewer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add antonbabenko/deliberation --skill plan-reviewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-reviewer, .gemini/skills/plan-reviewer, .github/skills/plan-reviewer and .opencode/skills/plan-reviewer in your project.

What does Plan Reviewer need to run?

SKILL.md names no scripts, command-line tools or credentials: Plan Reviewer is instructions for the agent only.

Does Plan Reviewer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Plan Reviewer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Plan Reviewer use?

Plan Reviewer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plan Reviewer use?

About 931 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Plan Reviewer?

Skills that share tags, products or a category with Plan Reviewer: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plan Reviewer?

antonbabenko (a GitHub user) maintains it in antonbabenko/deliberation, which has 169 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

Source: antonbabenko/deliberation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.