The visual-maps Skill — Navigate the Datarim Pipeline Without Loading Everything
How the visual-maps skill provides a fragment-based index of workflow diagrams so an agent loads only the diagram relevant to its current question, not the full map library.
Datarim has diagrams for its pipeline stages, its agent relationships, its content flows, and its quality rules. Loaded all at once, those diagrams consume context an agent could spend on the actual task. The visual-maps skill solves this with a routing index: a short entry that names the five diagram fragments and tells an agent which one answers which question.
The skill is used for orientation, not for every task. When the next step is obvious, there is no reason to load it. When an agent needs to understand where it sits in the pipeline, or how two commands relate to each other, the index provides a precise pointer.
The five fragments
The first fragment is pipeline-routing.md. It covers complexity-based routing across the full init → archive flow and the artefact flow that includes the init-task, expectations, and playwright-run nodes added in v2.8.0. Use it when the question is which pipeline a task should follow.
The second is stage-process-flows.md, which covers stage-specific flows from /dr-init through /dr-archive, including the Layer 3b expectations verification and the Layer 4f playwright-run in /dr-qa. Use it when the question is what happens inside one specific stage.
The third is content-and-management-flows.md, which covers /dr-write, /dr-edit, /factcheck, /humanize, /dr-addskill, /dr-optimize, and /dr-dream. Use it for content creation, knowledge-management, and optimisation flows.
Relationship and quality fragments
The fourth fragment is utility-and-dependencies.md. It holds the relationship graphs between commands and agents, and the agent-to-skill dependency map. Since v2.8.0 this includes the init-task-persistence, expectations-checklist, playwright-qa, and human-summary nodes. Use it when the question is how a command and an agent are wired together, or which skills an agent depends on.
The fifth is panels-and-quality.md, which covers Consilium panel layouts and the stage-to-quality rule mapping. Use it to understand how Consilium is structured or which quality rule applies at which pipeline stage.
Why a routing index instead of one diagram
The design decision behind this skill is explicit in the skill file: loading unrelated diagrams into context is waste. A task asking "what happens in /dr-qa?" needs one fragment, not five. The index entry itself is short enough to read without cost, and the selection guide maps each question type to a single fragment name. The full map library stays addressable without being loaded speculatively.
Read what Datarim is for broader context, or see the writing-plans skill for how plans are structured once the pipeline route is chosen.