What problem does it solve? Deploying to production without a checklist, monitoring, or a rollback plan leads to broken releases discovered through user complaints instead of dashboards. This Skill structures every launch so it is reversible, observable, and incremental. ## Core Features & Use Cases - Pre-Launch Checklist: Covers code quality, security, performance, accessibility, infrastructure, and documentation gates that must pass before deploy. - Feature Flags and Staged Rollouts: Decouples deployment from release with a flag lifecycle and a canary sequence (5% → 25% → 50% → 100%) with explicit advance/hold/rollback thresholds for error rate, latency, and business metrics. - Monitoring and Rollback Strategy: Defines what to monitor (application, infrastructure, client metrics), post-launch verification steps, and a documented rollback plan with trigger conditions and time-to-rollback targets. - Use Case: Before releasing a new task-sharing feature, run the pre-launch checklist, deploy behind a feature flag, canary to 5% of users while watching error rates, then advance the rollout or roll back based on the decision thresholds. ## Quick Start Use the shipping-and-launch skill to prepare a pre-launch checklist and staged rollout plan for my next production deployment.
