shipping-and-launch

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

2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill shipping-and-launch-moofonli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/MoofonLi/dev-ready/tree/main/src/dev_ready/templates/claude/skills/shipping-and-launch
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill shipping-and-launch-moofonli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying to production without a checklist, monitoring, or a rollback plan leads to undetected failures, big-bang releases, and slow incident response. 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 any deploy. - Feature Flags and Staged Rollouts: Defines 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: Specifies what to monitor (application, infrastructure, client metrics), post-launch verification steps, and a documented rollback plan with trigger conditions and time estimates. - Use Case: Before releasing a new task-sharing feature, run the checklist, deploy behind a feature flag, canary to 5% of users while watching error rates, then roll out gradually with a documented rollback path. ## Quick Start Ask the agent 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 deployment checklist?

A production deployment checklist covers code quality (tests, lint, reviews), security (no secrets, dependency audits, headers), performance (Core Web Vitals, query indexes), accessibility (WCAG 2.1 AA), infrastructure (env vars, SSL, health checks), and documentation updates before launch.

How to do a staged rollout with feature flags?

Deploy with the flag off, enable for internal users, then canary to 5% of users while monitoring error rates and latency. Advance through 25%, 50%, and 100% only if metrics stay within thresholds, and remove the flag after full rollout.

When should I roll back a production deployment?

Roll back when error rates exceed 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 common mistakes when shipping to production?

Common mistakes include deploying without a rollback plan, skipping monitoring, big-bang releases without staging, feature flags with no owner or expiration, and relying on staging behavior to predict production. Each is avoidable with checklists and staged rollouts.