Separate planning from execution
Choose when a human reviews intent and enforce the boundary according to task risk.
Plan, execute, validate
A plan describes what will change and why. Execution makes the concrete change. Validation checks whether the result meets the goal. The infographic emphasizes reviewing intent before accepting impact.
Two useful arrangements
A plan-first proposal receives approval before implementation. This can suit sensitive workflow, authentication or infrastructure changes.
A combined plan-and-change proposal includes the rationale and implementation together, then receives checks and review before merge. This can suit smaller, reversible tasks.
Neither arrangement removes review. The difference is when code is generated relative to the human decision.
Enforce the chosen boundary
Use read-only planning capability, restricted tools or an explicit approved handoff where the environment supports them. A "plan mode" label or sentence in a prompt is not sufficient proof that execution is impossible.
Record approval and scope. If new information materially changes the plan, return to the decision point rather than treating the old approval as unlimited authorization.