mirror of
https://github.com/azaion/detections.git
synced 2026-04-25 21:36:31 +00:00
Oleksandr Bezdieniezhnykh
3482173e7d
ci/woodpecker/push/02-build-push Pipeline was successful
Made-with: Cursor
30 lines
1.5 KiB
Plaintext
30 lines
1.5 KiB
Plaintext
---
|
|
description: "Forbid spawning subagents; the main agent must do the work directly"
|
|
alwaysApply: true
|
|
---
|
|
# No Subagents
|
|
|
|
Do NOT create or delegate to subagents. This includes:
|
|
|
|
- The `Task` tool with any `subagent_type` (e.g. `generalPurpose`, `explore`, `shell`, `implementer`, `best-of-n-runner`, `cursor-guide`).
|
|
- Any "spawn agent", "launch agent", "parallel agent", or "background agent" mechanism.
|
|
- Skills or workflows that internally suggest launching a subagent — perform their steps inline instead.
|
|
|
|
## Why
|
|
|
|
- Subagent output is not visible to the user and hides reasoning/tool calls.
|
|
- Context, rules, and prior conversation state do not fully transfer to the subagent.
|
|
- Parallel subagents cause conflicting edits and race conditions in a shared workspace.
|
|
- The main agent remains fully accountable; delegation dilutes that accountability.
|
|
|
|
## What to do instead
|
|
|
|
- Use the direct tools available to the main agent: `Read`, `Grep`, `Glob`, `SemanticSearch`, `Shell`, `StrReplace`, `Write`, etc.
|
|
- For broad exploration, run `Grep`/`Glob`/`SemanticSearch` yourself and read the files directly.
|
|
- For multi-step work, use `TodoWrite` to track progress inline.
|
|
- For isolated experiments the user explicitly asks for, use a git branch/worktree you manage directly — not a subagent runner.
|
|
|
|
## Exception
|
|
|
|
Only spawn a subagent if the user explicitly requests it in the current turn (e.g. "use a subagent to…", "launch an explore agent…"). Even then, confirm once before spawning.
|