shipping-and-launch

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

Updated May 21, 2026
One-click install
npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill shipping-and-launch-nicorevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/nicorevo/AI-SDLC-Template/tree/main/.opencode/skills/shipping-and-launch
Command: npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill shipping-and-launch-nicorevo

SYSTEM DOCUMENTATION & REQUIREMENTS

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 complete launch discipline so every deployment is reversible, observable, and incremental. ## Core Features & Use Cases - Pre-Launch Checklist: Covers code quality, security, performance, accessibility, infrastructure, and documentation gates that must pass before any deploy. - Feature Flags and Staged Rollouts: Defines a flag lifecycle and a canary sequence (team → 5% → 25% → 50% → 100%) with explicit metric thresholds for advancing, holding, or rolling back. - Monitoring and Rollback Strategy: Specifies what to monitor (error rates, latency, Core Web Vitals), post-launch verification steps, and a documented rollback plan with time estimates. - Use Case: Before releasing a new task-sharing feature, run the pre-launch checklist, deploy behind a feature flag, canary to 5% of users while watching error-rate thresholds, and keep a one-minute flag-based rollback ready. ## Quick Start Ask the agent to prepare a production launch plan with a pre-launch checklist, staged rollout, and rollback strategy for your upcoming 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 deployment checklist?▼

A production deployment checklist covers six areas: code quality (tests, lint, reviews), security (no secrets, dependency audits, headers), performance (Core Web Vitals, N+1 queries), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation (changelog, ADRs).

How to do a staged rollout with feature flags?▼

Deploy with the flag off, enable for internal team first, then canary to 5% of users while monitoring error rates and latency for 24-48 hours. 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 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). In the first hour, verify the health endpoint, error dashboards, and the critical user flow.

Do small changes still need feature flags and rollback plans?▼

Yes. Every deployment carries risk regardless of size, and even simple changes can break production. A feature flag acts as a kill switch, and a documented rollback plan ensures recovery in minutes instead of an improvised response during an incident.