shipping-and-launch

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

665|3|Updated Sep 12, 2026
One-click install
npx skills add https://github.com/rizqinrr/viserys-agent --skill shipping-and-launch-rizqinrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/rizqinrr/viserys-agent/tree/main/skills/shipping-and-launch
Command: npx skills add https://github.com/rizqinrr/viserys-agent --skill shipping-and-launch-rizqinrr

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 covering readiness checks, 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. - Staged Rollout with Thresholds: Defines a deploy-to-staging, feature-flag, canary (5% to 100%) sequence with explicit advance/hold/rollback metric thresholds. - Rollback and Error Budget Gates: Requires a documented rollback plan and uses error budget policy to decide whether it is safe to ship. - Use Case: Before releasing a new task-sharing feature, run the checklist, deploy behind a feature flag, canary to 5% of users while watching error rate and P95 latency, then roll out gradually with a tested rollback path. ## 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 launch checklist?

A production launch checklist covers 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.

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.

What metrics should I monitor after a production deploy?

Monitor error rate, p50/p95/p99 latency, request volume, Core Web Vitals, client JavaScript errors, and infrastructure metrics like CPU, memory, and database connections. Check these within the first hour after launch.

What is an error budget release gate?

An error budget gate uses your SLO's allowed failure budget to decide release pace. Above 20% remaining you ship normally, between 0-20% you slow rollouts, and when exhausted you freeze feature work to focus on reliability.