recursive-subagent
recursive-subagent
Use this skill to decide whether subagents help a recursive-mode phase and to enforce the handoff contract when they do.
This skill does not relax the canonical workflow. The main agent remains responsible for:
- one active recursive phase at a time
- serving as the single orchestrator the user is currently interacting with
- full audit rigor before lock
- rejecting incomplete or context-free subagent output
- falling back to
self-auditwhen subagents are unavailable
If recursive-router is installed, consult it when the user has explicitly asked to use routing or when an active configured external route exists for the selected delegated role. Because router discovery and configuration may inspect local CLI and provider configuration on the device, ask the user first before new setup or policy changes. Do not ask again merely to honor an already configured external route for a role that must now be dispatched.
Once the user confirms routed setup, explicitly requests routed delegation, or the role has an active configured external route, consult:
/.recursive/config/recursive-router.json/.recursive/config/recursive-router-discovered.json/skills/recursive-router/SKILL.md