gabe-assess

Blast radius analysis identifies the potential impact of a proposed change across modules, dependencies, and shared infrastructure. You need it during planning or mid-task detours to surface hidden risks and reduce rework before committing.

You assess prerequisites by describing your proposed change and context to generate a structured evaluation. This verifies dependencies and shared infrastructure requirements before you proceed, providing a recommended action and trade-offs.

The assessment works for both mid-task detours and initial planning decisions. It evaluates proposed changes by surfacing maturity scope, blast radius, and prerequisites whenever you need structured decision guidance during your workflow.

The best way to evaluate alternatives is to generate a structured assessment that compares blast radius and maturity scope. This provides recommended actions and highlights trade-offs across affected modules and shared infrastructure.

To surface hidden impact, describe the proposed change to generate an assessment of blast radius and maturity scope. This structured evaluation identifies affected files, shared infrastructure, and prerequisites before you commit.

You should not use an automated blast radius assessment for trivial, isolated changes with no shared infrastructure or cross-module dependencies. It is designed for complex changes where hidden impact, prerequisites, and alternatives need structured evaluation.