plan-review
Skill2 starsChanged 53 days agoMITView on GitHub
Criteria for reviewing implementation plans against quality standards
47 other projects use a version of this.
Adopted by
Most recently taken up by
- SamuelBostic29/claude-skillstheir own version, first seen Nov 16, 2026
- antick/skillstheir own version, first seen Nov 16, 2026
- pantheon-org/tekhnetheir own version, first seen Nov 15, 2026
- ihorpar/agent-skillstheir own version, first seen Nov 15, 2026
- iuliandita/skillstheir own version, first seen Nov 15, 2026
- duncanmorris/agent-skillstheir own version, first seen Nov 13, 2026
Used with
Projects with it also use plan-execute, pr-comment and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
longranger2Skillplan-execute
Use when the user says "/plan-execute", "plan execute", "implement plan", or "execute plan" and provides a finalized plan file path to carry out. Claude orchestrates, Codex writes code, Claude reviews, and Codex fixes issues until the quality bar is met.
Also in 4 projects that use this
BenjaminGSkillpr-comment
This skill should be used when reviewing someone else's pull request and you want drafted review comments posted to GitHub — either gate / gate-wf findings (tier-marked) or pr-challenge's reviewer questions (unmarked) — each drafted through humanizer and posted as a standalone inline comment at its file:line, after one confirmation. Triggers on "post these as review comments", "comment the gate findings on the PR", "draft and post my review", "leave review comments", after a gate / gate-wf run or a pr-challenge pass on a PR you're reviewing.
Also in 3 projects that use this
MicrosoftSkillspec-review
Independent, multi-model review of a design or spec **before** any code is written, for the microsoft/winappcli repo. Activate when a contributor asks to "review this spec", "review my design", "review this design doc", "validate this approach", "should we build this", "spec review", "design review", or "feature review". Fans out parallel sub-agents — each doing its OWN research against the real codebase and ecosystem rather than trusting the spec — covering necessity & scope, approach & alternatives, feasibility vs reality, risks & unknowns, DX & user impact, and a different-model-family cross-check. Emits a decision-oriented recommendation (proceed / proceed-with-changes / reconsider) to stdout. This is the PRE-CODE companion to the pr-review skill (which reviews code already written); use spec-review at the design/spec stage, not on an implemented diff. Does NOT write code or edit the spec.
Also in 3 projects that use this
AnthropicSkilloffice-hours
Set up and run Claude Code office hours, including the calendar event when the champion's own calendar connector allows it. Use when a champion wants a regular time for teammates to bring problems.
Also in 3 projects that use this
Hugging FaceSkillsimplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Also in 3 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 5 projects that use this
Other versions47 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 47
- ahmadrosid/nakama★ 826same name
- igerber/diff-diff★ 414same name
- Mathews-Tom/armory★ 340same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- YougLin-dev/Aha-Loop★ 181same name
- longranger2/claude-gpt-workflow★ 76same name
- ConnorGriffin/skills★ 21same name
- liewcf/agent-skills★ 16same name
- aws-solutions/konductor★ 12same name
37 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-philosophySkill
- code-reviewSkill
- frontend-philosophySkill
- plan-protocolSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
When reviewing implementation plans before execution
- Distinctive: line 15
When auditing plan quality after creation
- Distinctive: line 16
When verifying plans meet documentation standards
- Very specific: line 134
Do NOT re-validate format—plan_save handles structural validation
- Distinctive: line 135
Do NOT evaluate code quality (that's code-review's job)
- Distinctive: line 136
Do NOT execute or modify the plan during review
- Distinctive: line 137
Do NOT skip citation verification for decisions
- Distinctive: line 138
Do NOT accept vague goals or ambiguous tasks
- Distinctive: line 139
Do NOT forget to note positive observations
- Distinctive: line 145
Before completing a plan review, verify:
“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plan Review
Load this skill when reviewing implementation plans (not code).
TL;DR
Systematic plan review focused on 3 quality categories: Citation Quality, Completeness, and Actionability. Structure is pre-validated by plan_save—focus on whether the plan provides actionable implementation guidance.
When to Use This Skill
- When reviewing implementation plans before execution
- When auditing plan quality after creation
- When verifying plans meet documentation standards
- As part of the plan validation workflow
Plan Review Checklist
1. Structure (Pre-validated)
Note: Saved plans are structurally validated by
plan_savebefore storage. Format compliance (YAML frontmatter, status markers, CURRENT marker, numbering) is guaranteed. Focus your review on the quality aspects below.
2. Citation Quality
| Requirement | Check |
| Decisions reference sources | ref:delegation-id format used |
| No unsubstantiated claims | Architectural decisions cite research |
| Research phases show refs | Completed research tasks include citations |
| Citations are verifiable | IDs match actual delegation outputs |
Red Flags:
- Decisions table with empty or
-in Source column - Claims like "industry standard" or "best practice" without citation
- Research tasks marked complete without
→ ref:id
3. Completeness
| Requirement | Check |
| Goal is specific | Measurable outcome, not vague intent |
| Phases are logical | Sequential, with clear progression |
| Edge cases considered | Error handling, failure modes addressed |
| Notes section present | Key decisions and observations documented |
| Context & Decisions table | Captures architectural choices with rationale |
Goal Quality Examples:
- ❌ "Improve authentication" (vague)
- ❌ "Make it better" (unmeasurable)
- ✅ "Add JWT authentication with refresh token support" (specific)
- ✅ "Migrate user table to PostgreSQL with zero downtime" (measurable)
4. Actionability
| Requirement | Check |
| Tasks are specific | Clear what file/component is affected |
| No ambiguous tasks | Avoids "investigate" or "figure out" without scope |
| Dependencies clear | Sequential tasks show logical order |
| Implementation path obvious | Developer can start without clarification |
Actionability Examples:
- ❌ "Set up the backend" (too vague)
- ❌ "Make it work" (no implementation path)
- ✅ "Create
src/auth/jwt.tswith sign/verify functions" (specific file) - ✅ "Add bcrypt password hashing to
UserService.create()" (clear scope)
Severity Classification
| Severity | Icon | Criteria | Action Required |
| Critical | 🔴 | Missing citations for key decisions, no clear goal, unactionable tasks | Must fix before execution |
| Major | 🟠 | Vague tasks, incomplete phases, missing edge case handling | Should fix |
| Minor | 🟡 | Missing notes, unclear dependencies, incomplete rationale | Nice to fix |
| Nitpick | 🟢 | Style preferences, wording suggestions | Optional |
Output Format
Structure your plan review as:
## Plan Review
### Files Reviewed
- `PLAN.md` (or plan content from `plan_read`)
### Overall Assessment
APPROVE | REQUEST_CHANGES | NEEDS_DISCUSSION
### Summary
2-3 sentence overview of plan quality.
### Issues
#### 🔴 Critical
- [Issue description with specific location]
#### 🟠 Major
- [Issue description with specific location]
#### 🟡 Minor
- [Issue description with specific location]
#### 🟢 Nitpick
- [Suggestion]
### Quality Assessment
| Check | Status |
|-------|--------|
| Goal is specific and measurable | PASS / FAIL |
| Citations support key decisions | PASS / FAIL |
| Tasks are actionable | PASS / FAIL |
| Edge cases addressed | PASS / FAIL |
### Positive Observations
- [What's done well - always include at least one]What NOT to Do
- Do NOT re-validate format—
plan_savehandles structural validation - Do NOT evaluate code quality (that's code-review's job)
- Do NOT execute or modify the plan during review
- Do NOT skip citation verification for decisions
- Do NOT accept vague goals or ambiguous tasks
- Do NOT forget to note positive observations
Adherence Checklist
Before completing a plan review, verify:
- All 3 quality categories analyzed (Citations, Completeness, Actionability)
- Severity assigned to each finding
- Specific locations noted for all issues
- Quality Assessment table completed
- Positive observations noted
- Output follows the standard format
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

