Skills anthropics knowledge-work-plugins
deploy-checklist
- Use it when:
- You're about to ship a release, especially one with database migrations, feature flags or a breaking API change.
- You get:
- A Markdown checklist in four parts: pre-deploy, deploy, post-deploy, and rollback triggers on error rate, latency and a critical user flow.
- Covers:
- CI, review, migrations, flags, a rollback plan, staging and smoke tests, a canary, 15 minutes of monitoring, release notes and stakeholders.
- Adapts:
- Adds flag, migration or consumer-notification steps when you say your deploy has them.
- With connectors:
- It pulls the release diff, checks PR approvals and the CI pipeline, and pre-fills rollback thresholds from current monitoring baselines.
- Runs:
- As /deploy-checklist with a service or release name.
- Part of:
- The engineering plugin of Anthropic's knowledge-work plugins.
TL;DR
A checklist command from the engineering plugin of Anthropic's knowledge-work plugins. The checklist has four parts. Pre-deploy: tests passing in CI, code reviewed and approved, no known critical bugs, migrations tested, feature flags configured, a documented rollback plan and on-call notified. Deploy: staging first, smoke tests, production with a canary if available, 15 minutes watching error rates and latency, and key user flows verified. Post-deploy: metrics nominal, release notes or changelog updated, stakeholders notified, related tickets closed. Rollback triggers, set before the deploy: an error rate, a P50 latency and a critical user flow failing. Saying the deploy uses feature flags, includes a database migration or breaks an API adds matching steps. With source control connected it pulls the release diff and checks that all PRs are approved and merged; with CI/CD, that the pipeline is green; with monitoring, it pre-fills rollback thresholds from current baselines and sets up a post-deploy metric watch.
Summarizes the skill at ab4cb1c.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill deploy-checklist skills.sh pageSource on GitHubAll skills from anthropics/knowledge-work-plugins
- Total Downloads
- 5,800 on skills.sh, Nov 9, 2026
- Repo stars
- 35,234 anthropics/knowledge-work-plugins
- First seen
- Mar 13, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 101 |
| Sep 28 | 95 |
| Oct 5 | 66 |
| Oct 12 | 91 |
| Oct 19 | 95 |
| Oct 26 | 96 |
| Nov 2 | 78 |
| Nov 9 | 68 |
| Category |
Deploy, provision, observe and debug cloud apps. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A one-shot action you invoke by name, such as turning the conversation into a PRD. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics |
SKILL.md
From anthropics/knowledge-work-plugins at ab4cb1c. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: deploy-checklist
description: 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.
argument-hint: "[service or release name]"/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
## 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
- Run before every deploy — Even routine ones. Checklists prevent "I forgot to..."
- Customize once, reuse — Tell me your stack and I'll remember your deploy process.
- Include rollback criteria — Decide when to roll back before you deploy, not during.