Dispatch Debugging
This guide helps diagnose and resolve issues with skill dispatch and protocol injection.Common Issues
Wrong Skill Selected
Symptom: Task executes with wrong skill (e.g., research task uses ct-task-executor) Diagnosis:-
Add explicit label:
-
Use keyword in title:
-
Manual override:
Unresolved Tokens
Symptom: Subagent fails with references to{{TOKEN_NAME}}
Diagnosis:
-
Verify task exists:
-
Check parent epic:
-
Ensure session is active:
Skill Not Found
Symptom: Error “Unknown skill: ct-my-skill” Diagnosis:- Register skill in
skills/manifest.json - Verify skill path exists:
ls skills/ct-my-skill/SKILL.md
Protocol Not Loaded
Symptom: Subagent doesn’t follow skill instructions Diagnosis:- Check SKILL.md syntax - Valid markdown with proper sections
- Verify shared protocols exist:
Debug Mode
Enable Verbose Dispatch
- Labels checked
- Keywords matched
- Task type evaluated
- Final skill selection
Trace Protocol Composition
- Base protocol loaded
- Skill protocol loaded
- Tokens resolved
- Final prompt length
Diagnostic Commands
Check Dispatch Decision
Verify Token Resolution
Test Keyword Matching
Validate Manifest
Error Reference
| Error | Cause | Fix |
|---|---|---|
Unknown skill | Skill not in manifest | Add to skills/manifest.json |
Unresolved tokens | Missing task metadata | Verify task exists with required fields |
Protocol not found | SKILL.md missing | Create skills/ct-name/SKILL.md |
Base protocol missing | _shared dir issue | Restore skills/_shared/ |
Recovery Procedures
Reset Dispatch Cache
Rebuild Manifest
Force Skill Selection
When automatic dispatch fails:Related Documentation
- Skill Dispatch Algorithm - How dispatch works
- Protocol Injection Flow - How protocols load
- Architecture - Full system design
