# Deployment Checklist

> Run pre-deployment verification before pushing to staging or production — build, tests, env config, security, DB, infra, integration — and return a READY / NOT READY verdict. Trigger on: "pre-deploy check", "deployment checklist", "ready to ship", "is this ready for prod", "deploy readiness", "release checklist", "can we deploy", "verify the build", "pre-flight check".

- Skill: `ivy00johns/deployment-checklist` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add ivy00johns/deployment-checklist`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ivy00johns/deployment-checklist/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: ivy00johns (https://skillmd.com/u/ivy00johns)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/ivy00johns/deployment-checklist

---


# Deployment Checklist

Run pre-deployment verification before pushing to staging or production.

## Role

You verify that a build is ready for deployment by running through a structured checklist. You check build artifacts, environment configs, security basics, and integration health.

## Inputs

- **Target environment** — `staging` or `production` (determines which checks apply and which URLs to verify)
- **QA report** — the qe-agent's `qa-report.json` must show `gate_decision.proceed: true` before you run; if QA hasn't passed, block deployment
- **Infrastructure state** — the infrastructure-agent should have completed Docker builds, health check endpoints, and CI/CD config before this checklist runs
- **Project profile** — `CLAUDE.md` / `.claude/profile.yaml` for environment-specific commands and URLs

## Coordination

- **qe-agent**: Deployment-checklist runs *after* the QE gate passes. If `qa-report.json` shows `gate_decision.proceed: false`, do not proceed — report the blocker to the orchestrator.
- **infrastructure-agent**: Infrastructure-agent owns Docker, CI/CD, and deployment configs. Deployment-checklist *validates* their output (Docker builds, health checks, resource limits) but does not modify infrastructure files. Route infrastructure failures back to the infrastructure-agent via the orchestrator.
- **Orchestrator**: Report the final `READY / NOT READY` verdict to the orchestrator. Include the structured report so it can be appended to the build record.

## Process

Before running the checklist, apply the **assumption-audit** move (`references/assumption-audit.md`) to surface any unverified beliefs about the environment. Then run through `references/pre-deploy.md` in order. Each section must pass before moving to the next. Report results as a structured checklist.

### Quick Reference

1. **Build Verification** — does it compile/build cleanly?
2. **Test Verification** — do all tests pass?
3. **Environment Config** — are all env vars set?
4. **Security Basics** — no secrets in code, no debug mode?
5. **Database** — migrations applied, rollback tested?
6. **Infrastructure** — Docker builds, health checks pass?
7. **Integration** — services connect, CORS works?

## Reference Documents

- **`references/pre-deploy.md`** — full ordered checklist (build, tests, env config, security, DB, infra, integration).
- **`references/assumption-audit.md`** — thinking move for surfacing unverified assumptions before sign-off.

## Output

```markdown
# Pre-Deployment Report
Environment: [staging | production]
Generated: [timestamp]

## Results
| Check | Status | Notes |
|-------|--------|-------|
| Build | PASS/FAIL | |
| Tests | PASS/FAIL | X passed, Y failed |
| Env Config | PASS/FAIL | |
| Security | PASS/FAIL | |
| Database | PASS/FAIL | |
| Infrastructure | PASS/FAIL | |
| Integration | PASS/FAIL | |

## Blockers (if any)
[List of issues preventing deployment]

## Verdict
READY / NOT READY
```