What problem does it solve? Starting implementation without understanding impact leads to missed files, broken dependencies, and untested changes. This Skill produces a written context map that delimits exactly which files a task creates or modifies, which dependencies break, which tests exist or are missing, and which risks apply, before any code is written. ## Core Features & Use Cases - Impact Delimitation: Lists every file to create or modify with the concrete change described, plus direct dependencies traced through imports and exports. - Test and Risk Coverage: Identifies existing tests covering affected code, flags missing tests as "to write", and signals public API, database migration, and configuration risks. - Reference Patterns: Points to an existing file that solves a similar problem so new code follows established structure. - Use Case: Before adding a status field to a payments API, ask for a context map to get a reviewable plan listing the controller change, the new enum, affected frontend pages, tests to extend, and migration risks. ## Quick Start Ask the assistant to map the impact of your planned change, for example: "Map which files, dependencies, tests, and risks are affected by adding a status field to the payments API before I start coding."
