Skill

deploy-checklist

Generates customizable pre-deployment checklists to verify CI status, tests, reviews, migrations, feature flags, rollback plans, and monitor production deploys.

CI/CD

Git

devops

deployment

Install

npx claudepluginhub foundationforge/cowork-plugins --plugin engineering

Tool Access

This skill uses the workspace's default tool permissions.

Preview

> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).

SKILL.md

Similar Skills

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

152.2k

executing-plans

Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.

superpowers

152.2k

brainstorming

7 files

Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.

superpowers

152.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 12, 2026

Used By3 plugins

Actions

View Source View Plugin View on GitHub View README

Tags

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

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

/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.