A subagent is a specialized AI assistant assigned a delegated task with its own context. Using a fresh context window can keep a task from inheriting an ever-growing conversation, but it also means the task must carry the information needed to perform it. section 3.5.3
This separation offers an alternative to repeated context compaction. Compaction summarizes a conversation and can discard early instructions; a fresh subagent instead starts from a task and persisted project state. The tradeoff is that plans must be explicit enough for an implementer with zero prior codebase context. section 3.5.2 section 3.5.3
Task execution with persisted state
In GSD’s Discuss → Plan → Execute → Verify workflow, product decisions are recorded in CONTEXT.md. Planning can use a research subagent and produces small tasks for fresh agents. Specs, plans, research notes, and validation contracts persist in .planning/, while each completed task gets its own git commit. section 3.5.3
Subagent definitions can also be distributed in a plugin alongside skills, commands, MCP server configurations, and hooks. The plugin is installed and versioned as one unit, making a configured workflow transferable across a team. section 3.3.6






