shipping-and-launch

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

1|Updated Sep 4, 2026
One-click install
npx skills add https://github.com/SanHsien/agent-skills --skill shipping-and-launch-sanhsien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/SanHsien/agent-skills/tree/main/skills/shipping-and-launch
Command: npx skills add https://github.com/SanHsien/agent-skills --skill shipping-and-launch-sanhsien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying to production without a checklist, monitoring, or a rollback plan leads to avoidable outages and slow incident response. This Skill gives AI coding agents 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 Rollout: 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 & Rollback Strategy: Specifies what to monitor (application, infrastructure, client metrics), post-launch verification steps, error budget release gates, and a rollback plan template. - Use Case: Before releasing a new task-sharing feature, use this Skill to verify the checklist, deploy behind a feature flag, canary to 5% of users, and roll back automatically if error rates exceed 2x baseline. ## Quick Start Ask the agent 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 launch checklist before deploying?

A pre-launch checklist should cover code quality (tests, lint, review), security (dependency audits, auth, headers), performance (Core Web Vitals, N+1 queries), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation. All sections must pass before deploying.

How do I run a staged rollout with feature flags?

Deploy with the flag off, enable it 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, and 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, or data integrity or security problems appear. Feature flag rollbacks take under a minute; redeploying a previous version takes under five minutes.

What is an error budget release gate?

An error budget gate uses your SLO's allowed failure fraction to decide whether to ship. Above 20% budget remaining you ship normally, between 0-20% you slow rollouts, and when exhausted you freeze feature work to focus on reliability.

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). In the first hour, verify the health endpoint, error dashboards, and the critical user flow.