Identifies which repository files, modules, APIs, tests, examples, demos, documentation, configuration, and dependency areas are likely to be affected by a proposed change before implementation. Use when the user asks for an impact map, blast-radius analysis, affected areas, likely files to inspect or edit, test/doc update scope, or a planning handoff that predicts downstream repository impacts.
