dispatch-subagentslisted

# Dispatch Subagents ## Purpose Define safe optional delegation for lifecycle work. This is a power skill, not a lifecycle phase. It decides whether subagents may be used, which work can be delegated, what ownership each worker has, how caps apply, and how the parent agent records and integrates results. ## Invocation Context Use this skill only when: - the user explicitly authorizes subagents, delegation, or parallel agent work - a lifecycle phase has independent candidate workstreams - a phase skill asks whether delegation is allowed If explicit authorization is missing, do not dispatch. Continue locally and record a refusal only when it affects the active artifact. ## What To Load **Foundation** (confirm in context; load if not already present): - Root `AGENTS.md` - `workflow/router.md` - `workflow/lifecycle.md` - `workflow/rules.md` **Minimum for invocation**: - This file - `references/output-schema.md` **Before starting work**: - `references/decision-tree-by-phase.md` — to determine whether dispatch is permitted for the active phase - `references/phase-caps.md` — to determine the hard cap for the active phase **Load when the step requires it**: - `references/independence-rules.md` — when evaluating whether candidate work items are truly independent - `references/worker-ownership-format.md` — when defining delegations and ownership boundaries - `references/logging-format.md` — when writing the dispatch log entry in the active artifact **On demand**: - Active