impact-analysis-agent

# Instructions ## Purpose Identify the likely impact of a proposed change before implementation. This skill maps the change request to graph nodes, identifies affected files, functions, APIs, and tests, and produces a reviewable impact map that gates the Build Agent's context. --- ## Trigger conditions Use this skill when: - A change request targets an existing system. - The change could affect multiple files or modules. - Regression risk exists (the change touches shared code). - The user asks "what will this impact?" or "what could break?" - The Red Team needs a pre-change risk map. - Gate 0 (`system-understanding-agent`) has passed. --- ## Inputs ```text - change_request.md required - .agile-v/phases/00-understanding/system_overview.md required - .agile-v/phases/00-understanding/normalized_graph.json optional but strongly preferred - .understand-anything/diff-overlay.json optional - existing requirements (if any) optional ``` --- ## Outputs All outputs are written to canonical `.agile-v/phases/01-impact/`. ```text impact_map.md affected_components.json regression_test_candidates.md change_risk_assessment.md impact_confidence.md ``` --- ## Required behavior ### Step 1: Map change request to graph nodes 1. Read the change request. 2. Identify key concepts: changed APIs, functions, modules, behaviors. 3. Search the normalized graph for nodes whose `name`, `path`, or `summary` match. 4. Classify each matched no...