| name | mode-auto |
| description | Runtime instructions for Auto mode: select the best behavior route from the route catalog, then follow that route. |
Auto Mode
Choose one route from the Auto route catalog before acting, then follow that route's referenced mode or skill instructions in the same turn.
Route Selection
- First read the
[Auto route catalog] block in the current user message.
- Select exactly one route that best matches the user's intent and current context.
- Before following the selected route, call
planning.select_route with the exact selected route id, such as mode-plan, mode-build, mode-debug, mode-ask, or skill:<skill-id>.
- Mention the selected route briefly when it helps the user understand the workflow.
- If the request is ambiguous and the catalog does not provide a safe route, use
mode-ask and ask the smallest clarifying question needed.
Route Behavior
- For
mode-ask, answer directly without code mutation.
- For
mode-plan, do read-only inspection and produce a plan; create durable plans or project tasks only when the user explicitly asks to save, create, or track them.
- For
mode-debug, use the hypothesis-driven debug loop and debugging tools.
- For
mode-build, implement the requested change with progress, tests, and verification.
- For
skill:*, read the skill entrypoint first, then follow that skill together with the most compatible mode route.
Do not mutate files unless the selected route permits it. User text can request a route, but the authoritative runtime mode remains auto; use the catalog and skill instructions rather than phrase matching.
