shipping-and-launch

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

Updated May 13, 2026
One-click install
npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill shipping-and-launch-sapatamuku-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/sapatamuku-creator/mastersapatamuku/tree/main/releases/v2.7/.agents/skills/shipping-and-launch
Command: npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill shipping-and-launch-sapatamuku-creator

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 Checklist: Covers code quality, security, performance, accessibility, infrastructure, and documentation gates that must pass before any deploy. - 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, and a documented rollback plan with trigger conditions and time-to-rollback targets. - 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, then gradually roll out with a documented rollback plan ready. ## Quick Start Ask the assistant to prepare a production launch plan with a pre-launch checklist, staged rollout, and rollback strategy 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, reviews), security (no secrets, dependency audits, rate limiting), performance (Core Web Vitals, query indexes), 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 for 24-48 hours. Increase gradually to 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 error rate exceeds 2x baseline, P95 latency rises more than 50%, user-reported issues spike, data integrity problems appear, or a security vulnerability is discovered. 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, disk), 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 are the limitations of feature flag rollouts?▼

Feature flags add technical debt if not cleaned up—every flag needs an owner and expiration date, and should be removed within two weeks of full rollout. Nesting flags creates exponential test combinations, and both flag states must be tested in CI to avoid untested code paths.