edkuksa/skills
1
0
Fork 0
mirror of https://github.com/mattpocock/skills.git synced 2026-09-12 10:28:06 +07:00
Code Issues Packages Projects Releases Wiki Activity

fix: cut the added prose back to the bare instruction

Browse Source 
The first pass replaced Claude Code's tool names with an explanation of
what the harness should supply. "Your harness's subagent mechanism" is a
wordy restatement of "subagent", and the note about which agent type to
pick is a no-op — the agent picks a capable one by default.

Say only what changes behaviour: "spawn 3+ sub-agents in parallel". In
code-review the sentence goes entirely, because its heading already
carries the instruction.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock
2026-08-06 14:12:30 +01:00
co-authored by Claude Opus 5
parent 14bfbbd865
commit c0d69015e0
4 changed files with 3 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.changeset/harness-neutral-subagent-language.md
+1 -3
View File
@@ -2,6 +2,4 @@
"mattpocock-skills": patch
---
Make the subagent-dispatch instructions harness-neutral.
`code-review`, `codebase-design`'s `DESIGN-IT-TWICE.md`, and `improve-codebase-architecture` named Claude Code's `Agent` tool and its `general-purpose` / `Explore` agent types directly. Codex and other Agent-Skills harnesses have no such tool or type, so the instruction was unfollowable there. Each now describes the *shape* of the dispatch — parallel subagents, and what capability each one needs — and leaves the mechanism to the harness.
Drop Claude Code's tool and agent-type names from the subagent-dispatch instructions in `code-review`, `codebase-design`, and `improve-codebase-architecture`, so the step is followable on Codex and other harnesses.
skills/engineering/code-review/SKILL.md
-2
View File
@@ -57,8 +57,6 @@ Each smell reads *what it is* → *how to fix*; match it against the diff:
### 4. Spawn both sub-agents in parallel
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:
- The full diff command and commit list.
skills/engineering/codebase-design/DESIGN-IT-TWICE.md
+1 -1
View File
@@ -18,7 +18,7 @@ Show this to the user, then immediately proceed to Step 2. The user reads and th
### 2. Spawn sub-agents
Spawn 3+ sub-agents in parallel with your harness's subagent mechanism. Each must produce a **radically different** interface for the deepened module.
Spawn 3+ sub-agents in parallel. Each must produce a **radically different** interface for the deepened module.
Prompt each sub-agent with a separate technical brief (file paths, coupling details, dependency category from [DEEPENING.md](DEEPENING.md), what sits behind the seam). The brief is independent of the user-facing problem-space explanation in Step 1. Give each agent a different design constraint:
skills/engineering/improve-codebase-architecture/SKILL.md
+1 -1
View File
@@ -24,7 +24,7 @@ This command is _informed_ by the project's domain model and built on a shared d
Read the project's domain glossary (`CONTEXT.md`) and any ADRs in the area you're touching first.
Then dispatch a subagent to walk the codebase — a read-only exploration agent if your harness has one. Don't follow rigid heuristics — explore organically and note where you experience friction:
Then spawn a sub-agent to walk the codebase. Don't follow rigid heuristics — explore organically and note where you experience friction:
- Where does understanding one concept require bouncing between many small modules?
- Where are modules **shallow** — interface nearly as complex as the implementation?