01
What this skill does
Use this skill for non-trivial multi-step work where background subagents may help but the parent agent must keep ownership of framing, shared contracts, delegation, integration, verification, and user communication. It gives the coordinator a decision checklist for handling simple work directly, choosing explorer or worker shapes, defining disjoint scopes, protecting atomic migrations, and turning worker outputs into reviewed evidence.
02
When to use it
- SignalDeciding whether a complex repo task should be handled directly or delegated.
- SignalAssigning clear worker ownership boundaries in large repositories, monorepos, or dirty worktrees.
- SignalKeeping shared contracts, package exports, sequencing, and destructive migration boundaries under parent-agent ownership.
- SignalCoordinating independent exploration, implementation, review, or verification slices.
- SignalSynthesizing 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 based on independence, scope clarity, and synthesis cost.
- 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
- SignalA delegation decision that explains what stays with the parent and what, if anything, is assigned to workers.
- SignalWorker prompts with explicit ownership boundaries, constraints, validation, and expected output.
- SignalA synthesis of adopted results, blockers, command evidence, residual risks, and final verification.
05
Important boundaries
- SignalDo not delegate trivial requests or immediate blocking work that the parent must handle now.
- SignalDo not assign sibling workers overlapping write ownership for shared files, schemas, generated artifacts, or global config.
- SignalDo not accept worker output as fact without reviewing changed files, artifacts, command output, or other concrete evidence.
06