plan-reviewer

# Plan Reviewer ## Minimum required inputs from the plan (reviewer gate) Before reviewing details, confirm the plan includes these minimum inputs. If any are missing, request edits to the plan rather than guessing. - **Acceptance Criteria**: clear, user visible outcomes, written as observable conditions - **Validation Plan**: at least one validation step per acceptance criterion - **Automated Test Intent**: what will be covered by automated tests, and where they live - **Manual Validation Steps**: concrete steps anyone on the team can follow - **Integration Touchpoints**: systems, services, queues, APIs, data stores, or clients that will be affected Review implementation plans, PR specifications, and feature documentation **before coding begins**. This skill focuses on: - Testable acceptance criteria - Complete validation strategies (manual + automated) - Integration awareness - Clear open questions and risks It is designed to produce **actionable deltas**, not a perfect plan. --- ## When to Use This Skill Use this skill when reviewing: - Implementation plans and execution checklists - PR specifications - Feature documentation and PRDs (where acceptance criteria exist) **Do not use** this skill for: - Reviewing actual code (use a code reviewer) - Performance optimization reviews - Security audits (use a dedicated security review) - Architecture and design decisions (use an architecture review) --- ## Definition of Done (Stop Conditions) A plan review is “done” ...