shipping-and-launch

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

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Avistian/nba --skill shipping-and-launch-avistian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/Avistian/nba/tree/main/.cursor/skills/shipping-and-launch
Command: npx skills add https://github.com/Avistian/nba --skill shipping-and-launch-avistian

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 quickly. This Skill provides a disciplined launch workflow covering pre-launch verification, feature flags, staged rollouts, monitoring, and rollback planning 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 deploying. - Feature Flag & Staged Rollout Strategy: Defines a deploy-dark, canary-at-5%, then 25% → 50% → 100% rollout sequence 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, and a rollback plan template with trigger conditions and time-to-rollback targets. - Use Case: Before releasing a new task-sharing feature, use this Skill to verify the checklist, ship behind a feature flag, canary to 5% of users, watch error-rate dashboards, and roll back in under a minute if error rates double. ## 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 should cover code quality (tests, lint, review), security (no secrets, dependency audits, auth checks), performance (Core Web Vitals, query indexes), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation updates before any release.

How to do a staged rollout with feature flags?▼

Deploy with the flag off, enable for internal users first, then canary to 5% of users while monitoring error rates and latency for 24-48 hours. Advance through 25%, 50%, and 100% only if metrics stay within thresholds, then remove the flag after full rollout.

When should I roll back a production deployment?▼

Roll back immediately when error rates exceed 2x baseline, P95 latency rises more than 50%, user-reported issues spike, or data integrity or security problems appear. A feature flag rollback takes 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). 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 within about two weeks of full rollout, and nesting flags creates exponential test combinations. Both flag states must be tested in CI, and every flag needs an owner and expiration date to stay manageable.