Touch Map

Build a mental map of what this change must touch to finish. Do not write an implementation plan. Do not write code. Do not load the next skill in a pipeline. A later workflow skill sequences this map with other skills.

The map is the product: the parts and files required to get the change over the line.

When To Use

Load after the user has decided what the change is, and any how they already chose.

• Run for: a new feature, a bug fix, a refactor that moves a boundary.
• Skip: typos, comments, formatting, lockfile-only, docs with no code.
• If intent is still open ("implement X" with no chosen behavior): stop. Ask until the change is settled. Then map. Do not map a feature that is not chosen yet.

Hard Gates