What problem does it solve? Teams struggle with slow, risky releases caused by long-lived branches, manual deployments, and untested pipelines. This Skill applies Jez Humble and David Farley's Continuous Delivery discipline so every commit stays deployable and releasing becomes a routine business decision. ## Core Features & Use Cases - Deployment Pipeline Design: Structures commit, acceptance, non-functional, and deployment stages with fast-feedback targets and one-artifact promotion rules. - Branching & Release Strategies: Guides trunk-based development, feature flags, branch-by-abstraction, and blue/green, canary, rolling, and dark-launch deployments. - Delivery Health Measurement: Applies the four DORA metrics (deployment frequency, lead time, change failure rate, MTTR) to benchmark and improve team performance. - Use Case: When debating whether to keep a two-week feature branch or merge daily, use this Skill to evaluate trunk-based development with feature flags and design the pipeline stages that make daily merges safe. ## Quick Start Ask Claude to design a deployment pipeline for your service or to evaluate your branching strategy against trunk-based development and the DORA metrics.
