Vibe Coding — Impact Analysis

Map blast radius before changing shared code.

Entry Router

Change type is DELETION?
→ Force HIGH risk immediately. List all N consumers. Require user confirmation.

Otherwise run Steps 1-5:
  Step 1: Identify target (file, function, change type)
  Step 2: Find direct consumers (grep imports)
  Step 3: Build transitive impact map
  Step 4: Score risk → READ: ## Risk Scoring
  Step 5: Output safe change path

Run steps sequentially. Jump to ## Risk Scoring only after completing Steps 1-3. Jump to ## HIGH Impact Response only if risk score is HIGH — skip it otherwise.