aggel008 Compound Delivery
This skill is about organizing complex work, not writing code by itself.
Use it when:
- one task contains several independent parts
- you want parallel progress instead of one-thread-at-a-time work
- investigation, implementation, and verification can run separately
- the user explicitly wants subagents or delegated work
Main benefit:
- faster execution on composite tasks
- less context overload in one agent
- cleaner separation between implementation and checking
When To Use Delegation
Use delegation only when the user has asked for subagents, delegation, or parallel agent work in this thread.
Good delegation targets:
- codebase exploration with a specific question
- a bounded implementation on a disjoint file set
- verification that can run in parallel with implementation
- isolated documentation drafting
Bad delegation targets:
- the immediate blocking task when you need the answer before you can move
- vague “go investigate everything”
- overlapping edits to the same files
Workflow
- Identify the immediate critical-path step and keep it local.
- Split off sidecar tasks that are concrete, parallelizable, and non-overlapping.
- Delegate only what materially advances the result.
- While delegated work runs, keep moving on local non-overlapping work.
- Integrate results, verify, and close.
Delegation Rules
- State ownership clearly for delegated edits.
- Do not delegate and then idle waiting by default.
- Reuse subagents for follow-up only when context continuity matters.
- Prefer one sharp question over a broad open-ended brief.
- If a delegated result is needed on the critical path, wait only then.
Output
For larger tasks, produce:
- a short execution plan
- clear ownership for delegated work
- a verification summary
Review Mindset
Delegation is not the goal.
The goal is:
- better throughput
- less context pollution
- stronger verification
If delegation does not help those three, do the work locally.