From 22ae8ed516027dbc0e8d68b010c09ac780bc4ce1 Mon Sep 17 00:00:00 2001 From: Bryan Ramos Date: Wed, 1 Apr 2026 17:07:44 -0400 Subject: [PATCH] fix: enforce parallel researcher dispatch in orchestrate skill --- skills/orchestrate/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/orchestrate/SKILL.md b/skills/orchestrate/SKILL.md index 253327a..58628ea 100644 --- a/skills/orchestrate/SKILL.md +++ b/skills/orchestrate/SKILL.md @@ -71,7 +71,7 @@ Spawn `requirements-analyst` with the raw user request. It returns: restated pro If the requirements-analyst returns no research questions, skip Phase 2. **Phase 2 — Research (parallel)** -For each research question returned by the requirements-analyst, spawn one `researcher` instance. Spawn all instances in the same response — they run in parallel. +For each research question returned by the requirements-analyst, spawn one `researcher` instance. **All researchers must be spawned in a single response — dispatching them sequentially serializes the pipeline and defeats the purpose of parallel research.** Each researcher receives: - The specific research question (topic + why needed + where to look)