- Home
- Skills
- Shaul1991
- Shaul Agents Plugin
- Deployment Strategy
deployment-strategy_skill
- Makefile
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill shaul1991/shaul-agents-plugin --skill deployment-strategy- SKILL.md12.2 KB
Overview
This skill defines and executes safe deployment strategies including Feature Flags, Canary, and Blue-Green releases plus rollback controls. It focuses on minimizing risk during releases by enabling gradual rollouts, instant switches, and automated rollback triggers. The agent produces deployment plans, checklists, and scripts to operate predictable, observable deployments.
How this skill works
The agent configures feature flags (third-party or in-house) to gate functionality per user, group, or percentage. It orchestrates canary and blue-green deployments via Kubernetes manifests and rollout scripts, adjusting replica counts and service selectors to shift traffic. It monitors key metrics and applies automatic rollback rules (error rate, latency, CPU) and executes rollback scripts or disables flags when thresholds are breached.
When to use it
- Rolling out major changes where user impact must be minimized
- Releasing experimental features to limited audiences via flags
- Switching production traffic instantly between versions
- Needing automated rollback if error or latency thresholds are exceeded
- Coordinating multi-step staged rollouts with observability gates
Best practices
- Use feature flags to decouple deploy and release; include a kill switch for emergencies
- Start canary at a small percentage and progress through defined stages with timeboxes and metric checks
- Maintain Blue and Green environments of equal capacity and verify health before switching
- Automate monitoring and rollback conditions for error rate, p99 latency, and resource saturation
- Keep a published deployment checklist and ensure on-call and alerting channels are ready
Example use cases
- Release a new checkout flow to 10% of users via feature flag and increase after validation
- Deploy v2 as a canary with 1 replica while keeping stable replicas for 90% traffic
- Prepare a blue-green switch for zero-downtime cutover with a service selector patch
- Trigger an automatic rollback when error rate exceeds 5% for 5 minutes
- Disable a problematic feature instantly by toggling the feature flag kill switch
FAQ
Feature flags let you enable behavior for specific users or percentages while the canary deployment serves actual new-version traffic. Use flags for code-level gating and canaries for infrastructure-level validation.
When should I use blue-green instead of canary?
Use blue-green for immediate, reversible cutovers when you can provision parallel environments; prefer canary for gradual risk reduction when rolling changes across many instances.