IDDT — Automap Reveal 🗺️
Doom: IDDT (typed twice on the map) = the whole level appears, every monster and item included. Here: you reveal the project's full map so you don't grope blindly in an unknown codebase.
The goal is a navigable mental map: where the code starts, where the main modules are, how data flows, what the stack is — just enough to reach in confidently, no more.
The recon
Work targeted; on a large repo don't read everything, sample.
- Terrain: the root and main-folder structure (Glob), the manifest/config files (package.json, pyproject, Cargo.toml, etc.) → that gives the stack.
- Entry points: main / index / app / server / entry — where execution starts. Grep for the typical entries.
- Main modules: the largest / most-imported libs, the domain folders. On a large codebase launch an Explore subagent ("medium" or "very thorough") to map in parallel and return just the conclusion.
- Data flow: how they connect — API → service → data layer, or the UI → state → backend chain. Only the main arteries, not every capillary.
Readout — MAP REVEALED
═══ MAP REVEALED ═══
🧱 Stack: <languages/frameworks>
🚪 Entry: <main entry point(s) with filename>
🗂️ Modules: <3-6 key areas + a word each on what they do>
🔀 Dataflow: <the main chain in one sentence>
📍 Start at: <if there was a mission: the relevant entry point>
════════════════════
After the readout, if there was a concrete task behind /iddt, move on to that
point. If it was just recon, stop here — the map is the goal.
Teeth: real recon + cache
Two things make this more than a plain prompt:
- Actually launch an
Exploresubagent on a large/unknown codebase (don't "map" from memory). The subagent sweeps in parallel and returns only the conclusion — that's token-efficient, real recon. - Cache the map to a file so the next
/iddtdoesn't re-run: write the readout to.claude/iddt-map.mdat the project root. If the file exists and is fresh, read it FIRST — if the code hasn't materially changed (check git log / mtimes), the cache plus a quick "changed since?" delta pass is enough.
Restraint
The "whole map" here is the main structure, not every file. Good recon is like the Doom automap: walls and doors show, not every texture pixel.