shipping-and-launch

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

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/jampissarandev/Expense-Tracker --skill shipping-and-launch-jampissarandev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/jampissarandev/Expense-Tracker/tree/main/.github/skills/shipping-and-launch
Command: npx skills add https://github.com/jampissarandev/Expense-Tracker --skill shipping-and-launch-jampissarandev

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 errors, and no way to recover quickly. This Skill provides a repeatable launch workflow covering readiness checks, feature flags, staged rollouts, monitoring, and rollback planning. ## Core Features & Use Cases - Pre-Launch Checklist: Covers code quality, security, performance, accessibility, infrastructure, and documentation gates before any deploy. - Feature Flag & Staged Rollout Strategy: Defines a deploy-dark, team-enable, canary (5% → 25% → 50% → 100%) sequence with explicit advance/hold/rollback thresholds for error rate, latency, and business metrics. - Monitoring & Rollback Planning: Specifies what to monitor (application, infrastructure, client metrics), post-launch verification steps, and a rollback plan template with trigger conditions and time-to-rollback targets. - Use Case: Before releasing a new expense-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 documented rollback plan ready. ## Quick Start Ask the assistant 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 code quality (tests, lint, reviews), security (no secrets, dependency audits, rate limiting), performance (Core Web Vitals, query indexes), accessibility (WCAG 2.1 AA), infrastructure (env vars, migrations, health checks), and documentation updates.

What is a staged rollout with feature flags?

A staged rollout deploys code with the feature flag off, enables it for internal users, then gradually increases exposure from 5% to 25%, 50%, and 100% of users. Each stage includes a monitoring window comparing error rates and latency against baseline before advancing.

When should I roll back a production deployment?

Roll back 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 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). Verify health checks, logs, and the critical user flow within the first hour.

Do small changes still need feature flags and rollback plans?

Yes. Every deployment carries risk, and even simple changes can break in production due to different data and traffic patterns. A feature flag acts as a kill switch, and a documented rollback plan keeps recovery time under a few minutes.