Plan Review Criteria

Plan Review Criteria

Overview

Multi-dimensional plan review with quality gates. Every plan gets reviewed before implementation starts — no exceptions. Review covers six axes: completeness, task quality, architecture & sequencing, risk coverage, actionability, and proposed code quality.

The approval standard: Approve a plan when it is specific enough that a skilled implementer could execute it without guessing, the task ordering is sound, and risks are acknowledged. Perfect plans don't exist — the goal is confidence that implementation won't derail. Don't block a plan because it isn't exactly how you would have structured it. If it's executable and well-organized, approve it.

When to Use

• The reviewer subagent of the review-plan flow loads this skill to perform the review of a plan.
• To review a plan, always go through the review-plan flow — never load this skill directly for that. This is the criteria reference, not the flow.

Do NOT use for: Single-file changes with obvious scope, or when the task is trivial enough to just do.

The Six-Axis Review

Every plan gets evaluated across these dimensions:

1. Completeness

Does the plan cover everything needed to implement successfully?

• Is the context clear? (What problem, why now, what's the goal?)
• Are affected modules identified with paths?
• Are architecture decisions documented with rationale?
• Is there a testing strategy?
• Are verification commands explicit (not "run the tests")?
• Are open questions listed (not buried in someone's head)?
• Is there a parallelization assessment for multi-task plans?

Missing any of these is a gap, not a nit.

2. Task Quality

Are the tasks well-defined and independently executable?

• Does every task have acceptance criteria? (Testable, not vague)