shipping-and-launch

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

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/memasanz/agent-harness --skill shipping-and-launch-memasanz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/memasanz/agent-harness/tree/main/.github/skills/shipping-and-launch
Command: npx skills add https://github.com/memasanz/agent-harness --skill shipping-and-launch-memasanz

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 when things go wrong. This Skill provides a complete launch framework 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 that must pass before any deploy. - Feature Flags and Staged Rollouts: Guides deployment behind flags with a canary sequence (5% → 25% → 50% → 100%) and metric thresholds for advancing, holding, or rolling back. - Monitoring and Rollback Planning: Defines what to monitor (error rates, latency, Core Web Vitals), post-launch verification steps, and a documented rollback plan with trigger conditions. - Use Case: You are about to release a new task-sharing feature. Use this Skill to verify the pre-launch checklist, configure a feature flag, roll out to 5% of users, watch error-rate dashboards, and keep a one-minute rollback path ready. ## Quick Start Ask the agent to prepare a production launch plan with a pre-launch checklist, staged rollout schedule, and rollback strategy for your upcoming feature 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 launch checklist before deploying?

A production launch checklist covers six areas: code quality (tests, lint, reviews), security (no secrets, audit clean, headers), performance (Core Web Vitals, no N+1 queries), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation. All sections must pass before deploying.

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 while monitoring error rates and latency for 24-48 hours. Advance through 25%, 50%, and 100% only if metrics stay within thresholds, then remove 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, data integrity problems appear, or a security vulnerability is discovered. Feature flag rollbacks take under a minute; redeploying a previous version takes under five minutes.

What metrics should I monitor after a production deploy?

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 the health endpoint, check for new error types, and manually test the critical user flow.

What are the limitations of feature flag rollouts?

Feature flags add complexity when nested, since combinations grow exponentially, and stale flags create dead code paths. Every flag needs an owner and expiration date, both flag states must be tested in CI, and flags should be cleaned up within two weeks of full rollout.