09_multi_agent_delegation_skill

Overview

This skill prepares isolated sub-workspaces so parallel "Worker" agents can execute tasks safely and deterministically. It creates a ready-made swarm directory with mission instructions and context files so each worker can start immediately. It is designed for PowerShell-based agent workflows and emphasizes safety gates and impasse detection.

How this skill works

The spawner makes a new subdirectory (./.swarm/<task_name>) and copies specified context files and workspace metadata into it. It generates a MISSION.md that contains the worker-specific instructions, success criteria, and guardrails. The resulting workspace is isolated so the worker runs with deterministic inputs and the orchestrator can monitor outcomes and handle failures.

When to use it

• Splitting a large project into parallel subtasks for faster completion
• Delegating time-boxed audits, tests, or reviews to independent agents
• Running adversarial or sandboxed experiments that must not affect the main workspace
• Creating repeatable worker environments for CI or batch processing
• Isolating risky operations behind safety gates before merging results

Best practices

• Provide concise, measurable instructions and explicit success criteria in --instructions
• Include only necessary context files to keep worker workspaces minimal
• Use descriptive, unique task names to avoid directory collisions
• Attach stop conditions and post-action checks in MISSION.md to prevent loops
• Monitor worker outputs and run failure postmortems for any impasses

Example use cases

• Spawn an agent to perform an auth audit on a specific module with a focused MISSION.md
• Create multiple workers to parallelize test-case generation and validation
• Delegate a security fuzzing task in an isolated swarm directory to limit side effects
• Run independent code refactors per component and collect results centrally
• Launch adversarial reviewers to probe a change set without exposing the main workspace