@tekyzinc/gsd-t 2.15.1 → 2.15.3

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [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
+- `gsd-t-gap-analysis` team mode now handles flat requirement lists — chunks into batches of ~8–10 per teammate instead of requiring sections
+
 ## [2.15.1] - 2026-02-13
 
 ### Changed

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

@@ -50,7 +50,15 @@ Discuss now or proceed with assumptions?
 
 ## Step 4: System Scan + Gap Classification (Team Mode)
 
-Automatically use agent teams to scan and classify requirements in parallel. Each teammate handles one requirement section independently.
+Automatically use agent teams to scan and classify requirements in parallel.
+
+### Team Distribution Strategy
+
+**Hard cap: maximum 4 teammates.** Distribute requirements evenly across them:
+
+- **Spec has sections**: Group adjacent sections so each teammate gets roughly equal work. (e.g., 12 sections → 4 teammates with 3 sections each)
+- **Flat list (no sections)**: Divide requirements into 4 equal batches (e.g., 30 requirements → R1–R8, R9–R15, R16–R23, R24–R30)
+- **Small spec (< 5 requirements)**: Skip teams, use solo mode
 
 ### Classification Reference
 
@@ -89,11 +97,12 @@ Classification rules:
 Output format per requirement:
   | ID | Requirement | Status | Severity | Evidence |
 
-Teammate assignments (one per requirement 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})
-  (add more teammates as needed — one per section)
+Teammate assignments (max 4 — divide requirements evenly):
+    - Teammate "analyst-1": Scan and classify R1–R{N}
+    - Teammate "analyst-2": Scan and classify R{N+1}–R{M}
+    - Teammate "analyst-3": Scan and classify R{M+1}–R{P}
+    - Teammate "analyst-4": Scan and classify R{P+1}–R{end}
+  (use fewer if < 16 requirements — 2 teammates for 5–10, 3 for 11–15, 4 for 16+)
 
 Lead responsibilities:
 - Distribute requirement sections to teammates
@@ -105,7 +114,7 @@ Lead responsibilities:
 
 ### Fallback: Solo Mode
 
-If agent teams are not available or the spec has only 1 section, run sequentially:
+If agent teams are not available or there are fewer than 5 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.1",
+  "version": "2.15.3",
   "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",