shipping-and-launch

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

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

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 disciplined launch workflow so every deployment is reversible, observable, and incremental. ## Core Features & Use Cases - Pre-Launch Checklists: Covers code quality, security, performance, accessibility, infrastructure, and documentation gates before any deploy. - Feature Flags and Staged Rollouts: Defines a flag lifecycle and a canary rollout sequence (5% → 25% → 50% → 100%) with explicit advance/hold/rollback thresholds for error rate, latency, and business metrics. - Monitoring and Rollback Planning: Specifies what to monitor post-launch, error reporting patterns, and a documented rollback plan with trigger conditions and time-to-recover 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 path. ## Quick Start Ask the AI 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 deployment checklist?▼

A production deployment checklist covers code quality (tests, lint, review), security (no secrets, audit clean, rate limiting), performance (Core Web Vitals, no N+1 queries), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation updates.

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 when metrics stay within thresholds, then remove the flag after full rollout.

When should I roll back a production deployment?▼

Roll back 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). Check health endpoints and error dashboards within the first hour after launch.

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 assuming staging behavior guarantees production behavior. Every launch should be reversible, observable, and incremental.