shipping-and-launch

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

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/insightriot/signal --skill shipping-and-launch-insightriot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/insightriot/signal/tree/main/plugin/skills/ship/shipping-and-launch
Command: npx skills add https://github.com/insightriot/signal --skill shipping-and-launch-insightriot

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 regressions, and no way to recover quickly. This Skill provides a disciplined 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: Decouples deployment from release with a flag lifecycle and a canary sequence (5% → 25% → 50% → 100%) governed by explicit advance/hold/rollback thresholds. - Monitoring and Rollback Plans: Defines what to monitor post-launch, error reporting patterns, and a documented rollback plan with trigger conditions and time-to-rollback targets. - Use Case: You are releasing a new task-sharing feature to production. Use this Skill to verify the pre-launch checklist, deploy behind a feature flag, canary to 5% of users while watching error-rate and latency thresholds, then roll out fully and clean up the flag. ## Quick Start Ask the AI to walk you through the shipping-and-launch checklist and build a rollout and rollback plan for your 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 deploy a feature to production safely?▼

Deploy behind a feature flag with the flag off, enable it for internal users first, then canary to 5% of users while monitoring error rates and latency. Advance through 25%, 50%, and 100% only when metrics stay within defined thresholds.

What should a pre-launch checklist include before release?▼

A pre-launch checklist should cover code quality (tests, lint, review), security (no secrets, dependency audit, auth checks), performance (Core Web Vitals, query indexes), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation updates.

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, data integrity problems appear, or a security vulnerability is discovered. Feature flag rollbacks take under a minute; redeploys under five minutes.

How do feature flags work for staged rollouts?▼

Deploy code with the flag off, enable it for team members, then gradually increase exposure from 5% to 100% of users while monitoring at each stage. Every flag needs an owner and expiration date, and should be removed within two weeks of full rollout.

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). In the first hour, verify health checks, error dashboards, and the critical user flow.