routelisted

# Route The mandatory routing layer for Doctrine. The routing gate concept is documented in [[mem.concept.doctrine.routing-gate]]. Follow it rigorously *unless* the user has instructed otherwise. If the user explicitly invoked a skill, use that now; if the routing layer indicates a subsequent action in a chain, go on with it afterwards. Do not respond, explore, inspect files, run commands, or start implementation until you have chosen the skill that governs the task. If there is a reasonable chance another Doctrine skill governs it, route through that skill first. Do not rationalize around this. If you skip routing because the task feels familiar, simple, urgent, or "probably fine", you are doing it wrong: - "I'll just inspect files first." → No. Routing decides *how* you inspect. - "I already know the command shape." → No. Use the CLI, don't guess. - "Small enough to skip routing." → Small tasks still need the right skill. - "I'll gather context first and decide later." → Decide first. When unsure, route to the stricter skill, not the looser one. ## The table rides the boot snapshot The routing table, mid-flight rules (consult / record-memory / backlog / notes / next / conduct postures), and core guardrails are already inlined in this session's prefix (`@.doctrine/state/boot.md`). Apply them from there — this skill does not restate them. What follows is route-unique. ## Route-unique rules The core loop (slice→design→plan→execute→audit→close) is documented in [[mem