← ClaudeAtlas

planguard-blast-radiuslisted

Walks the user through the dependency and blast-radius questions for a proposed infrastructure change (what depends on it, what the rollback is, whether state is backed up, whether there is a maintenance window, who is paged) and writes a change record with a go or no-go that never says go while a high or critical finding is open. Use when the user says "what is the blast radius of this change", "write the change record", "can we apply this in production", "who depends on this resource", "is it safe to run this terraform", or "go or no-go for this deploy".
vivekbhange-hub/plan-guard-skill · ★ 0 · DevOps & Infrastructure · score 75
Install: claude install-skill vivekbhange-hub/plan-guard-skill
# planguard-blast-radius: know what breaks before you press apply A scanner tells you what is wrong with the change. It does not know that a payments service reads that queue, that the last state backup is three weeks old, or that nobody is on call on Friday night. This skill asks those questions, uses the `blast-radius-mapper` agent to find dependents in the repo, and writes a change record with a decision. ## Inputs - The proposed change: a plan report from `planguard-terraform`, a manifest audit from `planguard-k8s`, a drift report from `planguard-compare`, or a plain description. - The environment (dev, staging, production) and the planned time. - Answers to the questions in step 3. Do not invent them; "unknown" is a valid answer and it counts against the go decision. - No script runs in this skill; on Windows use `python` (or `py -3`) for any helper command the other planguard skills print. ## Outputs - A change record in this shape: ``` Change: <one line> Environment: <env> Date/window: <when> Owner: <name> On call: <name or unknown> Findings open: <n critical, n high, n medium> Blast radius: <what depends on it, who notices, how fast> Rollback: <exact steps, time to run, point of no return> State and data backup: <where, how old, restore tested yes/no> Decision: GO / NO-GO / GO WITH CONDITIONS Conditions: <list> Approver: <name> Date: <date> ``` - A list of open questions, each with