shipping-and-launch

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

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill shipping-and-launch-kunj-sharma03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/templates/skills/shipping-and-launch
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill shipping-and-launch-kunj-sharma03

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 complete launch framework covering readiness checks, gradual rollouts, observability, and rollback planning. ## Core Features & Use Cases - Pre-Launch Checklist: Covers code quality, security, performance, accessibility, infrastructure, and documentation gates before any deploy. - Feature Flags & Staged Rollout: Decouples deployment from release with a canary sequence (5% → 25% → 50% → 100%) and metric-based advance/hold/rollback thresholds. - Monitoring & Rollback Strategy: Defines what to monitor (error rates, latency, Core Web Vitals), post-launch verification steps, and a documented rollback plan with trigger conditions. - Use Case: Before releasing a new task-sharing feature, run the checklist, deploy behind a feature flag, enable it for 5% of users, watch error rates against baseline for 48 hours, then advance the rollout or roll back using the documented plan. ## Quick Start Ask the agent to prepare a production launch plan with a pre-launch checklist, staged rollout, 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 deployment checklist?

A pre-launch checklist should cover code quality (tests, lint, review), security (no secrets, dependency audits, CORS), performance (Core Web Vitals, N+1 queries), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, SSL), and documentation updates 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, then remove the flag after full rollout.

When should I roll back a production deployment?

Roll back immediately when error rates exceed 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). Check dashboards within the first hour and verify the critical user flow manually.

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 rather than hours.