subagent-delegation

Delegates GSD workflow tasks to Antigravity subagents with workspace isolation and inline fallback.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/amanpal3/SKILLs --skill subagent-delegation-amanpal3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-delegation
Source: https://github.com/amanpal3/SKILLs/tree/main/.agent/plugins/gsd/.agents/skills/subagent-delegation
Command: npx skills add https://github.com/amanpal3/SKILLs --skill subagent-delegation-amanpal3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Orchestrator agents that read dozens of files and execute every task themselves exhaust their context window before a phase completes, making quality thresholds unreachable. This Skill defines when and how to delegate GSD work to native Antigravity subagents so the orchestrator preserves its context budget. ## Core Features & Use Cases - Delegation Decision Matrix: Maps work types (plan execution, plan authoring, verification, research, debugging) to the correct subagent (gsd-executor, gsd-planner, gsd-verifier, gsd-researcher, gsd-debugger). - Invocation Contracts: Enforces prompt construction rules — paths instead of pasted file contents, explicit tool grants, and compact return blocks. - Workspace Isolation Modes: Selects inherit, branch, or share isolation based on whether subagents write concurrently, preventing commit corruption across parallel waves. - Inline Fallback: Detects Antigravity versions lacking invoke_subagent and switches to a degraded single-plan-per-session mode with context-health monitoring. - Use Case: While running a multi-plan GSD wave, the orchestrator spawns one gsd-executor per plan in isolated git worktrees, receives compact status blocks, and merges results without ever loading plan contents into its own context. ## Quick Start Ask the agent to delegate execution of the current GSD plan to a subagent following the subagent-delegation protocol.

Frequently Asked Questions about subagent-delegation

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

FAQPage Schema
How do I delegate tasks to subagents in Antigravity?▼

Call invoke_subagent targeting the subagent by the name in its .agents/agents/*.md definition. The prompt must include the contract fields, file paths instead of pasted contents, constraints from STATE.md, and the expected return block format.

What tasks should be delegated to subagents versus kept in the orchestrator?▼

Delegate plan execution, plan authoring, verification, research, and debugging to dedicated subagents. Keep argument parsing, file existence checks, wave grouping, STATE.md updates, and user communication in the orchestrator.

Does subagent delegation work on Antigravity 1.x?▼

No, invoke_subagent requires Antigravity 2.0 or later. On 1.x, workflows run in degraded inline mode: one plan per invocation, pausing between plans, and stopping at 70% context usage.

Why does a subagent hang instead of failing when tools are misconfigured?▼

An unmapped or misspelled tool name causes the subagent to hang rather than fail. Tool names must be copied exactly from the registry, and the tools field must be explicitly declared since subagents do not inherit the parent's toolset.

When should I use branch versus share workspace isolation?▼

Use branch when two or more subagents write files concurrently, giving each an isolated git worktree. Use share for read-only concurrent work like research or verification, and inherit for sequential single-writer work.

What happens if a subagent returns file contents instead of a path?▼

Returning file contents instead of a path is treated as a failure meaning the artifact never reached disk. Handle it as blocked, identify the missing capability, and fix the subagent definition rather than pasting the content onward.