agentleFS
BagelHoleBagelHole/BagelSkills/skills/blast-radius/SKILL.md

blast-radius

Skill2 starsChanged 4 months agoMITView on GitHub

Use this skill when preparing to change a shared interface, schema, dependency, infrastructure component, permission model, or other high-coupling behavior. Trace direct and second-order consumers, rank credible failure paths, and produce a test, rollout, observability, and rollback plan grounded in repository and system evidence.

116 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ketchup-video, principle-never-block-on-the-human and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 14 projects that use this

  • jaydubya818Skill

    principle-never-block-on-the-human

    Apply when safe reversible implementation details can proceed inside scope.

    Also in 44 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 29 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 20 projects that use this

  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 25 projects that use this

  • jaydubya818Skill

    principle-make-operations-idempotent

    Apply when an operation must tolerate retries after partial completion.

    Also in 46 projects that use this

  • +6 more from jaydubya818

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 111 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a required input is retrievable from available tools or artifacts, retrieve it rather than asking the user.

    line 40
  2. Distinctive:

    Search typed references, imports, API clients, queries, event subscribers, CI/deploy config, dashboards, runbooks, and ownership.

    line 52
  3. Distinctive:

    Follow data and control flow into caches, retries, queues, permissions, analytics, billing, mobile versions, scheduled jobs, operational …

    line 58
  4. Distinctive:

    Complete when: every high-risk dependency has a test, signal, and rollout disposition

    line 78
  5. Distinctive:

    Search for behavior and data contracts, not only symbol references.

    line 82
  6. Distinctive:

    Import graph mistaken for full impact analysis.

    line 103

“Common” is measured: kept by at least 6 in 10 of the 111 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blast Radius

Outcome

Know what a consequential change can break, how failures will propagate, and how to contain them before implementation begins.

This skill changes the agent's process: it requires evidence, explicit claim strength, and a checkable completion boundary. Load references/playbook.md only when deeper prompts or rubrics are needed. Use assets/output-template.md when producing the final artifact.

When to use

  • The proposed change touches APIs, events, schemas, shared libraries, authentication, billing, infrastructure, or deployment behavior.
  • The user asks what could break, who depends on something, or how to roll out safely.
  • A migration or refactor crosses service, client, team, or data boundaries.

Do not use when

  • The edit is isolated, local, and covered by a clear contract.
  • The change is already failing and immediate debugging or incident response is required.

Required inputs

  • Proposed change and intended invariant
  • Repositories, schemas, dependency graphs, infrastructure, and deployment definitions
  • Known consumers, owners, environments, and compatibility window

If a required input is retrievable from available tools or artifacts, retrieve it rather than asking the user. Ask only when a missing answer represents authority, preference, or risk that tools cannot resolve.

Workflow

1. State the change contract

Describe current behavior, proposed behavior, preserved invariants, rollout unit, and reversibility. Split bundled changes that have different blast radii.

Complete when: the behavior delta and invariants are unambiguous

2. Discover first-order dependents

Search typed references, imports, API clients, queries, event subscribers, CI/deploy config, dashboards, runbooks, and ownership. Record evidence for each consumer.

Complete when: each first-order consumer has evidence and ownership status

3. Trace second-order effects

Follow data and control flow into caches, retries, queues, permissions, analytics, billing, mobile versions, scheduled jobs, operational tooling, and human procedures.

Complete when: non-code and delayed consumers have been considered

4. Model failure propagation

For each credible failure, state trigger, affected surface, detection signal, propagation boundary, user/data impact, and recovery path. Rank likelihood, impact, and detectability separately.

Complete when: high-risk scenarios include detection and recovery

5. Design containment

Choose compatibility, feature flag, shadow/dual-write, canary, backfill, versioning, staged migration, or kill-switch controls appropriate to the risk. Avoid controls that cannot actually reverse the change.

Complete when: containment controls match actual reversibility

6. Produce the change envelope

Deliver the dependency map, contract tests, migration order, observability, ownership, rollout gates, rollback criteria, and residual unknowns. Verify every high-risk consumer has a disposition.

Complete when: every high-risk dependency has a test, signal, and rollout disposition

Operating rules

  • Search for behavior and data contracts, not only symbol references.
  • Absence from code search does not prove absence of external consumers.
  • Rollback after an irreversible data write may require forward recovery; say so.
  • Mobile and third-party clients may remain old beyond the deployment window.
  • Unknown consumers increase risk; they do not justify invented certainty.

Output contract

The final result must contain:

  • Current/proposed contract and invariants
  • First- and second-order dependency map with evidence
  • Ranked failure propagation scenarios
  • Required contract, integration, and regression tests
  • Staged rollout, signals, gates, and rollback/forward-recovery plan
  • Owners, unknowns, and residual risk

Distinguish observed, inferred, assumed, and unverified claims. Link to files, commits, screenshots, commands, logs, or supplied sources when those artifacts support a consequential conclusion. Keep the executive result concise; move detail behind appendices when necessary.

Common pitfalls

  • Import graph mistaken for full impact analysis.
  • Rollback theater that ignores schema or data irreversibility.
  • A giant undifferentiated list with no risk ranking.
  • Forgetting operational and human consumers.

Verification checklist

  • The requested outcome—not merely the procedure—has been satisfied.
  • Every consequential claim is supported, qualified, or explicitly unverified.
  • The workflow's completion criteria are met in order.
  • Safety boundaries and forbidden side effects were respected.
  • The output follows assets/output-template.md or contains equivalent information.
  • Remaining unknowns have an owner, next action, or stated consequence.

Resources

  • references/playbook.md — deeper domain prompts and evaluation guidance.
  • assets/output-template.md — reusable final-output structure.
  • evals/evals.json — output-quality cases.
  • evals/trigger-evals.json — positive and negative description-trigger cases.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.