review-implementation-plan

Skill: Review Implementation Plan

This skill provides an independent quality gate for implementation plans authored via author-and-verify-implementation-plan.

A reviewer fresh from the authoring context evaluates one implementation plan or an ordered batch against phase scope, existing code, and actionability criteria. Fresh independence does not mean starting a cold reviewer for every phase. Each review remains a per-phase plan artifact.

---

When to Use

Use this skill when:

• An implementation plan has been authored/verified and you want to validate it before execution.
• Multiple implementation plans have been authored sequentially and should be reviewed together as a dependency-ordered batch.
• You want to confirm that the implementation plan is concrete enough for execute-work-package.
• The user explicitly requests an implementation plan review.

Do not use this skill to:

• Review the plan itself (use review-plan).
• Review a completed implementation (use review-implementation).
• Rewrite the implementation plan during the independent review pass. After review completion, accepted related findings may transition to review-fix in the same reviewer session.

Review Focus

The default priority is the smallest complete implementation: confirm that phase obligations are covered and no implementation step or new artifact is unauthorized, unnecessary, or needlessly indirect. Use the actual codebase to substantiate material concerns, but record only evidence-backed exceptions. The primary may add a focus via {{focus}}.

Review posture

Detect existing gold-plating without becoming an adversarial reviewer. A reduction finding must name a concrete planned step/artifact and show missing authorization, missing present necessity, or a smaller path in the current codebase that remains complete: the requested behavior must still work, affected real paths must still integrate, and applicable existing invariants must be preserved. Scope discipline is not permission to omit necessary work. Do not invent ideal architecture, hardening, tests, infrastructure, policy, or replacement work. Zero findings remains valid.