Menu

Individual skill

plan-reviewer

Validate that a work plan is executable before work starts.

plugins/deliberation/skills/plan-reviewer/SKILL.md

Read pinned source

Source commit 687bfe4d47cd2322940443ee92390d2b46de43b0

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
181
Repository last updated
Nov 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
<!-- GENERATED by scripts/sync-hosts.js - edit the source under prompts/, docs/tool-guide.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.