plan-review

Reviews implementation plans against specs, codebase reality, and design rules before execution.

Updated May 13, 2026
One-click install
npx skills add https://github.com/andrewcodesit/skills --skill plan-review-andrewcodesit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/andrewcodesit/skills/tree/main/skills/project-management/plan-review
Command: npx skills add https://github.com/andrewcodesit/skills --skill plan-review-andrewcodesit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Plans written by agents or engineers often drift from the spec, ignore existing code, or hide architectural flaws that only surface during implementation. This Skill stress-tests a plan before any code is written, catching blocking issues early when they are cheap to fix. ## Core Features & Use Cases - Multi-lens plan audit: Checks spec alignment, repo rules, codebase reality, YAGNI violations, contract integrity, layer discipline, security exposure, delivery completeness, task decomposition, and pre-mortem coverage. - Structured findings report: Produces a saved review file with blocking findings, non-blocking risks, missing steps, open questions, and a verdict of ready, needs edits, or rewrite. - Guided resolution: Offers a resolution gate to grill on ambiguous findings, apply best judgment, or leave the plan unchanged, then edits the plan in place and records decisions. - Use Case: Before letting an agent execute a multi-file refactor plan, run a plan review to confirm the task ownership table matches real file dependencies and that failure paths have test coverage. ## Quick Start Review this implementation plan and tell me if it is solid before I execute it.

Frequently Asked Questions about plan-review

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

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

Run a plan review that checks the plan against the source spec, repo rules, and the actual codebase files it touches. The review produces blocking findings, risks, missing steps, and a verdict of ready, needs edits, or rewrite.

What should a good implementation plan review check?▼

A thorough review checks spec alignment, YAGNI violations, contract preconditions and postconditions, layer discipline, security exposure, test and rollback coverage, and task independence in the ownership table. Each finding should cite a plan section and propose a correction.

Can an AI agent review its own plan reliably?▼

Self-review right after planning tends to reconfirm the planner's own assumptions. A separate review pass that opens the actual files, reads the decision log, and checks the spec independently catches drift the original planning pass misses.

When should a plan be rejected instead of edited?▼

A plan gets a rewrite verdict when it is built on wrong assumptions, wrong layering, or major omissions that editing cannot fix. Plans with workable direction but specific correctable flaws get a needs edits verdict instead.

Does plan review work without a task ownership table?▼

Yes, the execution decomposition lens is skipped when the plan has no Task Ownership table. All other lenses including spec alignment, codebase reality, contracts, and pre-mortem coverage still apply.