hermes-ephemeral-delegation

Featured

Trigger: broad exploration, multi-file reads, tests/builds, fresh review, or multi-step debug. Orchestrate complex work via delegate_task to protect context.

AI & Automation 6,637 stars 740 forks Updated today MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## 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. ## Decision Gates | Situation | Action | |-----------|--------| | Need to read 4+ files to understand | Delegate a narrow exploration worker | | Need to write 2+ non-trivial files | Delegate a single writer with the full mission | | Need to run tests or builds | Delegate an executor; do not run inline | | Need an adversarial review of a diff | Delegate a fresh-context reviewer | | Multi-step debug t...

Details

Author
Gentleman-Programming
Repository
Gentleman-Programming/gentle-ai
Created
6 months ago
Last Updated
today
Language
Go
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

delegate

TRIGGER when: asked to delegate work, execute or parallelize a plan, "run this plan", "delegate this", or after /prd or plan creation. Decomposes work by dependency, launches worker sub-agents in parallel waves, validates completion, and reports results while preserving failure isolation and recursion limits.

38 Updated today
mifunedev
AI & Automation Listed

delegate-work

Delegate bounded work to Codex subagents and coordinate their results with explicit ownership, evidence, and stopping conditions. Use when the user explicitly asks for agents, subagents, delegation, parallel work, or an agent team, or when an applicable repository instruction explicitly requires delegation. Do not use merely because a task is large; keep tightly coupled, sequential, or overlapping work in the main task.

4 Updated 2 days ago
dayfinggg
AI & Automation Listed

delegate-work

Brief a background agent, confirm the brief arrived, and verify its report before acting on it. Use when writing the prompt for a subagent or parallel session, when several agents will run against one repository, when an instruction sent to a running agent goes unmentioned in its report, when a delegated fix has been rejected and another verification round is about to start, or before relaying a delegate's report onward. Also use when a delegate's final report arrives as a fragment or refers to a message that never reached you. Do NOT use to measure a run's cost (audit-agent), to prove a green check could go red (prove-checks), or to check a delegated claim (research-it).

5 Updated today
sergeyklay