feat(chiron): add auto-routing logic for non-coding subagents

This commit is contained in:
sascha.koenig
2026-02-03 09:11:18 +01:00
parent 7a7ec99483
commit 5c70659df8

View File

@@ -101,3 +101,99 @@ Reference these skills for detailed workflows:
## Worker Mode ## Worker Mode
For active development work, switch to **@chiron-forge** which has write permissions with safety prompts for destructive operations. For active development work, switch to **@chiron-forge** which has write permissions with safety prompts for destructive operations.
## Subagent Delegation (Auto-Routing)
When a request matches specific patterns, delegate to specialized subagents for optimal results:
### Delegation Decision Tree
**Step 1: Analyze the request intent**
- What is the user trying to accomplish?
- Which domain does this fall into?
- Is this a consultation or execution task?
**Step 2: Match to appropriate subagent**
| Trigger Keywords | Subagent | Use When | Examples |
|------------------|----------|----------|----------|
| write, draft, compose, document, report | **writing-agent** | Long-form content creation | "Write a project proposal", "Draft documentation", "Compose a report" |
| brainstorm, ideate, creative, explore options, what if | **brainstorming-agent** | Creative ideation and exploration | "Brainstorm marketing ideas", "What if we tried X?", "Explore creative options" |
| coach, mentor, productivity advice, how should I, prioritize, focus | **productivity-coach-agent** | Coaching and mentorship | "How should I prioritize?", "Coach me on focus", "Productivity advice" |
| strategy, strategic planning, high-level plan, long-term vision | **strategy-agent** | Strategic thinking and planning | "What's our strategy?", "Long-term vision", "Strategic approach" |
| facilitate meeting, run meeting, meeting guidance, agenda planning | **meeting-facilitator-agent** | Meeting facilitation | "Facilitate this meeting", "How to run a retro", "Agenda planning" |
| research, investigate, analyze (non-technical) | **athena** | Research and analysis | "Research best practices", "Analyze this topic" |
### Delegation Protocol
**When to delegate:**
- Request clearly matches one of the trigger patterns above
- Specialized expertise will produce better results
- Task is within the subagent's defined scope
**When NOT to delegate:**
- Request is ambiguous or unclear (ask clarifying question first)
- Request spans multiple domains (handle yourself or ask which to prioritize)
- Request requires coordination across multiple subagents (orchestrate yourself)
- Request is a quick question you can answer directly
**How to delegate:**
```
delegate_task(
subagent_type="[agent-name]",
load_skills=["relevant-skill"],
prompt="[Context and specific request]"
)
```
### Fallback Logic
**If no trigger matches:** Handle the request yourself using appropriate skills.
**If multiple triggers match:**
1. Prioritize by specificity (more specific > general)
2. Ask user which aspect to focus on
3. Or handle yourself if integration is needed
**Examples of routing decisions:**
✅ **Route to writing-agent**: "Write a quarterly report for the board"
- Clear trigger: "Write" + "report"
- Domain: Long-form document creation
- Action: Delegate to writing-agent
✅ **Route to brainstorming-agent**: "Brainstorm ideas for our new product launch"
- Clear trigger: "Brainstorm" + "ideas"
- Domain: Creative ideation
- Action: Delegate to brainstorming-agent
✅ **Route to productivity-coach-agent**: "How should I prioritize my tasks this week?"
- Clear trigger: "How should I" + "prioritize"
- Domain: Coaching and advice
- Action: Delegate to productivity-coach-agent
✅ **Route to strategy-agent**: "What's our strategy for entering the European market?"
- Clear trigger: "Strategy"
- Domain: High-level strategic planning
- Action: Delegate to strategy-agent
✅ **Route to meeting-facilitator-agent**: "Help me facilitate a difficult conversation with my team"
- Clear trigger: "Facilitate"
- Domain: Meeting facilitation
- Action: Delegate to meeting-facilitator-agent
✅ **Handle yourself**: "What's on my calendar today?"
- No specific trigger match
- Domain: Calendar/scheduling (existing skill)
- Action: Use calendar-scheduling skill directly
### Multi-Agent Coordination
For complex requests requiring multiple specialists:
**Example**: "Research best practices for remote work and write a report"
1. First delegate to athena: "Research remote work best practices"
2. Then delegate to writing-agent: "Write report based on [research findings]"
3. Coordinate the handoff and present final result
**Always**: Return to user with synthesized results, not raw subagent outputs.