01
What this skill does
Use this skill for non-trivial multi-step work where async/background subagents or local decomposition may help but the parent agent must keep ownership of framing, shared contracts, delegation, isolation, integration, verification, and user communication. It gives the coordinator a decision checklist for handling simple work directly, ordering queued requests, choosing explorer or worker shapes, defining disjoint scopes, protecting atomic migrations, and turning worker outputs into reviewed evidence.
02
When to use it
- 01Deciding whether a complex repo task should stay local, be decomposed, or be delegated.
- 02Assigning clear worker ownership boundaries in large repositories, monorepos, multi-root workspaces, dirty worktrees, or isolated worktrees and branches.
- 03Keeping shared contracts, package exports, sequencing, and destructive migration boundaries under parent-agent ownership.
- 04Coordinating queued independent requests, async exploration, implementation, review, or verification slices.
- 05Synthesizing worker outputs while preserving parent-agent accountability for the final result.
03
How it works
- 01
Read applicable repository rules and check the dirty worktree before assigning ownership.
- 02
Map success criteria, affected systems, likely owner files, shared contracts, and verification commands.
- 03
Keep shared files and contracts parent-owned unless one worker is explicitly assigned as the sole owner.
- 04
Choose zero, one, or a small set of workers and pick shared workspace or isolated worktree/branch execution based on risk.
- 05
Give each worker a concrete objective, allowed scope, forbidden actions, validation expectation, and output contract.
- 06
Review worker evidence, resolve conflicts or gaps, integrate only adopted work, and run the narrowest credible verification.
04
What you get back
- 01A delegation decision that explains what stays with the parent and what, if anything, is assigned to workers.
- 02Worker prompts with explicit ownership boundaries, constraints, validation, and expected output.
- 03A synthesis of adopted results, blockers, command evidence, residual risks, and final verification.
05
Important boundaries
- 01Do not delegate trivial requests or immediate blocking work that the parent must handle now.
- 02Do not assign sibling workers overlapping write ownership unless isolated branches or worktrees make the planned merge explicit.
- 03Do not accept worker output as fact without reviewing changed files, artifacts, command output, or other concrete evidence.
06