Make the manual recovery step a script with a dry run
The recovery step somebody performed by hand under pressure, turned into a script with a dry run.
The ticket
Turn a manual recovery step into a reviewed script with a dry-run mode.
Acceptance criteria
- The script has a dry-run mode that changes nothing
- Dry-run output is attached to the pull request
- It refuses to run against the wrong environment
- Execution stays with a person; the ticket delivers the script only
What lands as proof
Dry-run output showing exactly what would change, reviewed before anybody runs it for real.
Why teams defer it
- Scripting a destructive operation is more dangerous than doing it by hand once, so it needs review the ticket cannot skip.
- It only gets used during the next incident, which is exactly when nobody trusts an untested script.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: turn a manual recovery step into a reviewed script with a dry-run mode. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means dry-run output attached, the real execution stays with the team, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.