From db8c84acb4f72c4ce3e1612365ff912fdfe3cea1 Mon Sep 17 00:00:00 2001 From: Trevin Chow Date: Fri, 13 Mar 2026 14:54:27 -0700 Subject: [PATCH] fix(skills): include tool constraint in subagent task prompts The file-tools-over-bash instruction was in the orchestrator's context but not passed to spawned subagents. Changed to an explicit quoted instruction block that must be included in each subagent's task prompt so it's visible to the subagent, not just the orchestrator. --- .../compound-engineering/skills/ce-compound-refresh/SKILL.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md b/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md index d5cba9f..f79f4be 100644 --- a/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md +++ b/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md @@ -200,7 +200,9 @@ Use subagents for context isolation when investigating multiple artifacts — no | **Parallel subagents** | 3+ truly independent artifacts with low overlap | | **Batched subagents** | Broad sweeps — narrow scope first, then investigate in batches | -Subagents should use dedicated file search and read tools for investigation — not shell commands. This avoids unnecessary permission prompts and is more reliable across platforms. +**When spawning any subagent, include this instruction in its task prompt:** + +> Use dedicated file search and read tools (Glob, Grep, Read) for all investigation. Do NOT use shell commands (ls, find, cat, grep, test, bash) for file operations. This avoids permission prompts and is more reliable. There are two subagent roles: