feat(agentchannel): add DependsOn to SubtaskSpec so a decomposing task can order its own subtasks

1 files changed, 8 insertions, 0 deletions

diff --git a/internal/agentchannel/agentchannel.go b/internal/agentchannel/agentchannel.go
index 202283e..98104df 100644
--- a/internal/agentchannel/agentchannel.go
+++ b/internal/agentchannel/agentchannel.go
@@ -44,6 +44,14 @@ type SubtaskSpec struct {
 	// any other role-typed task. Empty (the default) preserves the prior
 	// hardcoded "claude" behavior for backward compatibility.
 	Role string
+	// DependsOn, when non-empty, names sibling task IDs (returned by a prior
+	// SpawnSubtask call in the same decomposition) this new subtask must wait
+	// for — set directly on the created child's task.DependsOn, so the
+	// existing dispatch-gating and cascade-fail-on-dependency-failure
+	// machinery (already built for top-level tasks) applies unchanged. Empty
+	// (the default) preserves today's behavior: every spawned subtask is
+	// structurally independent/parallel.
+	DependsOn []string
 }
 
 // EpicProposal describes an epic a discovery/planner-role agent wants to