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
- Build Verification — does it compile/build cleanly?
- Test Verification — do all tests pass?
- Environment Config — are all env vars set?
- Security Basics — no secrets in code, no debug mode?
- Database — migrations applied, rollback tested?
- Infrastructure — Docker builds, health checks pass?
- 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
# 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
1---2name: deployment-checklist3version: 1.2.04description: |5 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".6requires_agent_teams: false7requires_claude_code: true8min_plan: starter9owns:10 directories: []11 patterns: []12 shared_read: ["*"]13allowed-tools: ["Read", "Write", "Bash", "Glob", "Grep"]14composes_with: ["infrastructure-agent", "qe-agent", "security-agent", "observability-agent"]15spawned_by: ["orchestrator"]16metadata:17 source: https://skillmd.com/skills/ivy00johns/deployment-checklist18---1920# Deployment Checklist2122Run pre-deployment verification before pushing to staging or production.2324## Role2526You 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.2728## Inputs2930- **Target environment** — `staging` or `production` (determines which checks apply and which URLs to verify)31- **QA report** — the qe-agent's `qa-report.json` must show `gate_decision.proceed: true` before you run; if QA hasn't passed, block deployment32- **Infrastructure state** — the infrastructure-agent should have completed Docker builds, health check endpoints, and CI/CD config before this checklist runs33- **Project profile** — `CLAUDE.md` / `.claude/profile.yaml` for environment-specific commands and URLs3435## Coordination3637- **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.38- **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.39- **Orchestrator**: Report the final `READY / NOT READY` verdict to the orchestrator. Include the structured report so it can be appended to the build record.4041## Process4243Before 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.4445### Quick Reference46471. **Build Verification** — does it compile/build cleanly?482. **Test Verification** — do all tests pass?493. **Environment Config** — are all env vars set?504. **Security Basics** — no secrets in code, no debug mode?515. **Database** — migrations applied, rollback tested?526. **Infrastructure** — Docker builds, health checks pass?537. **Integration** — services connect, CORS works?5455## Reference Documents5657- **`references/pre-deploy.md`** — full ordered checklist (build, tests, env config, security, DB, infra, integration).58- **`references/assumption-audit.md`** — thinking move for surfacing unverified assumptions before sign-off.5960## Output6162```markdown63# Pre-Deployment Report64Environment: [staging | production]65Generated: [timestamp]6667## Results68| Check | Status | Notes |69|-------|--------|-------|70| Build | PASS/FAIL | |71| Tests | PASS/FAIL | X passed, Y failed |72| Env Config | PASS/FAIL | |73| Security | PASS/FAIL | |74| Database | PASS/FAIL | |75| Infrastructure | PASS/FAIL | |76| Integration | PASS/FAIL | |7778## Blockers (if any)79[List of issues preventing deployment]8081## Verdict82READY / NOT READY83```