shipping-and-launch

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

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/NAMEWTA/learning-open-code --skill shipping-and-launch-namewta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/NAMEWTA/learning-open-code/tree/main/translator/open-ai-skills/addyosmani-agent-skills/skills/shipping-and-launch
Command: npx skills add https://github.com/NAMEWTA/learning-open-code --skill shipping-and-launch-namewta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying to production without a structured process leads to outages, undetected regressions, and irreversible releases. This Skill provides a disciplined framework for shipping features safely with checklists, monitoring, and rollback strategies. ## Core Features & Use Cases - Pre-Launch Checklists: Covers code quality, security, performance, accessibility, infrastructure, and documentation gates before any deployment. - Feature Flags & Staged Rollouts: Implements a flag lifecycle and a staged sequence (staging → internal → 5% → 25% → 50% → 100%) with go/no-go thresholds for error rate, latency, and business metrics. - Monitoring & Rollback Plans: Defines what to observe (application, infrastructure, client metrics), post-launch verification steps, and documented rollback triggers and procedures. - Use Case: Before releasing a new task-sharing feature, use this Skill to run the full pre-launch checklist, gate the feature behind a flag, roll out to 5% of users while watching error-rate thresholds, and keep a one-minute flag-disable rollback ready. ## Quick Start Ask the agent to prepare a production launch plan with a pre-launch checklist, staged rollout thresholds, and a rollback strategy for your upcoming feature deployment.

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, input validation, security headers), performance (Core Web Vitals, bundle size, query indexes), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, CDN), and documentation updates.

How to do a staged rollout with feature flags?▼

Deploy code with the flag off, enable it for internal team members, then roll out progressively to 5%, 25%, 50%, and 100% of users. At each stage, monitor error rates and latency against baseline thresholds before proceeding, and remove the flag within two weeks of full rollout.

When should I roll back a production deployment?▼

Roll back immediately when error rates exceed twice the baseline, P95 latency increases over 50%, user issue reports spike, data integrity problems appear, or a security vulnerability is discovered. Feature flag rollbacks take under a minute; redeploying a previous version takes under five minutes.

What metrics should I monitor after a production release?▼

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 endpoints, error dashboards, and key user flows within the first hour after launch.

What are the limitations of feature flag rollouts?▼

Feature flags add code complexity and require lifecycle management: each flag needs an owner and expiration date, nesting flags creates exponential combinations, and both flag states must be tested in CI. Flags also do not replace database migration rollback planning.