Deploy Checklist

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Pre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production, or documenting rollback triggers ahead of time.

FeaturedInstructions onlyDevOps & Cloud
AI-generated overview

Generates a pre-deployment readiness checklist covering pre-deploy, deploy, post-deploy and rollback triggers.

What it does
Produces a markdown checklist for a named service or release, organized into Pre-Deploy, Deploy, Post-Deploy and Rollback Triggers sections. Items cover CI test status, code review and approval, database migrations, feature flags, staging verification, smoke tests, canary deploys, metric monitoring and stakeholder notification. The checklist is customized based on details the user provides, such as feature flags, database migrations or breaking API changes.
When to use it
Use when about to ship a release or deploy a change, especially one involving database migrations or feature flags. Also useful for verifying CI status and approvals before going to production, or for documenting rollback triggers in advance. Intended to be run before every deploy, including routine ones.
Requirements
No scripts; instructions only. Connectors for source control, CI/CD and monitoring are optional and only enrich the checklist.

/deploy-checklist

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Generate a pre-deployment checklist to verify readiness before shipping.

Usage

/deploy-checklist $ARGUMENTS

Output

markdown
## Deploy Checklist: [Service/Release]**Date:** [Date] | **Deployer:** [Name]
### Pre-Deploy- [ ] All tests passing in CI- [ ] Code reviewed and approved- [ ] No known critical bugs in release- [ ] Database migrations tested (if applicable)- [ ] Feature flags configured (if applicable)- [ ] Rollback plan documented- [ ] On-call team notified
### Deploy- [ ] Deploy to staging and verify- [ ] Run smoke tests- [ ] Deploy to production (canary if available)- [ ] Monitor error rates and latency for 15 min- [ ] Verify key user flows
### Post-Deploy- [ ] Confirm metrics are nominal- [ ] Update release notes / changelog- [ ] Notify stakeholders- [ ] Close related tickets
### Rollback Triggers- Error rate exceeds [X]%- P50 latency exceeds [X]ms- [Critical user flow] fails

Customization

Tell me about your deploy and I'll customize the checklist:

  • "We use feature flags" → adds flag verification steps
  • "This includes a database migration" → adds migration-specific checks
  • "This is a breaking API change" → adds consumer notification steps

If Connectors Available

If ~~source control is connected:

  • Pull the release diff and list of changes
  • Verify all PRs are approved and merged

If ~~CI/CD is connected:

  • Check build and test status automatically
  • Verify pipeline is green before deploy

If ~~monitoring is connected:

  • Pre-fill rollback trigger thresholds from current baselines
  • Set up post-deploy metric watch

Tips

  1. Run before every deploy — Even routine ones. Checklists prevent "I forgot to..."
  2. Customize once, reuse — Tell me your stack and I'll remember your deploy process.
  3. Include rollback criteria — Decide when to roll back before you deploy, not during.

Source and attribution

Source:anthropics/knowledge-work-pluginsinengineering/skills/deploy-checklistat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today