$npx -y skills add anthropics/knowledge-work-plugins --skill deploy-checklistPre-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.
| 1 | # /deploy-checklist |
| 2 | |
| 3 | > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). |
| 4 | |
| 5 | Generate a pre-deployment checklist to verify readiness before shipping. |
| 6 | |
| 7 | ## Usage |
| 8 | |
| 9 | ``` |
| 10 | /deploy-checklist $ARGUMENTS |
| 11 | ``` |
| 12 | |
| 13 | ## Output |
| 14 | |
| 15 | ```markdown |
| 16 | ## Deploy Checklist: [Service/Release] |
| 17 | **Date:** [Date] | **Deployer:** [Name] |
| 18 | |
| 19 | ### Pre-Deploy |
| 20 | - [ ] All tests passing in CI |
| 21 | - [ ] Code reviewed and approved |
| 22 | - [ ] No known critical bugs in release |
| 23 | - [ ] Database migrations tested (if applicable) |
| 24 | - [ ] Feature flags configured (if applicable) |
| 25 | - [ ] Rollback plan documented |
| 26 | - [ ] On-call team notified |
| 27 | |
| 28 | ### Deploy |
| 29 | - [ ] Deploy to staging and verify |
| 30 | - [ ] Run smoke tests |
| 31 | - [ ] Deploy to production (canary if available) |
| 32 | - [ ] Monitor error rates and latency for 15 min |
| 33 | - [ ] Verify key user flows |
| 34 | |
| 35 | ### Post-Deploy |
| 36 | - [ ] Confirm metrics are nominal |
| 37 | - [ ] Update release notes / changelog |
| 38 | - [ ] Notify stakeholders |
| 39 | - [ ] Close related tickets |
| 40 | |
| 41 | ### Rollback Triggers |
| 42 | - Error rate exceeds [X]% |
| 43 | - P50 latency exceeds [X]ms |
| 44 | - [Critical user flow] fails |
| 45 | ``` |
| 46 | |
| 47 | ## Customization |
| 48 | |
| 49 | Tell me about your deploy and I'll customize the checklist: |
| 50 | - "We use feature flags" → adds flag verification steps |
| 51 | - "This includes a database migration" → adds migration-specific checks |
| 52 | - "This is a breaking API change" → adds consumer notification steps |
| 53 | |
| 54 | ## If Connectors Available |
| 55 | |
| 56 | If **~~source control** is connected: |
| 57 | - Pull the release diff and list of changes |
| 58 | - Verify all PRs are approved and merged |
| 59 | |
| 60 | If **~~CI/CD** is connected: |
| 61 | - Check build and test status automatically |
| 62 | - Verify pipeline is green before deploy |
| 63 | |
| 64 | If **~~monitoring** is connected: |
| 65 | - Pre-fill rollback trigger thresholds from current baselines |
| 66 | - Set up post-deploy metric watch |
| 67 | |
| 68 | ## Tips |
| 69 | |
| 70 | 1. **Run before every deploy** — Even routine ones. Checklists prevent "I forgot to..." |
| 71 | 2. **Customize once, reuse** — Tell me your stack and I'll remember your deploy process. |
| 72 | 3. **Include rollback criteria** — Decide when to roll back before you deploy, not during. |