Skip to content
Development
Skill

/nw-deployment-strategies

Rollback procedures, risk assessment, pre/post-deployment validation, and contingency planning. Load when orchestrating deployment or preparing rollback plans. For deployment strategy details (canary, blue-green, rolling), see `cicd-and-deployment` skill.

From plugin
nwave
591200 skills34 agents27 commands
Install
$ npx -y skills add nWave-ai/nWave --skill nw-deployment-strategies --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/nw-deployment-strategies

Context preview

The summary Claude sees to decide when to auto-load this skill.

Rollback procedures, risk assessment, pre/post-deployment validation, and contingency planning. Load when orchestrating deployment or preparing rollback plans. For deployment strategy details (canary, blue-green, rolling), see `cicd-and-deployment` skill.

SKILL.md

nw-deployment-strategies.SKILL.md
name: nw-deployment-strategies
description: Rollback procedures, risk assessment, pre/post-deployment validation, and contingency planning. Load when orchestrating deployment or preparing rollback plans. For deployment strategy details (canary, blue-green, rolling), see `cicd-and-deployment` skill.
user-invocable: false
disable-model-invocation: true

Deployment Strategies — Rollback, Risk, and Validation

For deployment strategy patterns (canary, blue-green, rolling, progressive delivery), see `cicd-and-deployment` skill. This skill focuses on operational concerns: validation, rollback, risk, and post-deployment.

Pre-Deployment Validation

Before any deployment, validate:

  • Deployment scripts tested in staging | Database migrations tested with rollback scripts
  • Configuration management consistent across environments | Health checks and service discovery configured
  • Monitoring and alerting systems prepared | Backup and disaster recovery procedures validated

Rollback Procedures

Design Rollback First

Every deployment plan starts with the rollback section: 1. **Database rollback**: migration revert scripts tested and verified 2. **Application rollback**: previous version tagged and deployable 3. **Configuration rollback**: previous config snapshots available 4. **Traffic rollback**: load balancer / feature flag kill switch ready 5. **Data rollback**: data consistency plan for partial rollback scenarios

Automated Rollback Triggers

Configure automatic rollback when:

  • Error rate exceeds baseline by >2x | P95 latency exceeds SLA threshold
  • Health check failures exceed threshold (e.g., 3 consecutive) | Business metric anomaly detected (e.g., conversion drop >10%)

Manual Rollback Decision Criteria

Stakeholder-reported functional issues | Security vulnerability discovered post-deploy | Data integrity concerns | Performance degradation below acceptable levels.

Risk Assessment

Technical Risks

Integration failure with downstream services | Performance degradation under production load | Data migration integrity issues | Security vulnerabilities introduced.

Business Risks

User adoption challenges | Business process disruption | Stakeholder expectation misalignment.

Operational Risks

Infrastructure capacity limitations | Third-party dependency failures | Team availability for incident response.

Risk Mitigation Checklist

  • [ ] Rollback procedure designed and tested
  • [ ] Monitoring dashboards configured for deployment
  • [ ] On-call team notified of deployment window
  • [ ] Feature flags configured for gradual rollout
  • [ ] Communication plan for stakeholders prepared
  • [ ] Incident response runbook updated

Post-Deployment Validation

Production Smoke Tests

Critical user paths validated | Integration points tested with real external systems | Performance validated under production load | Security controls verified | Data integrity confirmed.

Monitoring Validation

Application performance metrics collecting | Error tracking and alerting active | Business metric dashboards updated | Infrastructure monitoring nominal.

Read more
Ships withnwave

AI agents that guide you from idea to working code, with human judgment at every gate. nWave runs inside Claude Code. It breaks feature delivery into seven waves (discover, diverge, discuss, design, devops, distill, deliver).

Get the whole plugin