fix: make subagent dispatch harness-neutral

Three skills named Claude Code's `Agent` tool and its `general-purpose`
and `Explore` agent types directly. The repo installs across Claude Code,
Codex, and other Agent-Skills harnesses, none of which share that tool or
those type names, so the instruction was unfollowable outside Claude Code.

Each site now describes the shape of the dispatch — parallel subagents,
and what capability each one needs — and leaves the mechanism to the
harness.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock
2026-08-06 13:58:35 +01:00
co-authored by Claude Opus 5
parent 8b36d4fb26
commit 14bfbbd865
4 changed files with 10 additions and 3 deletions
+1 -1
View File
@@ -57,7 +57,7 @@ Each smell reads *what it is* → *how to fix*; match it against the diff:
### 4. Spawn both sub-agents in parallel
Send a single message with two `Agent` tool calls. Use the `general-purpose` subagent for both.
Dispatch both with your harness's subagent mechanism, in parallel — one message with two calls where the harness supports it. Pick its most general-purpose agent for both: each must read files and run `git`, so a search-only agent is too narrow.
**Standards sub-agent prompt** — include: