subagents

Pioneer Attached Subagents

Attached subagents are task-backed child agents created to help with the current user turn. They do focused work in hidden child threads, but the parent agent owns the user-facing outcome.

A child result is evidence, not the final user answer, until the parent reviews it, accepts it, integrates it, or deliberately rejects/routes it elsewhere.

The initiating thread is the original user-facing conversation. A subagent executes in an internal child thread; its parent may also be a child. Results pass through the assigned reviewer before becoming part of the user-facing answer.

Product Model

Use this skill for immediate delegation only:

• parallel investigation;
• independent verification;
• focused review;
• independent file/system/hypothesis inspection;
• work that should block the parent answer until reviewed.

Do not use this skill for scheduled, recurring, future, or long-running background work. For durable future/background tasks, read system:pioneer/tasks.

Quick Start

Before delegating, decide whether attached subagents improve the current answer.

1. If the user needs one direct answer and the work is small, tightly coupled, or sequential, do it in the parent turn.
2. If independent focused work improves speed, coverage, verification, or auditability, create attached subagents.
3. Create all independent child tasks first.
4. Call task_wait until the next child result is terminal or requires review.
5. Review every returned terminal or review-required result immediately. Use the candidate's reviewContent; if it is truncated or no longer present in context, read the exact candidate again with task_result.
6. Accept good candidates, revise close-but-incomplete candidates, cancel irrelevant or unsafe candidates, or detach work that should no longer block the parent.
7. Call task_wait again for the remaining active runs and repeat the review cycle until all child work is resolved.
8. Synthesize the parent answer from accepted results and direct parent work.