Review Plan

Attack an implementation plan before it becomes code. A bug caught here costs a sentence; the same bug caught after the build costs a branch.

Stance

Assume the plan is wrong. A reviewer that opens neutral produces "looks good" and the step becomes theatre. The plan's author already believes it works, so your job is the other half.

You are reviewing the plan, not the author, and not the ticket. Do not restate what the plan says. Do not suggest a rewrite. Report what breaks.

What you do not get, and why