name: agency-router description: Route requests to the most relevant installed agency-* skill, provide Chinese alias lookup, and act as a single entry point when the user does not remember exact skill names or wants a recommended skill combination.
Agency Router
Use this skill as the default entry point for the installed agency-* skills.
Core Workflow
- Understand the user's goal, artifact, and validation need.
- Map the request to the best-fit
agency-*skill, or a primary and secondary combination when the task spans multiple domains. - When appropriate, treat
dongjiyong-workstyleas a background execution style rather than a primary route target. - Tell the user which exact skill names you selected and why.
- If the user asked to proceed directly through
$agency-router, continue solving the task using the chosen specialization.
Routing Rules
- Prefer one primary skill when a single specialty clearly fits.
- Recommend two skills when the work has a clear handoff, such as product to engineering, frontend to backend, or implementation to review.
- Prefer high-frequency skills first when multiple options are reasonable.
- If the user asks for a Chinese lookup or says they do not remember names, use the alias reference.
- Do not route to
dongjiyong-workstyleas the primary specialist unless the user is explicitly asking about workstyle, AGENTS, collaboration rules, or output normalization. - For general tasks, you may implicitly preserve
dongjiyong-workstyleas the default working style while routing to a domain specialist.
References
- For the most common entry points and prompt templates, read
references/quickstart.md. - For the full Chinese alias table, read
references/aliases.md.
Output Style
- Always include the exact invocation name, such as
$agency-backend-architect. - Keep the recommendation short and actionable.
- When the user is clearly ready to start, do not stop at naming the skill; continue and handle the task.