More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Launch Runbook: Go-Live and Rollback

    1

    Build a go-live runbook that survives 2am: timed cutover steps with owners and undos, pre-agreed rollback triggers, a comms cadence, and the first-week watch.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Launch Runbook: Go-Live and Rollback

    Launch Runbook: Go-Live and Rollback

    Example session with this skill installed

    We're moving our booking SaaS to a new host Friday at 11pm — database migration plus a DNS switch. It's me and two engineers. Give me the runbook spine: countdown, cutover, and the triggers we should agree on now.

    • Read your context and instructions
    • Compiled the launch runbook

    Here is the spine, built to the three rules: every step owned, checked, and reversible; decision rights named; rollback tested before Friday.

    Countdown: scope freezes tonight — anything added after needs your sign-off by name. Wednesday: lower DNS TTLs to 300s (propagation is the one thing you can't rush Friday). Thursday: full rehearsal out loud, including running the rollback in staging and timing it. Friday 10pm: go/no-go against the checklist; any unchecked box means move or shrink, never "fix it live."

    Cutover (you = lead, Eng A = ops, Eng B = backend):
    T+0:00 Announce start in the launch channel. Check: both ack.
    T+0:05 Snapshot and back up the production database. Check: restore verified on staging copy.
    T+0:15 Run the migration. Check: log clean, row counts match source.
    T+0:25 Deploy the new build on the new host, traffic still pointed at old. Check: health endpoint 200, version string correct.
    T+0:35 Smoke test as a stranger: signup, create a booking, pay a test transaction. Check: all three green.
    T+0:45 Flip DNS. Check: new host resolving from two networks.
    T+1:00 Verify from a phone on mobile data. Check: booking flow works end to end.
    T+1:15 Announce live; watch window starts.

    Rollback triggers, agreed now: error rate above 5% of this week's baseline for 10 minutes, any failed test payment, or a migration row-count mismatch — any one fires, you call rollback, no debate. Performance sag past 30% is your judgment call with one 15-minute investigation cycle, then decide. Rollback order: DNS back first, then declare the old host primary; the new database is discarded, so no reverse migration is needed — that's why the backup check sits at T+0:05.

    Comms: updates in the status channel every 15 minutes during the window even if the update is "on track." Customer announcement and support one-pager drafted Thursday, released on your word after the T+1:00 check. On-call rota covers the first 24 hours; first-day watch compares bookings and error rates against baseline.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most launches don't fail on technology; they fail on choreography — a step nobody owned, a rollback nobody had ever run, a decision nobody was empowered to make at 2am. This skill builds the document that prevents all three: a countdown from scope freeze to launch day, a numbered cutover script where every step carries an owner, a verification check, and an undo, rollback triggers agreed in numbers before launch day (split into no-debate hard triggers and lead-decides judgment calls), a comms clock with a fixed update cadence and pre-drafted external messages, and watch checklists for the first hour, day, and week. It includes a fill-in runbook template, a go/no-go checklist where any unchecked box means "no" or a scope cut, a rollback decision table, and a complete worked example of a site-migration cutover with its triggers and a timed rollback.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    • It writes the runbook; your team still has to rehearse it and test the rollback — the skill insists on both but cannot do them for you.
    • Trigger thresholds are set from your baselines; if you have no baseline metrics yet, the first task the skill assigns is recording them.
    • Covers the operational go-live only — not pre-launch QA, incident response after the watch window, or launch marketing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Scale it down, keep the skeleton: named lead, one numeric rollback trigger, a tested undo, and a 15-minute comms rhythm. The full template is for cutovers; the three rules are for everything.

    Then the skill treats the launch plan as incomplete: shrink the change until the rollback is testable, or get the risk accepted in writing by whoever owns the launch. An untested rollback is the single most common gap the go/no-go checklist catches.

    Whoever can say "we're rolling back" without asking permission — and who will actually be awake and present for the whole window. The deputy needs the same authority, named in the runbook itself.

    New in Business & Operations