shipping-and-launch

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

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/alissonpef/copilot_agent_skills --skill shipping-and-launch-alissonpef
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/alissonpef/copilot_agent_skills/tree/main/.github/skills/shipping-and-launch
Command: npx skills add https://github.com/alissonpef/copilot_agent_skills --skill shipping-and-launch-alissonpef

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 repeatable launch workflow covering readiness checks, feature flags, staged rollouts, monitoring, and rollback planning. ## Core Features & Use Cases - Pre-Launch Checklist: Covers code quality, security, performance, accessibility, infrastructure, and documentation verification before any deploy. - Feature Flag & Staged Rollout Strategy: Defines a deploy-to-staging, canary (5%), gradual (25% → 50% → 100%) rollout sequence with metric-based advance/hold/rollback thresholds. - Monitoring & Rollback Planning: Specifies application, infrastructure, and client metrics to watch, plus a documented rollback plan template with trigger conditions and time-to-rollback targets. - Use Case: Before releasing a new task-sharing feature, run the pre-launch checklist, deploy behind a feature flag, roll out to 5% of users while watching error rates and P95 latency, and keep a rollback plan ready in case thresholds are breached. ## Quick Start Ask the agent to prepare a production launch plan with a pre-launch checklist, staged rollout, and rollback strategy for your upcoming 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, reviews), security (no secrets, vulnerability audits, CORS), performance (Core Web Vitals, query indexes), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation updates.

How to do a staged rollout with feature flags?▼

Deploy with the flag off, enable it for internal team members, then roll out to 5% of users as a canary. Monitor error rates and latency for 24-48 hours, then increase to 25%, 50%, and 100%, advancing only when metrics stay within baseline thresholds.

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. 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 application metrics (error rate, p50/p95/p99 latency, request volume), infrastructure metrics (CPU, memory, database connections), and client metrics (Core Web Vitals, JavaScript errors). Check these within the first hour and at each rollout stage.

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. Every flag needs an owner, an expiration date, and tests covering both on and off states in CI.