Tool Hierarchy Compact

Generic pocket summary of service and task rankings. Canonical routing lives in Capability Routing Map and Skill Resolver; Cursor's tool-hierarchy.mdc is one compact projection.

Pick the highest-ranked tool per task; drop only when it cannot do the job. Start from the generic map, then use harness-specific projection files only for local loader syntax or context-budget constraints. Source: Capability Routing Map, 2026-06-29

Key rankings (examples)

• Research: Security and Review Skills → Security and Review Skills → web search
• Browser: route by test type (Complementary Browser Testing)
• Repo topology: use graphify-sidecar for codebase graph, path/explain, affected-node, and PR-risk questions; keep qmd for wiki knowledge.
• CSS/UI: CSS UI Enforcement
• Dedalus workspace: prefer matching Dedalus-origin category skill first

If the generic wiki pages and a compact projection disagree, the wiki wins. Update Capability Routing Map and Skill Resolver first, then mirror the compact shape into Cursor or any future harness projection.

---

Timeline

• 2026-07-02 | Added the Graphify sidecar boundary to the compact hierarchy: qmd owns compiled wiki retrieval; graphify-sidecar owns repo topology/path/explain/affected questions. Source: User request, 2026-07-02
• 2026-06-29 | Reframed the compact hierarchy as a generic agent-doc backed by Capability Routing Map and Skill Resolver; Cursor tool-hierarchy.mdc is only one projection. Source: User correction, 2026-06-29
• 2026-05-31 | Agent doc pointing to tool-hierarchy.mdc compact layer. Source: tool-hierarchy.mdc, 2026-05-31
• 2026-06-28 | Updated Dedalus skill routing to category taxonomy with origin metadata. Source: User request, 2026-06-28