Menu
Visual index for Datarim maps. Load this entry first, then only the diagram fragment needed for routing, stage flow, or dependency orientation.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | visual-maps |
| description | Visual index for Datarim maps. Load this entry first, then only the diagram fragment needed for routing, stage flow, or dependency orientation. |
| model | inherit |
| current_aal | 1 |
| target_aal | 2 |
When to load: When an agent needs visual orientation in the Datarim pipeline or framework structure. Do not load the full map set for simple tasks with an obvious next step.
Load only the fragment relevant to the question:
pipeline-routing.md
Use for complexity-based routing across init → archive and the artefact flow (init-task, expectations, playwright-run nodes since v2.8.0).stage-process-flows.md
Use for stage-specific flows from /dr-init through /dr-archive, including Layer 3b expectations verification and Layer 4f playwright-run in /dr-qa.content-and-management-flows.md
Use for /dr-write, /dr-edit, /factcheck, /humanize, /dr-addskill, /dr-optimize, and /dr-dream.utility-and-dependencies.md
Use for utility command flows, command-agent relationships, and agent-skill dependencies (includes init-task-persistence, expectations-checklist, playwright-qa, human-summary nodes since v2.8.0).panels-and-quality.md
Use for Consilium panel layouts and stage-to-quality rule mapping.pipeline-routing.md.stage-process-flows.md.content-and-management-flows.md.utility-and-dependencies.md.panels-and-quality.md.This skill is used for orientation, not for every task. Keeping a short index entry avoids loading unrelated diagrams into context while preserving the full map library in directly addressable fragments.
Schema and migration semantics for /dr-doctor — thin one-liner contract, 6-pass migration, data-loss safety, conflict resolution. Loaded by self-heal.
Core Datarim rules. Load this entry first, then only the fragment needed for paths, storage, numbering, backlog, routing, or archive behavior.
Post-QA hardening — detects task type (code, docs, research, legal, content, infra) and applies the matching verification checklist before archiving.
Testing pyramid, frameworks, mocking. Load first; then the fragment for the active gate (live smoke, silent failure, bats, legacy triage).
Preserve Datarim task continuity while orchestrated Claude Code or Codex sessions compact or clear context at deterministic pressure thresholds.
Immutability contract for all pipeline stages: artefact freeze, V-AC parity, non-code parity, anti-tautological rule, and return-to-source transition.