@tekyzinc/gsd-t 2.15.2 → 2.15.4

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.15.4] - 2026-02-13
+
+### Changed
+- `gsd-t-gap-analysis` team scaling: one teammate per requirement (3–10), cap at 10 with even batching for 11+, solo for 1–2
+
+## [2.15.3] - 2026-02-13
+
+### Fixed
+- `gsd-t-gap-analysis` hard cap of 4 teammates max — scales by requirement count (2 for 5–10, 3 for 11–15, 4 for 16+), solo for < 5
+
 ## [2.15.2] - 2026-02-13
 
 ### Changed

package/commands/gsd-t-gap-analysis.md

@@ -54,8 +54,11 @@ Automatically use agent teams to scan and classify requirements in parallel.
 
 ### Team Distribution Strategy
 
-- **Spec has sections**: One teammate per section
-- **Flat list (no sections)**: Chunk requirements into batches of ~8–10 and assign one teammate per batch (e.g., 30 requirements → 3 teammates handling R1–R10, R11–R20, R21–R30)
+**One teammate per requirement, cap at 10.** Maximize parallelism:
+
+- **1–2 requirements**: Solo mode (team overhead not worth it)
+- **3–10 requirements**: One teammate per requirement (e.g., 4 requirements → 4 teammates)
+- **11+ requirements**: Cap at 10 teammates, divide requirements evenly (e.g., 30 requirements → 10 teammates with 3 each)
 
 ### Classification Reference
 
@@ -94,16 +97,17 @@ Classification rules:
 Output format per requirement:
   | ID | Requirement | Status | Severity | Evidence |
 
-Teammate assignments:
-  If spec has sections — one teammate per section:
-    - Teammate "section-1": Scan and classify {Section 1} (R1–R{N})
-    - Teammate "section-2": Scan and classify {Section 2} (R{N+1}–R{M})
-    - Teammate "section-3": Scan and classify {Section 3} (R{M+1}–R{P})
-  If flat list — chunk into batches of ~8–10:
-    - Teammate "batch-1": Scan and classify R1–R10
-    - Teammate "batch-2": Scan and classify R11–R20
-    - Teammate "batch-3": Scan and classify R21–R30
-  (scale teammates to match — aim for 3–5 teammates max)
+Teammate assignments (one per requirement, cap at 10):
+  For 3–10 requirements — one teammate each:
+    - Teammate "analyst-1": Scan and classify R1
+    - Teammate "analyst-2": Scan and classify R2
+    - ...
+    - Teammate "analyst-{N}": Scan and classify R{N}
+  For 11+ requirements — divide evenly across 10 teammates:
+    - Teammate "analyst-1": Scan and classify R1–R{batch}
+    - Teammate "analyst-2": Scan and classify R{batch+1}–R{2*batch}
+    - ...
+    - Teammate "analyst-10": Scan and classify R{...}–R{end}
 
 Lead responsibilities:
 - Distribute requirement sections to teammates
@@ -115,7 +119,7 @@ Lead responsibilities:
 
 ### Fallback: Solo Mode
 
-If agent teams are not available or there are fewer than 5 requirements, run sequentially:
+If agent teams are not available or there are fewer than 3 requirements, run sequentially:
 - Scan the codebase for each requirement
 - Read source files, test files, config, schema, contracts, and docs
 - Classify each requirement with evidence

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "2.15.2",
+  "version": "2.15.4",
   "description": "GSD-T: Contract-Driven Development for Claude Code — 40 slash commands with backlog management, impact analysis, test sync, and milestone archival",
   "author": "Tekyz, Inc.",
   "license": "MIT",