shipping-and-launch

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

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/visdomtech/skills --skill shipping-and-launch-visdomtech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/visdomtech/skills/tree/main/shipping-and-launch
Command: npx skills add https://github.com/visdomtech/skills --skill shipping-and-launch-visdomtech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying to production without a structured process leads to broken releases, undetected errors, and no way to recover quickly. This Skill provides a complete launch framework 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 Rollout: 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 & Rollback Strategy: Defines what to monitor (application, infrastructure, client metrics), post-launch verification steps, error budget release gates, and a documented rollback plan template. - 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 against the thresholds table, and keep a rollback plan ready that disables the flag in under a minute. ## Quick Start Ask the assistant to prepare a production launch plan with a pre-launch checklist, staged rollout, and rollback strategy for your upcoming release.

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?▼

A production launch checklist covers six areas: code quality (tests, lint, reviews), security (dependency audits, headers, rate limiting), performance (Core Web Vitals, N+1 queries), 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 it for internal team members, then canary to 5% of users while monitoring error rates and latency for 24-48 hours. Increase gradually through 25%, 50%, and 100%, advancing only when metrics stay within defined thresholds, then remove the flag after full rollout.

When should I roll back a production deployment?▼

Roll back immediately when the error rate exceeds 2x baseline, P95 latency rises more than 50%, user-reported issues spike, or data integrity or security problems appear. Feature flag rollbacks take under a minute; redeploying a previous version takes under five minutes.

What metrics should I monitor after a production deploy?▼

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

What is an error budget release gate?▼

An error budget release gate uses your SLO's allowed failure fraction to decide if it is safe to ship. Above 20% budget remaining you ship normally, between 0-20% you allow only slow rollouts, and when exhausted you freeze feature work to focus on reliability.

Do small changes still need feature flags and rollback plans?▼

Yes. Every deployment carries risk, and even simple changes can break production under real traffic and data. A feature flag acts as a kill switch, and a documented rollback plan with trigger conditions ensures recovery in minutes rather than hours.