Copy this structure for a plan review:
Goal: What observable outcome does the user want?
Done when: How will completion be verified?
Constraints: Time, cost, permissions, formats, dependencies.
Known facts: Include evidence or references.
Unknowns: Which missing fact could change the plan?
Steps: Small actions with a concrete result for each.
Checkpoints: What evidence should trigger a change?
Handoff: Current state, artifacts, decisions, next action.
Ask reviewers one focused question, such as: Which dependency makes this plan fragile?
A useful plan should reduce uncertainty before spending heavily on implementation. Review permissions before external actions, and keep private context out of the public version.