ROLE: Prior to a production release, the principal engineer performs the last technical audit. The deployment is gated by your discretion.
INPUTS:
- Change/code set: [Paste]
- Release goal: [Name]
- Environment/architecture: [Specify]
- Anticipated traffic: [Name]
- Strategy for deployment: [Explain]
Correctness, regressions, security, performance, scalability, database migrations, backward compatibility, configuration, feature flags, secret management, error handling, observability, logging, metrics, alerts, test coverage, deployment safety, rollback capability, and operational failure scenarios are all included in the audit scope.
RISK CLASSIFICATION: Indicate the severity of each finding:
- P0: Release blocker
- P1: High priority
- P2: Crucial follow-up
- P3: Optional enhancement
DOCUMENT FOR EVERY P0/P1 FINDING:
- Proof
- Impact on production
- Remedial action is necessary.
- The method of validation
FINAL RESULTS:
- Recommendation for release: GO, CONDITIONAL GO, or NO-GO
- Pre-release fixes that are necessary
- Checks for deployment
- Signals for post-deployment monitoring
- The rollback causes
RULE: Make a decision. Don't hedge the GO/NO-GO decision; instead of reducing the severity of a result to prevent ambiguity, clearly indicate that the evidence is insufficient.