From e59d2975b81731fd0df9a3eb7450cd37142569bd Mon Sep 17 00:00:00 2001
From: Stable Genius <259448942+stablegenius49@users.noreply.github.com>
Date: Thu, 5 Mar 2026 23:26:29 -0800
Subject: [PATCH] Clarify SDD must avoid background subagent dispatch

---
 skills/subagent-driven-development/SKILL.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/skills/subagent-driven-development/SKILL.md b/skills/subagent-driven-development/SKILL.md
index b578dfa48..9cd363d23 100644
--- a/skills/subagent-driven-development/SKILL.md
+++ b/skills/subagent-driven-development/SKILL.md
@@ -7,7 +7,7 @@ description: Use when executing implementation plans with independent tasks in t
 
 Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
 
-**Core principle:** Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
+**Core principle:** Fresh subagent per task + strictly sequential dispatch (no background tasks) + two-stage review (spec then quality) = high quality, fast iteration
 
 ## When to Use
 
@@ -202,7 +202,9 @@ Done!
 - Start implementation on main/master branch without explicit user consent
 - Skip reviews (spec compliance OR code quality)
 - Proceed with unfixed issues
-- Dispatch multiple implementation subagents in parallel (conflicts)
+- Dispatch any implementation subagent with `run_in_background: true` or retrieve results via `TaskOutput`
+  - Keep implementation dispatch strictly synchronous (one task at a time)
+  - Rationale: background retrieval can return truncated transcript fragments and break review gates
 - Make subagent read plan file (provide full text instead)
 - Skip scene-setting context (subagent needs to understand where task fits)
 - Ignore subagent questions (answer before letting them proceed)