shipping-and-launch

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

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill shipping-and-launch-raishoemi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/raishoemi/traffic-sim-v2/tree/main/.github/skills/shipping-and-launch
Command: npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill shipping-and-launch-raishoemi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying to production without a structured process leads to broken releases, undetected errors, and no way to recover when things go wrong. This Skill provides a complete launch framework so every deployment is reversible, observable, and incremental. ## Core Features & Use Cases - Pre-Launch Checklists: Covers code quality, security, performance, accessibility, infrastructure, and documentation verification before any deploy. - Feature Flags & Staged Rollouts: Implements flag-based releases with a canary sequence (5% → 25% → 50% → 100%) and metric-based advance/hold/rollback thresholds. - Monitoring & Rollback Plans: Defines what to monitor (error rates, latency, Core Web Vitals), post-launch verification steps, and documented rollback triggers and procedures. - Use Case: Before releasing a new task-sharing feature in a React app, use this Skill to run the pre-launch checklist, deploy behind a feature flag, canary to 5% of users, and monitor error rates against baseline thresholds before full rollout. ## Quick Start Ask the agent to prepare a production launch plan with a pre-launch checklist, staged rollout strategy, and rollback plan for your upcoming feature 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 deployment checklist?

A production deployment checklist should cover code quality (tests, lint, build), security (no secrets, npm audit, CORS), performance (Core Web Vitals, bundle size), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation updates 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 while monitoring error rates and latency. Advance through 25%, 50%, and 100% only if metrics stay within thresholds, then clean up the flag after full rollout.

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. Feature flag rollbacks take under a minute; redeploying a previous version takes under five minutes.

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). Verify health checks, logs, and the critical user flow within the first hour.

What are the limitations of feature flag rollouts?

Feature flags add code complexity and require discipline: every flag needs an owner and expiration date, nesting flags creates exponential test combinations, and both flag states must be tested in CI. Flags should be removed within two weeks of full rollout.