Deployment And Rollback Audit
Definition
Confirm the release can be deployed and, if necessary, safely rolled back. Production readiness includes deploy mechanics, not just code quality.
Questions To Ask
- What pipeline builds, tests, and deploys this release?
- Has the release deployed successfully to staging or an equivalent environment?
- What environment variables, secrets, and configuration differ in production?
- How do migrations interact with rollback?
- What smoke tests and release controls gate production?
Existing Project Comparison
- Inspect CI/CD config, deployment scripts, environment examples, migration order, release docs, smoke tests, and rollback instructions.
- Compare deploy steps against actual project tooling and hosting platform behavior.
- Check whether rollback restores safe code and data states.
Suggestive Plan
- Map build, staging, production, and rollback flow.
- Verify pipeline and staging evidence.
- Inspect config, secrets, migrations, and release controls.
- Confirm smoke tests and rollback steps are executable.
- Update
PRODUCTION_READINESS.md.
Example
For a billing release, verify staging deploy, migration apply, invoice smoke test, production config, rollback command, and post-rollback data compatibility.
Vocabulary
- Release control: gate that prevents unsafe production deployment.
- Smoke test: fast production-critical check after deploy.
- Rollback: returning code or configuration to a prior safe version.
- Staging: production-like environment used for release validation.
Expected Outcome
Produce a deployment audit with pipeline evidence, staging status, config risks, migration and rollback safety, smoke tests, blockers, and accepted risks.
1---2name: deployment-rollback-audit3description: Audit deployment and rollback readiness before production. Use when verifying build pipeline, staging deployment, environment configuration, migrations, smoke tests, release controls, rollback plan, and deploy safety.4---56# Deployment And Rollback Audit78## Definition910Confirm the release can be deployed and, if necessary, safely rolled back. Production readiness includes deploy mechanics, not just code quality.1112## Questions To Ask1314- What pipeline builds, tests, and deploys this release?15- Has the release deployed successfully to staging or an equivalent environment?16- What environment variables, secrets, and configuration differ in production?17- How do migrations interact with rollback?18- What smoke tests and release controls gate production?1920## Existing Project Comparison2122- Inspect CI/CD config, deployment scripts, environment examples, migration order, release docs, smoke tests, and rollback instructions.23- Compare deploy steps against actual project tooling and hosting platform behavior.24- Check whether rollback restores safe code and data states.2526## Suggestive Plan27281. Map build, staging, production, and rollback flow.292. Verify pipeline and staging evidence.303. Inspect config, secrets, migrations, and release controls.314. Confirm smoke tests and rollback steps are executable.325. Update `PRODUCTION_READINESS.md`.3334## Example3536For a billing release, verify staging deploy, migration apply, invoice smoke test, production config, rollback command, and post-rollback data compatibility.3738## Vocabulary3940- Release control: gate that prevents unsafe production deployment.41- Smoke test: fast production-critical check after deploy.42- Rollback: returning code or configuration to a prior safe version.43- Staging: production-like environment used for release validation.4445## Expected Outcome4647Produce a deployment audit with pipeline evidence, staging status, config risks, migration and rollback safety, smoke tests, blockers, and accepted risks.
harsh817