Deployment Plan
Core Workflow
- Identify artifact, target environment, hosting model, dependencies, release owner, users affected, and approval requirements.
- Document pre-deploy checks: build, tests, migrations, config, secrets, capacity, observability, and support readiness.
- Define deployment steps, rollout order, smoke tests, monitoring, and communication points.
- Include rollback or fallback triggers before deployment begins.
- Separate dry-run, staging, canary, and production steps.
- Record owners, timing, risks, and go/no-go criteria.
Safety Rules
- Do not deploy, change production config, run migrations, or restart services without explicit approval.
- Do not claim a deployment is safe without validation evidence.
- Escalate deployments involving customer data, auth, billing, migrations, high traffic, regulated workloads, or broad availability.
Deliverable Shape
For deployment plans, provide:
- Target artifact and environment
- Preconditions
- Deployment steps
- Smoke tests and monitoring
- Rollout and communication plan
- Rollback triggers
- Owners and approvals
- Go/no-go criteria
References
- Read
references/deployment-plan-checklist.mdwhen preparing deployment plans or runbooks.