shipping-and-launch

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

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

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 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 Checklist: Covers code quality, security, performance, accessibility, infrastructure, and documentation gates that must pass before shipping. - Feature Flags & Staged Rollouts: Defines a rollout sequence from internal team enablement through 5% canary to 100% with explicit advance/hold/rollback thresholds for error rate, latency, and business metrics. - Monitoring & Rollback Strategy: Specifies 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 checkout flow, use this Skill to verify the checklist, deploy behind a feature flag, canary to 5% of users, watch error rates against baseline, and roll back instantly if thresholds are breached. ## Quick Start Ask the AI to prepare a production launch plan with a pre-launch checklist, staged rollout schedule, 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 covers 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.

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, and gradually increase to 25%, 50%, and 100%. Monitor error rates and latency at each stage for 24-48 hours, advancing only when metrics stay within baseline thresholds.

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 is an error budget release gate?▼

An error budget release gate uses your SLO's allowed failure fraction to decide shipping readiness. Above 20% budget remaining you ship normally, 0-20% means slow rollouts only, and exhausted budget freezes feature work until reliability is restored.

When are feature flags not appropriate for a release?▼

Feature flags add overhead when changes are purely internal refactors with no user-facing behavior, and they should never be nested since that creates exponential test combinations. Every flag needs an owner, an expiration date, and cleanup within two weeks of full rollout.