shipping-and-launch

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

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill shipping-and-launch-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/marcmarti9/agentit/tree/main/skills/shipping-and-launch
Command: npx skills add https://github.com/marcmarti9/agentit --skill shipping-and-launch-marcmarti9

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 so every deployment is reversible and observable. ## Core Features & Use Cases - Pre-Launch Checklist: 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%) with explicit advance/hold/rollback thresholds for error rate, latency, and business metrics. - Monitoring and Rollback Strategy: Defines what to monitor post-launch, error budget release gates, and a documented rollback plan with trigger conditions and time-to-rollback targets. - Use Case: Before releasing a new task-sharing feature, run the pre-launch checklist, ship the code behind a feature flag, canary it to 5% of users while watching error rates, and keep a rollback plan ready in case thresholds turn red. ## 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 launch checklist?▼

A production launch checklist covers code quality, security, performance, accessibility, infrastructure, and documentation. Verify tests pass, dependency audits show no critical vulnerabilities, environment variables are set, health checks respond, and monitoring is configured before deploying.

How to do a staged rollout with feature flags?▼

Deploy code with the flag off, enable it for internal users, then canary to 5% of users while monitoring error rates and latency. Increase gradually 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 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.

What metrics should I monitor after a deployment?▼

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 of these within the first hour after launch.

What is an error budget release gate?▼

An error budget release gate uses your SLO's allowed failure fraction to decide if it is safe to ship. Above 20% budget remaining you ship normally, at 0-20% you slow rollouts, and when exhausted you freeze feature work to focus on reliability.