staging-validation-phase
Standard Operating Procedure for staging validation. Manual testing before production.
When & Why to Use This Skill
This Claude skill provides a structured Standard Operating Procedure (SOP) for staging validation, designed to ensure software stability before production deployment. It helps teams minimize release risks by guiding the agent through smoke tests, critical user flow verification, and data migration audits, ensuring a formal sign-off process is followed.
Use Cases
- Pre-production Sign-off: Executing a final manual and automated checklist on the staging environment to authorize a production release.
- Smoke Testing: Performing rapid verification of core system functionalities immediately after a deployment to catch major regressions early.
- Data Migration Verification: Ensuring that database schema changes and data migrations have executed correctly in a staging environment before applying them to live data.
- Release Risk Mitigation: Following a standardized rollback and validation protocol to ensure the system can recover if the staging deployment fails.
| name | staging-validation-phase |
|---|---|
| description | "Standard Operating Procedure for staging validation. Manual testing before production." |
| allowed-tools | Read, Edit, Bash |
Staging Validation Phase: Standard Operating Procedure
Training Guide: Validate staging deployment before promoting to production.
Phase Overview
Purpose: Manual testing on staging, smoke tests, sign-off Inputs: Staging deployment Outputs: Validation report, sign-off decision Expected duration: 30-60 minutes
Execution Steps
- Run smoke tests on staging
- Test critical user flows
- Verify data migrations
- Check rollback capability
- Sign-off decision (approve/reject)
Common Mistakes
- Validation steps skipped
- Smoke tests insufficient
- Sign-off unclear
Completion Criteria
- Smoke tests pass
- Critical flows verified
- Sign-off documented
This SOP guides staging validation.