| name | hermes-ephemeral-delegation |
| description | Trigger: broad exploration, multi-file reads, tests/builds, fresh review, or multi-step debug. Orchestrate complex work via delegate_task to protect context. |
| license | Apache-2.0 |
| metadata | {"author":"gentleman-programming","version":"1.0"} |
Activation Contract
Load this skill when you are acting as the parent orchestrator and the work ahead falls into any of these categories:
- Broad exploration (4+ files to understand, codebase mapping, approach comparison)
- Multi-file implementation (touching 2+ non-trivial files)
- Test or build execution
- Fresh adversarial review (diffs, PR readiness, incident audit)
- Multi-step debugging that would flood the parent context
Do NOT load this skill if you are already inside a delegated child task — you are the executor, not the orchestrator.
Hard Rules
- Use
delegate_task for all complex work listed above. Do NOT execute it inline.
- Workers are EPHEMERAL: each
delegate_task call creates a fresh context. Do NOT request persistent agent files or profiles.
- Pass a self-contained mission. Workers have no memory of the parent conversation.
- Treat worker output as self-report: verify file writes, test pass/fail, URLs, and IDs before reporting success to the user.
- Batch parallel calls only for INDEPENDENT workstreams. Sequential dependencies must run sequentially.