assess-impactlisted

# Assess Impact Understand the potential blast radius of changes before making them by analyzing dependencies, coupling patterns, and ownership. ## Prerequisites Omen CLI must be installed and available in PATH. ## Workflow ### Step 1: Check Symbol Blast Radius Use the `impact` command to get transitive callers and callees in one call: ```bash omen -f json impact <symbol-name> --depth 2 ``` This returns affected files, caller/callee BFS levels, and the total count — much faster than building the picture manually. To inspect a specific symbol first: ```bash omen -f json symbol <symbol-name> ``` ### Step 2: Map File-Level Dependencies Run the dependency graph analysis for file-level coupling: ```bash omen -f json graph --compact ``` Identify: - Direct dependents (files that import the target) - Transitive dependents (files that import the dependents) ### Step 3: Check Temporal Coupling Run the temporal coupling analysis: ```bash omen -f json temporal ``` Files with high temporal coupling to the target often need to change together even without explicit imports. ### Step 3: Identify Stakeholders Run the ownership analysis: ```bash omen -f json ownership ``` Identify: - Primary owner of the target file - Owners of dependent files - Subject matter experts to consult ## Impact Categories Classify impact by type: | Category | Description | Action | |----------|-------------|--------| | Direct | Explicit imports/calls | Will break if signature changes | | Imp