Evaluates technical plans for gaps and risks before implementation begins.
Install
mkdir -p .claude/skills/review-plan && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17373" && unzip -o skill.zip -d .claude/skills/review-plan && rm skill.zipInstalls to .claude/skills/review-plan
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use after creating a plan in plan mode to critique it for gaps, risks, and clarifying questions before implementation. Triggers on "review plan", "critique plan", "check my plan".Key capabilities
- →Assess plan completeness
- →Evaluate technical feasibility of a plan
- →Review implementation clarity
- →Check dependencies and prerequisites
- →Critique testing strategy
- →Address documentation requirements
How it works
The skill systematically analyzes a plan across several dimensions, provides an overall assessment, and then asks clarifying questions one at a time.
Inputs & outputs
When to use review-plan
- →Critique current implementation plan
- →Check for missed edge cases
- →Validate testing approach
About this skill
Review Current Plan
Conduct a thorough review of the plan created in the current session. Act as a meticulous technical reviewer and strategic advisor.
Prerequisites
This skill requires an active plan from plan mode. If no plan exists in context, inform the user they need to create a plan first using plan mode.
Review Dimensions
Systematically analyze the plan across:
- Completeness: Missing components, edge cases, error handling, dependencies not addressed
- Technical feasibility: Technical challenges, performance bottlenecks, architectural concerns
- Implementation clarity: Does each step have sufficient detail? Any ambiguity?
- Dependencies & prerequisites: External deps, tools, libraries, infrastructure requirements documented?
- Testing strategy: Testing approaches, validation criteria, quality checks defined?
- Documentation: Documentation requirements and knowledge transfer needs addressed?
- Security & compliance: Security considerations, compliance requirements noted?
(Enterprise-only dimensions — deployment/rollout, timeline realism, resource allocation/budget — were dropped for the solo-dev profile.)
Output Format
-
Brief summary: Overall quality assessment and critical gaps (2-3 sentences max)
-
Iterative questions: Ask clarifying questions one at a time using AskUserQuestion tool:
- Context: What aspect you're questioning and why it matters
- Current state: What the plan says (or doesn't say) about this
- Impact: Why this decision matters for success
- Provide multiple-choice options where applicable
-
After each answer, either:
- Ask the next critical question, or
- Confirm the plan is comprehensive
Guidelines
- Be direct and concise in feedback
- Prioritize critical gaps over minor improvements
- Focus on risks that could derail the project
- Don't ask about things already clearly addressed in the plan
- Stop questioning when all critical decisions are resolved
Reference Files
references/question-examples.md- Sample clarifying questions with context
When not to use it
- →When no active plan exists from plan mode
- →When the user wants minor improvements over critical gaps
Limitations
- →Requires an active plan from plan mode
- →Focuses on critical gaps over minor improvements
- →Does not address enterprise-only dimensions like deployment or timeline realism
How it compares
This skill provides a structured, iterative critique of a plan, focusing on critical gaps and risks, unlike a general or unstructured review.
Compared to similar skills
review-plan side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| review-plan (this skill) | 0 | 17d | No flags | Intermediate |
| confidence-check | 13 | 4mo | Review | Beginner |
| specification-architect | 13 | 8mo | Review | Advanced |
| drift-analysis | 2 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
confidence-check
SuperClaude-Org
Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification.
specification-architect
adrianpuiu
A rigorous, traceability-first system that generates five interconnected architectural documents (blueprint.md, requirements.md, design.md, tasks.md, and validation.md) with complete requirements-to-implementation traceability. Use this skill when users need to architect systems, create technical specifications, or develop structured project documentation with guaranteed traceability.
drift-analysis
avifenesh
This skill should be used when the user asks about "plan drift", "reality check", "comparing docs to code", "project state analysis", "roadmap alignment", "implementation gaps", or needs guidance on identifying discrepancies between documented plans and actual implementation state.
flow-next-plan-review
gmickel
Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
rfc-check
meta-pytorch
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
feature-planning
mhattingpete
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.