hermes-ephemeral-delegation

Activation Contract

Load this skill when you are acting as the parent orchestrator and the work ahead has a named reason to delegate:

• A map you need to decide or route that exceeds the inline evidence budget (codebase mapping, approach comparison); never to read files you will read anyway before writing inline
• A writer reason: 2+ independent units of behavior (code, tests, and docs together; each several minutes of work) launched together, or the context backstop; a large task alone is tracked, not delegated
• A high-risk change that needs an independent verifier, or a large task's long suites and builds
• Fresh adversarial review (diffs, PR readiness, incident audit); never restart it automatically for a candidate whose terminal approved authority was already burned and that is unchanged since, unless a new independent review is deliberately requested
• 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 only for a named reason listed above. Without one, work inline following your logbook; file count, size, or a large task alone is never a reason.
• 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.

Decision Gates

Execution Steps

1. Identify which gate applies. If none applies, skip delegation.
2. Draft a self-contained mission for the worker — include:
   • Exact goal (one sentence)
   • File paths or targets to act on
   • Relevant prior context the worker needs (decisions, conventions, prior findings)
   • Constraints (style, budget)
   • For a writer: the applicable test-first policy and runner from ## Implementation Routing. Write one RED test per requested rule; for every existing command or option the change touches, add one test proving its previous behavior still holds; add no other cases; update help text and docs for any changed command, option, or message
   • For a verifier: the Verify handoff from the Delegated Verification Gate (the whole feature document, the baseline commit, the probe command forms, first-launch probes in a mktemp -d scratch copy never inside the workspace, and its severity rules)
   • Expected evidence to return (e.g., file written, test output, URL found)
   • Allowed toolsets/MCP/skills the worker should use
   • Any SKILL.md paths to load before work
3. Call delegate_task with that mission.
4. Wait for the worker summary.
5. Verify the claimed output (check file existence, test result, side effect).
6. Synthesize the verified result into your orchestrator reply.

Output Contract

After synthesizing worker results, return:

• What was delegated and to how many workers
• What each worker returned (verified, not just claimed)
• Any discrepancy between worker self-report and verified evidence
• Final answer or next step for the user

References

• references/tuning-knobs.md — Full table of delegate_task configuration parameters and the explicit toolset/MCP/skill checklist for worker missions.