shipping-and-launch

Prepare production deployments with monitoring, staged rollouts, and rollback plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, production-ready launch process that reduces risk by ensuring deployments are observable, reversible, and incremental so teams can release changes confidently and recover quickly from regressions.

Core Features & Use Cases

  • Pre-launch checklist for code quality, security, performance, accessibility, infrastructure, and documentation to prevent common release failures.
  • Feature flag and staged rollout strategy with canary and percentage-based rollouts plus decision thresholds for advancing, holding, or rolling back.
  • Monitoring, observability, and post-launch verification guidance including health checks, error reporting, P95/P99 latency tracking, and first-hour verification steps.
  • Use case: Preparing a major feature release with database migrations, requiring a feature-flagged rollout, canary monitoring, and a documented rollback plan.

Quick Start

Prepare a pre-launch checklist, monitoring plan, staged rollout sequence, and rollback plan for release v1.0 so the team can perform a safe canary deployment and rollback if thresholds are exceeded.

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 safe production deployment with a rollback plan?

A staged rollout reduces deployment risk by incrementally releasing changes using canary or percentage-based rollouts. It includes decision thresholds for advancing, holding, or rolling back, ensuring deployments remain observable and reversible before reaching full production traffic.

What should be included in a pre-launch checklist for a feature release?

A pre-launch checklist for a feature release should cover code quality, security, performance, accessibility, infrastructure, and documentation. This structured process prevents common release failures and ensures the deployment is fully observable before launch.

How do I monitor a canary deployment and verify health checks?

Yes, feature flags are essential for safe migrations and betas. They enable percentage-based rollouts and canary deployments, allowing you to define decision thresholds for advancing, holding, or rolling back if health checks and error monitoring detect regressions.

When should I execute a rollback procedure during a staged rollout?

Execute a rollback procedure during a staged rollout when error monitoring exceeds defined thresholds or health checks fail. Having a verifiable rollback plan ensures you can quickly recover from regressions before they impact the entire user base.