silver-blast-radius

Identify blast radius of proposed infrastructure changes before planning.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill silver-blast-radius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: silver-blast-radius
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/silver-blast-radius
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill silver-blast-radius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determine and communicate the blast radius of proposed infrastructure or DevOps changes to prevent uncontrolled risk and enable safe planning.

Core Features & Use Cases

  • Scope mapping: enumerate all resources affected across environments and identify associated IaC artifacts, CI/CD definitions, and secret changes.
  • Dependency and coupling analysis: document downstream dependents and classify coupling as hard, soft, or none.
  • Risk management artifacts: produce a rollback plan, change-window assessment, and gating outputs to satisfy /devops-quality-gates.
  • Use Case: Before executing a Kubernetes cluster upgrade, run this assessment to validate impact, rollback viability, and window timing.

Quick Start

Run a blast-radius assessment for the proposed infrastructure change to generate scope, dependencies, failure scenarios, rollback steps, and window risk.

Frequently Asked Questions about silver-blast-radius

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a blast radius assessment for infrastructure changes?

A blast radius assessment identifies the scope of proposed infrastructure changes by mapping affected resources, dependencies, and failure modes across environments to prevent uncontrolled risk. It enables safe change planning through structured risk evaluation.

How do I assess the blast radius of a Kubernetes cluster upgrade?

To assess the blast radius of a Kubernetes cluster upgrade, map the scope of affected resources, classify downstream dependency coupling as hard or soft, and document failure scenarios, rollback steps, and change-window timing risks.

How do I map infrastructure dependencies before executing a DevOps change?

Map infrastructure dependencies by enumerating all affected resources across environments and identifying associated IaC artifacts, CI/CD definitions, and secret changes. Classify downstream dependents by coupling type to communicate risk before execution.

Does this blast radius assessment produce outputs for devops-quality-gates?

Yes, the blast radius assessment produces gating outputs, rollback plans, and change-window assessments specifically designed to satisfy the structured requirements for devops-quality-gates before proceeding with infrastructure changes.

What is the best way to plan a rollback for infrastructure changes?

The best way to plan a rollback is to perform a blast radius assessment that documents failure scenarios and validates rollback viability before execution. This produces a structured rollback plan detailing steps and change-window timing risks.

Can I use this for risk assessment across multiple environments?

Yes, this risk assessment applies to DevOps and IaC changes across multiple environments. It details the scope of affected resources, classifies dependency coupling, and evaluates failure modes and window risks for each environment.