shipping-and-launch

Guides production deployments with pre-launch checklists, staged rollouts, and rollback plans.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/ByronWilliamsCPA/plugin --skill shipping-and-launch-byronwilliamscpa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/ByronWilliamsCPA/plugin/tree/main/plugins/wff-code/skills/shipping-and-launch
Command: npx skills add https://github.com/ByronWilliamsCPA/plugin --skill shipping-and-launch-byronwilliamscpa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying to production without a checklist, monitoring, or a rollback plan leads to broken releases discovered by users 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, observability, accessibility, infrastructure, and documentation, with durable OPS-* manifest checks for items like restore drills and secret management. - Feature Flags and Staged Rollout: Defines a flag lifecycle and a staged rollout path (staging, canary at 5%, gradual to 100%) with explicit advance/hold/rollback thresholds for error rate, latency, and business metrics. - Rollback Strategy and Post-Launch Verification: Provides a rollback plan template with trigger conditions and time estimates, plus a first-hour verification loop after deploy. - Use Case: Before releasing a new feature, run the checklist, ship behind a feature flag, canary to 5% of users, monitor error rates against baseline, and roll back instantly if errors exceed 2x baseline. ## Quick Start Use the shipping-and-launch skill to prepare a pre-launch checklist and rollback plan for my upcoming production deployment.

Frequently Asked Questions about shipping-and-launch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a production deployment checklist?▼

A pre-launch checklist should cover code quality, security, performance, observability, accessibility, infrastructure, and documentation. This Skill provides all sections, including durable checks like restore-drill logs and secret-manager verification rather than simple checkbox states.

How to do a staged rollout with feature flags?▼

Deploy with the flag off, enable for internal users, then canary to 5% and gradually increase to 25%, 50%, and 100% while monitoring at each stage. Advance only when error rate stays within 10% of baseline and P95 latency within 20%.

When should I roll back a production deployment?▼

Roll back immediately when error rate exceeds 2x baseline, P95 latency rises more than 50%, user-reported issues spike, or data integrity or security problems appear. Treat any failed post-launch verification step as a rollback trigger, not a watch-and-see situation.

What should a rollback plan include?▼

A rollback plan needs trigger conditions, step-by-step rollback actions such as disabling the feature flag or reverting the commit, database migration considerations, and time-to-rollback estimates. Feature flags typically revert in under a minute; redeploys take under five minutes.

How long should feature flags live after full rollout?▼

Feature flags should be removed within two weeks of reaching full rollout, and every flag needs an owner and expiration date. Avoid nesting flags, and test both on and off states in CI to prevent untested code paths.