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.
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.
/deploy-checklist $ARGUMENTS
## 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
Tell me about your deploy and I'll customize the checklist:
If ~~source control is connected:
If ~~CI/CD is connected:
If ~~monitoring is connected: