shipping-and-launch

Prepares production launches with pre-launch checklists, staged rollouts, monitoring, and rollback plans.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill shipping-and-launch-qiuyi-hong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/Qiuyi-Hong/addyosmani-skills/tree/main/skills/shipping-and-launch
Command: npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill shipping-and-launch-qiuyi-hong

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 the entire launch process so every deployment 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 shipping. - Feature Flags & Staged Rollouts: Guides a deploy-dark, canary-at-5%, then 25% to 50% to 100% rollout with explicit advance/hold/rollback thresholds for error rate, latency, and business metrics. - Monitoring & Rollback Strategy: Defines what to monitor (application, infrastructure, client metrics), post-launch verification steps, error budget release gates, and a documented rollback plan with time estimates. - Use Case: Before releasing a new task-sharing feature, use this Skill to verify the pre-launch checklist, ship behind a feature flag, canary to 5% of users, and roll back instantly if error rates exceed 2x baseline. ## Quick Start Ask the agent to prepare a production launch plan with a pre-launch checklist, staged rollout, and rollback strategy for your feature.

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 launch checklist before deploying?

A production launch checklist covers code quality (tests, lint, review), security (no secrets, dependency audits, CORS), performance (Core Web Vitals, bundle size), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation. All sections must pass before deploying.

How to do a staged rollout with feature flags?

Deploy with the flag off, enable for internal team first, then canary to 5% of users, and increase through 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. A feature flag rollback takes under a minute; redeploying a previous version takes under five minutes.

What is an error budget release gate?

An error budget release gate uses your SLO's remaining failure allowance to decide shipping pace. Above 20% budget remaining you ship normally, between 0-20% you slow rollouts, and when exhausted you freeze feature work to focus on reliability.

What metrics should I monitor after a production launch?

Monitor application metrics (error rate, p50/p95/p99 latency, request volume), infrastructure metrics (CPU, memory, database connections), and client metrics (Core Web Vitals, JavaScript errors). In the first hour, verify the health endpoint, error dashboards, and the critical user flow.