enforce-blast-radius

Audit software components for excessive scope, coupling, and complexity.

8|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/chrislema/claude-environments --skill enforce-blast-radius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enforce-blast-radius
Source: https://github.com/chrislema/claude-environments/tree/main/skills/enforce-blast-radius
Command: npx skills add https://github.com/chrislema/claude-environments --skill enforce-blast-radius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses architectural bloat and excessive coupling by identifying components that are too large, complex, or interconnected to be easily maintained or tested.

Core Features & Use Cases

  • Complexity Auditing: Evaluates code against strict line-count budgets for functions, modules, and services.
  • Coupling Analysis: Detects deployment, domain, and UI/logic coupling that prevents isolated testing and deployment.
  • Use Case: Use this during a design review to break down a monolithic service that has become a single point of failure, ensuring each new unit is testable and independently deployable.

Quick Start

Run the enforce-blast-radius skill to audit the current architecture and generate a plan for splitting over-scoped components.

Frequently Asked Questions about enforce-blast-radius

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

FAQPage Schema
How do I evaluate code for excessive coupling and architectural bloat?

Assess components against strict line-count budgets and analyze deployment, domain, and UI/logic coupling to detect architectural bloat. This ensures every unit remains independently testable and failure-isolated.

What is a blast radius analysis in software architecture?

Blast radius analysis evaluates software components for excessive scope and complexity to isolate failures. It applies a three-question test and complexity budget to ensure modules do not mix unrelated concerns.

How do I break down a monolithic service that has become a single point of failure?

Run an architectural review to split over-scoped components and enforce a small blast radius. This generates a refactoring plan ensuring each new unit is independently testable and deployable.

When do I need to enforce complexity budgets during refactoring?

Enforce complexity budgets during refactoring when modules or functions exceed defined size thresholds. This isolates failures by ensuring every unit adheres to strict line-count limits and passes a three-question test.

Does this architectural review approach work for evaluating task plans?

Yes, this approach evaluates task plans for excessive scope and complexity. By applying a complexity budget and three-question test, it ensures planned units remain independently testable and failure-isolated.