@tekyzinc/gsd-t 2.15.3 → 2.15.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,11 @@
2
2
 
3
3
  All notable changes to GSD-T are documented here. Updated with each release.
4
4
 
5
+ ## [2.15.4] - 2026-02-13
6
+
7
+ ### Changed
8
+ - `gsd-t-gap-analysis` team scaling: one teammate per requirement (3–10), cap at 10 with even batching for 11+, solo for 1–2
9
+
5
10
  ## [2.15.3] - 2026-02-13
6
11
 
7
12
  ### Fixed
@@ -54,11 +54,11 @@ Automatically use agent teams to scan and classify requirements in parallel.
54
54
 
55
55
  ### Team Distribution Strategy
56
56
 
57
- **Hard cap: maximum 4 teammates.** Distribute requirements evenly across them:
57
+ **One teammate per requirement, cap at 10.** Maximize parallelism:
58
58
 
59
- - **Spec has sections**: Group adjacent sections so each teammate gets roughly equal work. (e.g., 12 sections 4 teammates with 3 sections each)
60
- - **Flat list (no sections)**: Divide requirements into 4 equal batches (e.g., 30 requirements → R1–R8, R9–R15, R16–R23, R24–R30)
61
- - **Small spec (< 5 requirements)**: Skip teams, use solo mode
59
+ - **1–2 requirements**: Solo mode (team overhead not worth it)
60
+ - **3–10 requirements**: One teammate per requirement (e.g., 4 requirements → 4 teammates)
61
+ - **11+ requirements**: Cap at 10 teammates, divide requirements evenly (e.g., 30 requirements 10 teammates with 3 each)
62
62
 
63
63
  ### Classification Reference
64
64
 
@@ -97,12 +97,17 @@ Classification rules:
97
97
  Output format per requirement:
98
98
  | ID | Requirement | Status | Severity | Evidence |
99
99
 
100
- Teammate assignments (max 4 divide requirements evenly):
101
- - Teammate "analyst-1": Scan and classify R1–R{N}
102
- - Teammate "analyst-2": Scan and classify R{N+1}–R{M}
103
- - Teammate "analyst-3": Scan and classify R{M+1}–R{P}
104
- - Teammate "analyst-4": Scan and classify R{P+1}–R{end}
105
- (use fewer if < 16 requirements — 2 teammates for 5–10, 3 for 11–15, 4 for 16+)
100
+ Teammate assignments (one per requirement, cap at 10):
101
+ For 3–10 requirements one teammate each:
102
+ - Teammate "analyst-1": Scan and classify R1
103
+ - Teammate "analyst-2": Scan and classify R2
104
+ - ...
105
+ - Teammate "analyst-{N}": Scan and classify R{N}
106
+ For 11+ requirements — divide evenly across 10 teammates:
107
+ - Teammate "analyst-1": Scan and classify R1–R{batch}
108
+ - Teammate "analyst-2": Scan and classify R{batch+1}–R{2*batch}
109
+ - ...
110
+ - Teammate "analyst-10": Scan and classify R{...}–R{end}
106
111
 
107
112
  Lead responsibilities:
108
113
  - Distribute requirement sections to teammates
@@ -114,7 +119,7 @@ Lead responsibilities:
114
119
 
115
120
  ### Fallback: Solo Mode
116
121
 
117
- If agent teams are not available or there are fewer than 5 requirements, run sequentially:
122
+ If agent teams are not available or there are fewer than 3 requirements, run sequentially:
118
123
  - Scan the codebase for each requirement
119
124
  - Read source files, test files, config, schema, contracts, and docs
120
125
  - Classify each requirement with evidence
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tekyzinc/gsd-t",
3
- "version": "2.15.3",
3
+ "version": "2.15.4",
4
4
  "description": "GSD-T: Contract-Driven Development for Claude Code — 40 slash commands with backlog management, impact analysis, test sync, and milestone archival",
5
5
  "author": "Tekyz, Inc.",
6
6
  "license": "MIT",