chief-of-staff

Agent routing for multi-layer requests works by scoping context to decide whether work belongs to legacy or new platforms, then recommending specific AGENTS.md rules and OpenSpec commands to load before execution begins.

Create a preflight checklist for multi-layer requests by summarizing the outcome, constraints, audience, and blast radius, then proposing a 3–7 step routing plan that identifies the smallest specialist surface and required agents before code changes.

Preflight routing does bypass extended routing when a concrete command or folder is specified, directly recommending the required AGENTS.md or OpenSpec commands to load instead of running through broad design discussions.

The best way to triage unclear work sequencing across repositories is to generate a concise routing decision that scopes context, identifies blast radius, and stops execution when a single clarifying question resolves the ambiguity.

You should not use a preflight routing checklist when a request is already clear, confined to a single platform layer, or does not span multiple repositories, OpenSpec workflows, or specification modes requiring intent clarification.