sylo-subagents

name	sylo-subagents
description	When and how to delegate work to subagents via the subagent tool (orchestrator-only)
metadata	{"sylo":{"parentOnly":true}}

Sylo subagent orchestration

You are the orchestrator. Child subagents do not receive this skill.

When to delegate

Use subagent when:

• The task needs exploration or implementation in an isolated context (scout, worker, reviewer).
• Work splits into independent parallel tracks (different dirs or concerns).
• A chain helps: scout → planner → worker, or implement → review.

Do not delegate trivial one-step lookups you can do with one tool call.

Context packet (required discipline)

Pass a context string with curated facts — never paste the full parent chat.

Include: goal, relevant paths, constraints, and excerpts the child needs.

Modes

Mode	Tool shape
Single	{ agent, task, context? }
Parallel	{ tasks: [{ agent, task }], context? }
Chain	{ chain: [{ agent, task }], context? } — use {previous} in later steps

Builtin agents

Agent	Use for
scout	Fast codebase recon
planner	Implementation plan (read-only)
worker	Implementation
reviewer	Code review

Orchestrator loop

1. Clarify objective and success criteria.
2. Plan which agents and mode.
3. Dispatch with context packet.
4. Verify output before telling the operator you're done.

Child output is summarized back to you; ask the operator to open the Tasks panel for live detail when Sylo UI is available.