review-plan

A pre-flight check for an implementation plan is a structural validation that identifies feasibility gaps, missing verification steps, ordering bugs, and unrecorded decisions before any coding begins. It produces a machine-parseable READY, NEEDS_REVISION, or BLOCKED verdict to prevent mid-execution rework.

To review an implementation plan for feasibility risks, evaluate the plan against eight core categories including feasibility, completeness, task ordering, and risk factors. This generates a prioritized findings table with actionable recommended edits to resolve any identified structural contract violations.

Yes, automated plan validation applies directly to all software engineering implementation plan markdown files. It enforces a plan-shape contract by requiring machine-readable checkboxes, explicit file touch references, verifiable task steps, appropriate task sizing, and a clearly defined end-state.

The best way to catch unrecorded decisions and task ordering bugs is to run a content checklist review on the plan. This evaluates verification coverage and scope, returning a prioritized findings table that highlights incorrectly ordered dependent tasks or missing critical choices like a cache library.

Yes, plan review outputs a clear machine-parseable READY, NEEDS_REVISION, or BLOCKED verdict paired with a prioritized findings table. This structured output is usable both standalone and as a pre-execution gate for downstream implementation skills.

You should not use automated implementation plan review if your plan lacks machine-readable checkboxes, explicit file touch references, or verifiable task steps. The structural validation requires this defined plan-shape contract and a clear end-state to generate a meaningful readiness verdict.