← ClaudeAtlas

self-service-deliverylisted

Deliver a change to production yourself instead of handing steps to the requester. Use when: work has to actually land — push/PR, database migration, deploy, production data fix, config change — or when you are about to write 'please run this' / 'paste this SQL' / 'double-click this'. Do NOT use when: you are still investigating a root cause.
RICK-ORPHEN/agent-discipline-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill RICK-ORPHEN/agent-discipline-skills
# Deliver the change to production yourself Writing the code is half of it. The other half is getting it into production and proving that it landed. **Do not hand that half to the requester.** This document depends on no particular tool or company. Specific names belong in each project's own runbook. --- ## 1. Do not hand steps to a human "Double-click this", "paste this SQL", "click here" are not deliverables. What you hand over is **the result and the verification.** The only exceptions are things genuinely only that person can do — entering a password or payment details, identity verification, final approval of an irreversible deletion. In those cases, hand over **click-by-click instructions**, not abstract operational steps. ## 2. Choose the route by "least likely to stall" ``` API > your own execution environment > their machine (remote shell, GUI control) ``` The further right, the more fragile. Their machine stalls easily: another process holds it, the shell stops responding, an app will not come to the front. **Do not start a design assuming the most fragile route.** Ask first whether the work can be done through an API alone, and leave on their machine only the parts that cannot. If you get stuck, do not keep waiting. Wait a few minutes, and if nothing moves, **change route.** A plan with only one route stops being a plan the moment that route blocks. ## 3. When you think "a human has to do this", look for the key first **This is the biggest one.**