review-plan

Evaluate implementation plans from .claude/plans/ with a structured checklist and verdict.

9|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/gewoonseba/dotfiles --skill review-plan-gewoonseba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/gewoonseba/dotfiles/tree/main/claude/.claude/skills/review-plan
Command: npx skills add https://github.com/gewoonseba/dotfiles --skill review-plan-gewoonseba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review a project plan with the scrutiny of a principal software engineer before coding starts, surfacing ambiguities, risks, and scope gaps.

Core Features & Use Cases

  • Explicit checklist-driven critique of plans from .claude/plans/ to ensure assumptions are stated and decisions are justified.
  • Structured feedback output including Strengths, Concerns, Assumptions to Verify, and Simplification Opportunities.
  • Final verdict guidance with APPROVE, REVISE, or RETHINK and concrete next steps.

Quick Start

Provide the plan filename from .claude/plans/ and I will deliver a structured critique using the review checklist.

Frequently Asked Questions about review-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an implementation plan before coding starts?

Plan review before coding involves applying a checklist-driven critique to surface assumptions, risks, and scope gaps. Provide a plan filename from .claude/plans/ to receive structured feedback including strengths, concerns, and a final APPROVE, REVISE, or RETHINK verdict.

What is the best way to validate architecture and migration proposals?

The best way to validate architecture and migration proposals is through principled evaluation using a structured review checklist. This process surfaces ambiguities and enforces explicit success criteria, ensuring decisions are justified and assumptions are clearly stated before development begins.

Can I use a checklist-driven critique to find scope gaps in software engineering plans?

Yes, you can use a checklist-driven critique to find scope gaps in software engineering plans. The evaluation enforces explicit success criteria and structured feedback fields, identifying simplification opportunities and assumptions that need verification before coding.

Does the plan review process provide a formal verdict on whether to proceed?

Yes, the plan review process provides a formal verdict of APPROVE, REVISE, or RETHINK. It delivers concrete next steps alongside structured feedback on strengths, concerns, and simplification opportunities to guide your decision on whether to proceed.

What do I need to provide to get a structured critique of my project plan?

You need to provide the plan filename stored in the .claude/plans/ directory. The review process will then evaluate the strategy, architecture, or migration proposal and deliver a structured critique covering assumptions, risks, and scope.

What limitations exist when evaluating strategy and design proposals?

A limitation is that the evaluation is restricted to plans sourced from the .claude/plans/ directory. The review focuses on surfacing assumptions and providing a verdict, meaning it validates existing proposals rather than generating new implementation plans from scratch.