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

• 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 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

• Confirm metrics are nominal
• Update release notes / changelog
• Notify stakeholders
• Close related tickets

• Error rate exceeds [X]%
• P50 latency exceeds [X]ms
• [Critical user flow] fails

undefined

• "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

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

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

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

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.