Deploy Checklist
Generate a production-ready deploy gate checklist with rollback triggers before you ship a release that touches CI, migrations, or feature flags.
Overview
Deploy Checklist is an agent skill for the Ship phase that generates a customizable pre-deploy, deploy, and post-deploy verification checklist with documented rollback triggers before production.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill deploy-checklistWhat is this skill?
- Three-phase markdown checklist: pre-deploy (7 gates), deploy (5 steps), post-deploy (4 follow-ups)
- Dedicated rollback-triggers block for error rate, P50 latency, and critical user-flow failures
- Customizes sections for database migrations, feature flags, canary deploys, and on-call notification
- Explicit 15-minute post-production monitoring window for error rates and latency
- Argument-hint driven invocation for a named service or release via /deploy-checklist
- Three checklist phases: pre-deploy, deploy, and post-deploy
- Pre-deploy section includes 7 verification items
- Deploy section includes 5 execution steps including 15-minute monitoring
Adoption & trust: 3k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to release but do not have a single, shared gate for CI status, migrations, feature flags, smoke tests, and when to roll back.
Who is it for?
Solo builders or tiny teams doing their own releases who want a consistent last-mile checklist before production, including migration or flag-heavy deploys.
Skip if: Fully automated continuous deployment pipelines that already enforce every gate in CI/CD with no human sign-off, or teams that only need deep security pentesting rather than release readiness.
When should I use this skill?
About to ship a release, deploying changes with database migrations or feature flags, verifying CI status and approvals before production, or documenting rollback triggers ahead of time.
What do I get? / Deliverables
You leave the session with a dated deploy checklist markdown file—pre-deploy, deploy, and post-deploy sections plus explicit rollback triggers—ready to execute or paste into your release runbook.
- Markdown deploy checklist with pre-deploy, deploy, and post-deploy sections
- Documented rollback triggers with quantified thresholds
- Release notes and stakeholder notification reminders in post-deploy
Recommended Skills
Journey fit
The skill is invoked immediately before shipping to production—verifying CI, approvals, staging, and go-live monitoring—which maps to Ship launch preparation rather than ongoing operations tuning. Output is a structured pre-deploy through post-deploy release ritual with smoke tests and stakeholder communication, which is canonical launch-prep work in the Ship phase.
How it compares
Use as a structured release template instead of ad-hoc chat reminders or a generic todo list with no rollback section.
Common Questions / FAQ
Who is deploy-checklist for?
Deploy Checklist is for solo and indie builders (and small teams) who ship their own services and want a standardized pre-production verification list tied to a named release or service.
When should I use deploy-checklist?
Use it in the Ship phase before production: when you are about to ship a release, need CI and approvals verified, are deploying migrations or feature flags, or want rollback triggers written down ahead of the deploy.
Is deploy-checklist safe to install?
It is procedural documentation that outputs a checklist in chat; review the Security Audits panel on this Prism page and your plugin source before enabling any connected tools referenced in CONNECTORS.md.
SKILL.md
READMESKILL.md - Deploy Checklist
# /deploy-checklist > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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.