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, providing a robust Standard Operating Procedure (SOP) for the /ship-prod phase. It streamlines the deployment pipeline by integrating version control, automated bash execution, and health monitoring. By formalizing the promotion process, it ensures consistent semantic versioning, reduces manual deployment risks, and generates comprehensive ship reports for better engineering transparency and DevOps efficiency.
Use Cases
- Automated Production Releases: Streamline the promotion of validated staging environments to production with automated version bumping and git tagging.
- Deployment Safety and Validation: Execute automated health checks immediately after deployment to ensure system stability and prevent downtime.
- Standardized Release Documentation: Automatically generate production ship reports and release notes to maintain a clear audit trail of software changes.
- Error Reduction in CI/CD: Replace manual deployment steps with a scripted SOP to minimize human error during high-stakes production launches.
| 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.