shipping-and-launch

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill shipping-and-launch-codecrafteradi2006
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/CodeCrafterAdi2006/Ink-and-Code/tree/main/Skills/shipping-and-launch
Command: npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill shipping-and-launch-codecrafteradi2006

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 when things go wrong. This Skill provides a complete launch framework covering pre-launch verification, 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 deployment. - 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% to 100%) with concrete advance, hold, and rollback decision thresholds for error rate, latency, and business metrics. - Monitoring and Rollback Plans: Specifies what to monitor post-launch and provides a rollback plan template with trigger conditions and time-to-recover 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, compare error rates against baseline, and advance or roll back based on the threshold table. ## Quick Start Ask the assistant to prepare a production launch plan with a pre-launch checklist, staged rollout schedule, and rollback strategy for your next 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 pre-launch checklist covers six areas: 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 health check endpoint responds before deploying.

How to do a staged rollout with feature flags?▼

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

When should I roll back a production deployment?▼

Roll back immediately when error rate exceeds 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 like error rate, p50/p95/p99 latency, and request volume; infrastructure metrics like CPU, memory, and database connections; and client metrics like Core Web Vitals and JavaScript errors. Check all dashboards within the first hour after deploying.

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 assuming staging behavior guarantees production behavior. Production has different data, traffic, and edge cases.