production-deployment-phase
Standard Operating Procedure for /ship-prod phase. Automated staging→production promotion.
When & Why to Use This Skill
This Claude skill automates the critical transition from staging to production environments by following a rigorous Standard Operating Procedure (SOP). It streamlines the deployment pipeline through automated versioning, health checks, and release reporting, ensuring that software promotions are consistent, documented, and error-free.
Use Cases
- Automated Production Promotion: Execute a seamless transition of validated code from staging to production with built-in safeguards and standardized steps.
- Release Management and Versioning: Automatically handle semantic versioning (SemVer) and Git release tagging to maintain a clean and traceable deployment history.
- Post-Deployment Health Monitoring: Perform immediate system health checks and generate comprehensive 'ship reports' to verify successful deployment and facilitate team communication.
| name | production-deployment-phase |
|---|---|
| description | "Standard Operating Procedure for /ship-prod phase. Automated staging→production promotion." |
| allowed-tools | Read, Edit, Bash |
Production Deployment Phase: Standard Operating Procedure
Training Guide: Promote staging to production with versioning and release.
Phase Overview
Purpose: Production deployment with version bump and release Inputs: Validated staging deployment Outputs: Production deployment, release version, production ship report Expected duration: 15-30 minutes
Execution Steps
- Verify staging validation complete
- Bump version (semantic versioning)
- Deploy to production
- Run health checks
- Create git release tag
- Generate production ship report
- Monitor post-deploy
Common Mistakes
- Production deploy failures
- Rollback needed
- Monitoring alerts missed
Completion Criteria
- Deployed to production
- Version bumped and tagged
- Health checks pass
- Monitoring configured
This SOP guides production deployment.