context-map

Run a context map analysis that searches for files related to your task, traces import/export dependencies, and locates affected tests. The output is a structured Markdown table listing files to modify, dependencies, and risks before implementation begins.

It should include files to modify with their purposes, direct dependencies that may need updates, test files covering affected functionality, similar code patterns to follow, and a risk checklist for breaking changes, migrations, and configuration updates.

The context map workflow searches the codebase for import and export statements referencing the target module. These direct dependencies are listed in a dedicated table so you know which files may need updates when the module changes.

For trivial single-file changes with no external consumers, a full context map adds overhead without benefit. It is most valuable for changes touching shared modules, public APIs, or functionality covered by multiple tests.

No, it only produces an analysis document and explicitly instructs not to proceed with implementation until the map is reviewed. Code changes happen separately after the context map is approved.