agentsclimarketplace
Sign in

Delegation triggers

Skill vitaliikapliuk/modelharness/skills/delegation-triggers

Use when deciding whether to spawn subagents — explicit rules for when delegation pays off and when direct work is faster. Opus 4.8 under-delegates by default; these rules correct that.From its SKILL.md

Install
npx -y skills add vitaliikapliuk/modelharness --skill delegation-triggers

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.4 KB, as published. Nobody here has run it

Delegation Triggers

Opus 4.8 is documented to under-reach for subagents. Apply these rules instead of intuition.

Delegate (spawn subagents, in parallel where independent) when:

  • Work fans out across independent items: reading/searching many files, auditing several modules, running several independent investigations.
  • You need a broad search where only the conclusion matters (use a read-only explore subagent; you keep the answer, not the file dumps).
  • You need fresh-context verification of your own work (see verification-loop).
  • Two or more workstreams have no shared state and no ordering dependency — launch them in one message so they run concurrently.

Work directly when:

  • A single file read or a known-location lookup would answer the question.
  • Edits are sequential and each depends on the previous result.
  • The task is small enough that subagent setup costs more than it saves.

How

  • Give each subagent a self-contained brief: goal, exact scope, what to return.
  • Don't duplicate a delegated search yourself — wait for the result.
  • Prefer asynchronous delegation: keep working on the main thread while subagents run; intervene only if one goes off track.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.