Verify Plan - a risk-coverage audit of a plan before you build

A plan built perfectly is still wrong if the plan was wrong - and a design error is far cheaper to fix on the page than after the code exists. This reviews an EXISTING plan or design (yours, or one writing-plans produced) for the defects that are expensive to discover later. It does not write or fix code; it flags gaps in the plan and hands them back.

When to use / not

• Use it the moment a plan exists and before implementation starts - especially for anything with a boundary, state, auth, migration, or concurrency surface.
• Not code review - that is /code-review, after the build.
• Not plan creation - that is writing-plans / superpowers:brainstorming. This audits a plan that already exists.

The audit - four passes, in order

Load the plan's target stack skill FIRST, so you check against the right trap list, not a generic one.