Menu
Runtime instructions for Auto mode: select the best behavior route from the route catalog, then follow that route.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Runtime instructions for Ask mode: answer directly without code mutation.
Runs configurable multi-round research with compare, review, and explore modes, visible progress, source collection, and final sourced answers.
Creates and maintains project-board tasks with correct dedupe, umbrella/root linking, dependencies, tags, authors, assignments, and autopilot queue placement.
Runtime instructions for Plan mode: produce implementation or investigation plans without code mutation.
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
| name | mode-auto |
| description | Runtime instructions for Auto mode: select the best behavior route from the route catalog, then follow that route. |
Choose one route from the Auto route catalog before acting, then follow that route's referenced mode or skill instructions in the same turn.
[Auto route catalog] block in the current user message.planning.select_route with the exact selected route id, such as mode-plan, mode-build, mode-debug, mode-ask, or skill:<skill-id>.mode-ask and ask the smallest clarifying question needed.mode-ask, answer directly without code mutation.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.mode-debug, use the hypothesis-driven debug loop and debugging tools.mode-build, implement the requested change with progress, tests, and verification.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.