Goal
Assess whether software is actually ready to deploy to the intended environment.
When to Use
- Release or deployment is approaching.
- A new environment is being introduced.
- The team needs a pre-deploy hardening check.
Instructions
- Review runtime assumptions and environment config.
- Review secrets, dependencies, migrations, and external services.
- Review observability, rollback, and operator visibility.
- Return blockers and recommended fixes.
Constraints
- Do not confuse passing tests with deployment readiness.
- Make environment-specific blockers explicit.
- Treat missing rollback or visibility as deployment risk.
Output Format
- readiness verdict
- blockers
- should-fix items
- deployment notes
Examples
- "Review this API for staging deployment readiness."
- "What is missing before we ship this worker service?"