Skill: Context Map

Generate file impact map before code changes to identify affected files, relationships, cascades — improves agent file partitions for parallel work.

When to Use

Steps

1 — Entry Points

Identify files that MUST change from task description.

2 — Trace Outward (dependents)

Find consumers of entry-point exports:

grep_search("import.*from.*places", isRegexp=true)   # find importers
vscode_listCodeUsages("PlaceCard")                     # find component consumers
grep_search("places.*route|/places", isRegexp=true)    # find route references

3 — Trace Inward (sources)

Find what entry points depend on:

grep_search("from.*libs/", includePattern="src/places/**")  # shared lib deps
grep_search("from.*config", includePattern="src/places/**")  # config deps

4 — Build the Map

Produce a compact map for Team Lead and downstream agents:

Context Map — Feature: Add priceRange

- Entry points:
	- src/lib/place/schema.ts
	- src/components/PriceRangeFilter/PriceRangeFilter.tsx

- Dependents (trace outward):
	- src/pages/places/page.tsx
	- src/components/PlacesList/PlaceCard.tsx

- Sources (trace inward):
	- src/lib/filters.ts
	- src/shared/types/place.ts

- Unaffected (optional):
	- src/components/Account/**

Validation checkpoint: every grep_search / vscode_listCodeUsages hit lands in the map; all listed files open without errors (CI: pnpm typecheck). Full template, depth levels, partition derivation, Team Lead integration: see REFERENCE.md.

Anti-Patterns

• Skipping for "obvious" tasks — shared libs cascade unexpectedly
• Guessing dependencies instead of using grep_search / list_code_usages
• Over-mapping a 2-file fix
• Using a stale map after plan changes