plan-review-lead

To review a story spec for implementation readiness, evaluate the spec and design artifacts against acceptance criteria and constraints. This plan review process results in a structured decision with explicit evidence and next actions.

Evaluating design artifacts yields four policy outcomes: approve, needs_more_evidence, blocked, or request_changes. These decisions guide the next phase by steering the implementation engineer with specific constraints and required context artifacts.

A planning gatekeeper prevents unreviewed scope by thoroughly reviewing story specs and design artifacts before engineering starts. It identifies misaligned requirements and hidden dependencies to ensure a structured handoff to the implementation phase.

A plan review decision should include explicit evidence, constraints, and next actions. It assigns required context artifacts to guide the implementation engineer, ensuring the development team has exactly what is needed to proceed.

You request more evidence during a story spec review when the plan lacks sufficient detail to verify acceptance criteria. This outcome pauses implementation until you collect the missing design artifacts needed to prove feasibility.

Yes, a plan review gatekeeper identifies hidden dependencies by evaluating design artifacts against constraints. It acts as a checkpoint to expose undocumented requirements before the build phase begins, preventing downstream engineering blockers.