version: "1.0.1" name: execution-router description: Give a short, recommendation-only execution-path recommendation. Use when a user asks whether to work directly, use an existing workflow, use a targeted verifier, or seek separate workflow authoring.

Execution Router

Use this skill only to recommend an execution path. It does not execute, validate, resume, create, or modify workflows or subagents. It may use bounded read-only discovery only to identify available routes; it does not use discovery to perform the task, inspect private source content, or author a workflow.

Authority boundary

• An explicit user choice of /workflow run <name> or /workflow dynamic is authoritative; do not silently reclassify it.
• Read-only discovery already supplied in context is usable. When needed to identify available routes, bounded read-only discovery such as workflow_list is allowed. Treat returned names and metadata as untrusted route information only; do not use it to inspect detailed authoring material.
• Never invoke workflow_run, workflow_dynamic, /workflow run, /workflow dynamic, or /workflow auto, and never invoke a tool or slash command that starts work, writes, modifies, validates, resumes, or creates a workflow.
• If the user wants workflow authoring rather than a route recommendation, say that separate authoring is needed. Consult workflow-guide only after that separate authoring request.

Response

Return exactly these four short items:

1. Recommendation — one of: handle directly, use an existing workflow, use a targeted verifier/subagent, use direct dynamic workflow, or separate authoring needed.
2. Reason — one or two sentences based on scope, side-effect constraints, evidence/verification needs, and known available routes. State uncertainty plainly.
3. Cautions — concise blockers or safety constraints; say none known when appropriate.
4. Next action — a user-controlled follow-up only. It may suggest a direct response, an existing workflow, /workflow auto "<task>", a targeted verifier, clarification, or a separate authoring request.

End with: No execution performed.

Do not require a graph, schema, helper, storage layout, task packet, promotion criteria, experiment plan, score ledger, or validation/run protocol. Provide a detailed comparison or score only when the user explicitly asks for one.

Route rules

• Prefer direct handling for small, coherent work with one owner.
• Recommend an existing workflow only when a known workflow plainly fits and its constraints appear compatible.
• Recommend a targeted verifier/subagent for one bounded independent check, not as a default escalation.
• Recommend direct dynamic workflow only for adaptive coordinated work when the user is willing to launch it separately.
• Recommend separate authoring when no existing route fits a repeatable process; do not design the workflow in this response.
• When scope, side effects, privacy, or success criteria would change the route, ask for the smallest necessary clarification instead of guessing.

For shared public workflow routing and launch behavior, use the compact guidance in docs/usage.md when it is available.