context-maplisted

# Context Map Build a task-focused map of the codebase before changing files. - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## When to Use Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below. - A request spans more than one file and the impact is not obvious yet. - You need to identify the minimum safe edit set before implementation. - You are debugging a bug or regression and need to trace nearby code paths. - You want a review-quality summary of likely code, test, config, and documentation touch points. ## Core Workflow 1. Restate the change in one sentence. 2. Search for obvious entry points by feature name, route, symbol, command, or error text. 3. Expand outward into direct dependencies, tests, docs, config, schemas, and scripts. 4. Separate likely edit targets from read-only reference patterns. 5. Call out risk multipliers such as public APIs, migrations, auth, secrets, environment variables, or generated artifacts. 6. Produce a compact context map before implementation. ## Search Order ### 1. Primary Targets Look for the files most likely to hold the requested behavior: - route handlers, commands, services, jobs, or pages - components, helpers, validators, and serializers - feature-specific configs, manifests, templates, and generated sources ### 2. Direct Dependencies Trace the files that import, export, call, or configure the primary targets: - imports and expor