shipping-and-launch

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

5|Updated Mar 5, 2024
One-click install
npx skills add https://github.com/TRAPZZY/God-Eyes --skill shipping-and-launch-trapzzy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/TRAPZZY/God-Eyes/tree/main/.skills/shipping-and-launch
Command: npx skills add https://github.com/TRAPZZY/God-Eyes --skill shipping-and-launch-trapzzy

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 quickly. This Skill provides a disciplined 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 gates before any deploy. - Feature Flag Strategy: Decouples deployment from release with a defined flag lifecycle, ownership rules, and cleanup deadlines. - Staged Rollout with Thresholds: Defines a canary sequence (5% → 25% → 50% → 100%) with explicit advance/hold/rollback metrics for error rate, latency, and business KPIs. - Monitoring and Rollback Plans: Specifies what to monitor post-launch and provides a rollback plan template with trigger conditions and time-to-recovery targets. - Use Case: Before releasing a new task-sharing feature, use this Skill to verify the checklist, deploy behind a flag, canary to 5% of users, and roll back instantly if error rates double. ## Quick Start Use the shipping-and-launch skill to prepare a pre-launch checklist and staged rollout plan for my upcoming production 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, reviews), security (no secrets, dependency audits, CORS), performance (Core Web Vitals, bundle size), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), 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 canary to 5% of users while monitoring error rates and latency. Gradually increase to 25%, 50%, and 100%, advancing only when metrics stay within defined thresholds, then remove the flag.

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 verify the critical user flow manually.

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 relying on staging behavior to predict production. Production has different data and traffic patterns.