shipping-and-launch

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

2|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill shipping-and-launch-ankaboot-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/shipping-and-launch
Command: npx skills add https://github.com/ankaboot-source/boucle --skill shipping-and-launch-ankaboot-source

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 complete launch framework 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 before any deploy. - Feature Flags & Staged Rollout: Decouples deployment from release with a flag lifecycle and a canary sequence (5% → 25% → 50% → 100%) with explicit advance/hold/rollback thresholds. - Monitoring & Rollback Strategy: Defines what metrics to watch, post-launch verification steps, and a documented rollback plan with trigger conditions and time-to-recover targets. - Use Case: You are about to ship a new task-sharing feature. Use this Skill to verify the checklist, deploy behind a feature flag, canary to 5% of users while watching error rates and P95 latency, then roll out gradually with a rollback plan ready. ## Quick Start Use the shipping-and-launch skill to prepare a pre-launch checklist and staged rollout plan for my upcoming production deployment.

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?

Use a pre-launch checklist covering code quality, security, performance, accessibility, infrastructure, and documentation. Verify tests pass, dependencies have no critical vulnerabilities, environment variables are set, and monitoring is configured before deploying.

How to do a staged rollout with feature flags?

Deploy with the flag off, enable for internal users, then canary to 5% of users while monitoring error rates and latency. 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.

What metrics should I monitor after a production launch?

Monitor error rate, p50/p95/p99 latency, request volume, Core Web Vitals, JavaScript errors, and infrastructure metrics like CPU, memory, and database connections. In the first hour, verify the health endpoint, check for new error types, and test the critical user flow manually.

Do small changes still need feature flags and rollback plans?

Yes. Every deployment carries risk, and even simple changes can break production. A feature flag acts as a kill switch, and a documented rollback plan with trigger conditions ensures fast recovery regardless of change size.