rollback-plan
Create rollback and fallback plans for deployments, releases, migrations, feature flags, and production changes. Use when Codex is asked to define rollback triggers, recovery steps, data restore needs, communication, or post-rollback validation.
Works with
--- name: rollback-plan description: Create rollback and fallback plans for deployments, releases, migrations, feature flags, and production changes. Use when Codex is asked to define rollback triggers, recovery steps, data restore needs, communication, or post-rollback validation. license: MIT --- # Rollback Plan ## Core Workflow 1. Identify change type, affected users, state changes, data migrations, and dependencies. 2. Define rollback triggers, decision owner, time window, and monitoring signals. 3. Document rollback steps, fallback alternatives, feature-flag switches, restore procedures, and verification checks. 4. Separate reversible code/config changes from irreversible data changes. 5. Include customer/support communication and incident handoff when relevant. 6. Add post-rollback validation and follow-up actions. ## Safety Rules - Do not claim rollback is possible when data or external side effects are irreversible. - Do not run rollback commands or restore data without explicit approval. - Escalate rollbacks involving migrations, payments, auth, customer data, or regulatory impact. ## Deliverable Shape For rollback plans, provide: - Change scope - Rollback triggers and owner - Reversible and irreversible parts - Rollback steps - Fallback path - Validation checks - Communication plan - Follow-up actions ## References - Read `references/rollback-plan-checklist.md` when preparing rollback or fallback plans.
More Deployment & CI/CD skills
azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
azure-kubernetes-app-deploy
microsoft/azure-skills
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).
