spawn

Spawn specialized subagents with scoped file ownership and permission checks.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/c-daly/agent-swarm --skill spawn-c-daly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spawn
Source: https://github.com/c-daly/agent-swarm/tree/main/skills/spawn
Command: npx skills add https://github.com/c-daly/agent-swarm --skill spawn-c-daly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation and management of subagents to handle specialized tasks, enabling efficient workload distribution and better context isolation.

Core Features & Use Cases

  • Orchestrated delegation: Spawn Explorer, Researcher, Architect, Implementer, and Reviewer subagents as needed to tackle complex tasks without overloading the main agent.
  • Clear scope and guardrails: Enforce per-task file ownership, output formats, and permission checks to maintain safety and traceability.
  • Use Case: When a project requires both code discovery and external web research, spawn dedicated subagents to perform each task independently and report back.

Quick Start

Use the spawn skill to delegate a requirements-gathering task to an Explorer subagent and a Researcher to gather docs.

Frequently Asked Questions about spawn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate specialized tasks to subagents in a multi-agent workflow?

Delegating tasks to subagents automates workload distribution by spawning Explorer, Researcher, Architect, Implementer, and Reviewer agents for specific responsibilities. Define clear task prompts, assign scoped file ownership, specify output formats, and enforce permission checks to maintain safety and traceability across the orchestrated delegation.

What's the best way to orchestrate multiple agents for complex projects?

Orchestration spawns specialized subagents as needed rather than overloading a single agent with all work. Each subagent handles a defined scope—code discovery, research, architecture, implementation, or review—with isolated context and independent reporting, reducing errors and improving task clarity.

When should I use task delegation with subagents instead of a single agent?

Task delegation with subagents fits projects requiring parallel work streams, external research, code discovery, and specialized expertise. When a task requires both web research and codebase analysis simultaneously, spawning dedicated agents prevents context collision and accelerates completion.

How do I set up file ownership and permission checks for subagent workflows?

Configure per-task file ownership by defining which files each subagent can access and modify, then enforce permission checks at spawn time. This maintains safety in multi-agent contexts by preventing unintended file modifications and ensuring traceability across delegated work.

What output formats should subagents use for verification and handoff?

Specify structured output formats for each subagent task before spawning to enable automated verification and handoff between agents. Clear formats allow orchestrators to validate results, extract data reliably, and route outputs to downstream agents without manual parsing.

Can I use task delegation to isolate risky or experimental work?

Yes; task delegation isolates specialized work in scoped subagent contexts, containing risk from experimental code, external data, or complex analysis. Guardrails and output verification ensure failed or unexpected subagent work doesn't corrupt the main workflow.