Design the approval screen for a real change

The prompt

For the last change an agent (or a human) shipped to this project, write out exactly what a reviewer would need to see before approving it: the proposed action, affected resources, policy result, validation evidence, and rollback plan. Is your current review process actually showing all five?

Why it's built that way

Human approval should occur at a meaningful boundary, with the exact proposed action, affected resources, policy result, validation evidence, and rollback plan visible before authorization is requested — not a summary that trusts the agent's account of its own work.

What to do with the answer

If your current PR template is missing the rollback plan or policy result, add those fields now.