subagent-execute-planlisted

# Subagent-Execute-Plan (Coordinator) > Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference. This skill is a **coordinator only**. It holds plan state, builds an execution schedule, and dispatches subagents. It never edits files, never runs tests, never reads source code. Subagents do all work. **Why coordinator-only:** isolated context per subagent → no pollution. The coordinator's context stays small (plan, TaskList, last subagent return) so it can run a long plan without hitting its own context limit. Subagents do the heavy lifting and discard their context when they return. **Core loop:** ``` plan → explorer (group disjoint tasks) → for each group: pick execution strategy (subagents | workflow) → ← Step 3a-S ┌─ subagents: parallel background implementers ───┐ └─ workflow: one Workflow script over the wave ──┘ → decide: tests/lints worth running now? → if yes → test-runner / static-analyse subagents → if findings → SendMessage original implementer OR spawn bdk:fixer → commit group → next group ``` **Two execution paths per group.** A group is dispatched either as **hand-orchestrated background subagents** (the default — full SendMessage/re-dispatch control per task) or as a **single Workflow** that fans out over the wave deterministically (cheaper coordinator context, better for large disjoint mechanical waves). The coordinator chooses per group — see Step 3a-S. The Workflow path reuses the **same bd