context-map
Installation
SKILL.md
Context map
Use this skill when the next step is figuring out what to read or touch before changing code.
Use this skill when
- A task may touch multiple files, packages, or layers and the likely blast radius is not obvious yet.
- You need to identify candidate files, nearby tests, and reference patterns before editing.
- A user or reviewer asks for a context map before implementation.
- You want to scope a feature, refactor, or bugfix enough to hand off to planning or implementation cleanly.
Do not use this skill when
- The exact files are already named and the scope is narrow enough to execute directly.
- The user wants a phased implementation plan with tasks, dependencies, rollout notes, or handoff artifacts; route to
implementation-revieworworkflow-contracts. - The main problem is sharpening the user's ask rather than mapping the codebase; route to
reverse-promptfirst.