← Back to Skills
Software EngineeringEngineeringGold

Deploy software updates safely and gradually.

Progressive Delivery Engineer

Feature flags, canary releases, A/B testing

advancedv5.0

Best for

  • Implementing canary deployment pipelines with automated rollback triggers based on error rate SLIs
  • Setting up feature flag architecture with percentage-based user rollouts and kill switches
  • Designing progressive rollout strategies from 1% internal users to full production release
  • Building observability-driven deployment decisions using Flagger or Argo Rollouts

What you'll get

  • Complete canary deployment configuration with Flagger/Argo Rollouts including traffic splitting rules, success metrics thresholds, and automated rollback triggers
  • Feature flag architecture design with LaunchDarkly/Unleash integration, flag lifecycle policies, and user targeting rules for progressive rollouts
  • Observability dashboard setup with deployment-specific SLIs, automated analysis criteria, and integration with promotion/rollback decisions
Expects

Details about the application architecture, current deployment pipeline maturity, risk tolerance, and specific metrics for measuring deployment health (error rates, latency, business KPIs).

Returns

Detailed progressive deployment strategy including traffic splitting configuration, automated promotion criteria, rollback triggers, feature flag taxonomy, and observability integration patterns.

What's inside

You are a Progressive Delivery Engineer. You design and implement controlled deployment strategies that minimize risk while maximizing deployment velocity using feature flags, canary releases, blue-green deployments, and observability-driven rollouts. - Decouple deployment from release using feature...

Covers

What You Do DifferentlyMethodologyWatch ForOutput Format Format
Not designed for ↓
  • ×Basic CI/CD pipeline setup without progressive deployment capabilities
  • ×Static blue-green deployments without gradual traffic shifting
  • ×Feature development or code implementation (focuses on release strategy)
  • ×Traditional monitoring setup without deployment-specific health checks

SupaScore

84.85
Research Quality (15%)
8.7
Prompt Engineering (25%)
8.4
Practical Utility (15%)
8.6
Completeness (10%)
8.3
User Satisfaction (20%)
8.2
Decision Usefulness (15%)
8.8

Evidence Policy

Standard: no explicit evidence policy.

progressive-deliveryfeature-flagscanary-releasesrolloutsa-b-testingdeploymentobservability

Research Foundation: 6 sources (1 industry frameworks, 2 web, 1 books, 2 official docs)

This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.

Version History

v5.03/25/2026

v5.5 distilled from v2 via Claude Sonnet

v1.0.02/15/2026

Initial version

Prerequisites

Use these skills first for best results.

Works well with

Need more depth?

Specialist skills that go deeper in areas this skill touches.

Common Workflows

Safe Production Release Pipeline

End-to-end safe deployment workflow from pipeline setup through progressive rollout to incident response readiness

© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice