shipping-and-launch

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

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/nntoan/ultra-omp --skill shipping-and-launch-nntoan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/nntoan/ultra-omp/tree/main/packages/proflow/skills/shipping-and-launch
Command: npx skills add https://github.com/nntoan/ultra-omp --skill shipping-and-launch-nntoan

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 complete launch framework 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 & 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 & Rollback Planning: 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, run the pre-launch checklist, deploy behind a feature flag, canary to 5% of users while watching error rates against the thresholds table, and keep 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?▼

Use the pre-launch checklist covering six areas: code quality, security, performance, accessibility, infrastructure, and documentation. Each section lists concrete verification items such as passing tests, dependency audits, Core Web Vitals thresholds, and health check endpoints.

How to do a staged rollout with feature flags?▼

Deploy with the flag off, enable for internal users, then canary to 5% of users before increasing to 25%, 50%, and 100%. Monitor error rates and latency at each stage and advance only when metrics stay within the defined green 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 is an error budget release gate?▼

An error budget gate uses your SLO's allowed failure fraction to decide release pace. 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 health checks, error dashboards, and the critical user flow.