shipping-and-launch

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

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

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 repeatable launch workflow 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: Decouples deployment from release with a flag lifecycle and a canary sequence (5% → 25% → 50% → 100%) governed by explicit advance/hold/rollback thresholds for error rate, latency, and business metrics. - Monitoring and Rollback Strategy: Defines what to monitor (application, infrastructure, client metrics), post-launch verification steps, and a documented rollback plan with trigger conditions and time-to-rollback targets. - Use Case: Before releasing a new task-sharing feature, run the checklist, deploy behind a feature flag, enable it for the internal team, then canary to 5% of users while watching error rates against baseline before full rollout. ## 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 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, health checks), and documentation updates before any deploy.

How to do a staged rollout with feature flags?▼

Deploy with the flag off, enable it for internal team members, then canary to 5% of users while monitoring error rates and latency against baseline. Increase gradually through 25%, 50%, and 100%, holding or rolling back if error rate exceeds 2x baseline or P95 latency rises over 50%.

When should I roll back a production deployment?▼

Roll back immediately when error rate exceeds 2x baseline, P95 latency increases 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 launch?▼

Monitor application metrics (error rate, p50/p95/p99 latency, request volume), infrastructure metrics (CPU, memory, database connections, disk), and client metrics (Core Web Vitals, JavaScript errors). In the first hour, verify the health endpoint, error dashboards, and the critical user flow manually.

What are common mistakes when deploying to production?▼

Common mistakes include deploying without a rollback plan, skipping monitoring setup, big-bang releases without staging, feature flags with no owner or expiration, and assuming staging behavior guarantees production behavior. Production has different data, traffic patterns, and edge cases.