shipping-and-launch

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

Updated May 5, 2026
One-click install
npx skills add https://github.com/UlaYuga/promo-preflight --skill shipping-and-launch-ulayuga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/UlaYuga/promo-preflight/tree/main/.agents/skills/shipping-and-launch
Command: npx skills add https://github.com/UlaYuga/promo-preflight --skill shipping-and-launch-ulayuga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying to production without a repeatable process leads to missed security checks, undetected regressions, and no way to recover when a release breaks. This Skill provides a structured launch workflow 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 and Staged Rollouts: Defines a flag lifecycle and a canary sequence (5% → 25% → 50% → 100%) with metric thresholds for advancing, holding, or rolling back. - Monitoring and Rollback Planning: Specifies what to monitor (error rates, latency, Core Web Vitals), post-launch verification steps, and a rollback plan template with trigger conditions. - Use Case: Before releasing a new feature, run the pre-launch checklist, deploy behind a feature flag, canary to 5% of users, and use the decision thresholds table to decide whether to advance or roll back. ## Quick Start Help me prepare a production launch plan with a pre-launch checklist, staged rollout, and rollback strategy for my 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, security, performance, accessibility, infrastructure, and documentation. Verify tests pass, no secrets exist in code, Core Web Vitals meet thresholds, environment variables are set, and a rollback plan is documented before deploying.

How to do a staged rollout with feature flags?▼

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

When should I roll back a production deployment?▼

Roll back when error rates exceed 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 error rates by endpoint, p50/p95/p99 latency, request volume, Core Web Vitals, client JavaScript errors, and infrastructure metrics like CPU, memory, and database connection pools. Check these within the first hour after launch.

What are common mistakes when shipping to production?▼

Common mistakes include deploying without a rollback plan, skipping monitoring, big-bang releases without staging, feature flags with no owner or expiration, and shipping late on Fridays. Each is avoidable with checklists and staged rollouts.