subagents

Gates subagent spawning decisions with dispatch rationales, checklists, and model routing rules.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill subagents-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagents
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/subagents
Command: npx skills add https://github.com/danielsuguimoto/skills --skill subagents-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents wasteful or incorrect subagent delegation by enforcing strict gates before any spawn, keeping work inline when coordination overhead exceeds the benefit. ## Core Features & Use Cases - Dispatch Rationales: Spawn only for parallel time wins (≥3 independent workstreams), verifiable context offloading, or explicit user request. - Pre-Spawn Checklist: A mandatory five-point checklist covering rationale, parallelism, offload size, profile, and foreground/background mode before every dispatch. - Model Routing: Maps task shapes (scout, doc lookup, implementation, synthesis, test runs) to fast, mid, or strong model tiers. - Use Case: Before launching a large codebase exploration, the agent checks the offloading exception gate (more than 5 file reads across more than 2 modules) and dispatches a read-only scout that returns a distilled brief instead of flooding the parent context. ## Quick Start Before spawning any subagent or running a large codebase scan, apply the subagents dispatch gates and pre-spawn checklist to decide whether to delegate or stay inline.

Frequently Asked Questions about subagents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I spawn a subagent instead of working inline?▼

Spawn a subagent only when one of three rationales holds: at least 3 independent workstreams with no shared writes, a verifiably large scan where the parent needs only a distilled brief, or an explicit user request. Otherwise default to inline work.

How do I decide between foreground and background subagents?▼

Default to foreground. Use background only when at least 3 independent workstreams exist, needed tools are pre-approved or read-only, and the parent has productive work while waiting, since background agents have reduced capabilities.

Should I spawn a subagent to invoke a skill like commit or PR creation?▼

No. Skill workflows such as commit, push, PR-create, and branch creation run inline in the parent. Spawning a subagent just to invoke a skill is an anti-pattern unless a dispatch rationale independently fires.

What model tier should a code exploration subagent use?▼

Code exploration and scout tasks route to fast, cheap models since they are bounded reads returning distilled briefs. Reserve strong models for implementation, PR fixes, and synthesis requiring multi-step reasoning.

What happens if a subagent returns BLOCKED or unavailable?▼

If a subagent returns BLOCKED, NO_*, or UNAVAILABLE, do that work inline instead of retrying the dispatch. The parent completes the task directly rather than spawning another attempt.