@tekyzinc/gsd-t 2.15.1 → 2.15.2
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 +5 -0
- package/commands/gsd-t-gap-analysis.md +17 -7
- package/package.json +1 -1
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.2] - 2026-02-13
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
- `gsd-t-gap-analysis` team mode now handles flat requirement lists — chunks into batches of ~8–10 per teammate instead of requiring sections
|
|
9
|
+
|
|
5
10
|
## [2.15.1] - 2026-02-13
|
|
6
11
|
|
|
7
12
|
### Changed
|
|
@@ -50,7 +50,12 @@ Discuss now or proceed with assumptions?
|
|
|
50
50
|
|
|
51
51
|
## Step 4: System Scan + Gap Classification (Team Mode)
|
|
52
52
|
|
|
53
|
-
Automatically use agent teams to scan and classify requirements in parallel.
|
|
53
|
+
Automatically use agent teams to scan and classify requirements in parallel.
|
|
54
|
+
|
|
55
|
+
### Team Distribution Strategy
|
|
56
|
+
|
|
57
|
+
- **Spec has sections**: One teammate per section
|
|
58
|
+
- **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)
|
|
54
59
|
|
|
55
60
|
### Classification Reference
|
|
56
61
|
|
|
@@ -89,11 +94,16 @@ Classification rules:
|
|
|
89
94
|
Output format per requirement:
|
|
90
95
|
| ID | Requirement | Status | Severity | Evidence |
|
|
91
96
|
|
|
92
|
-
Teammate assignments
|
|
93
|
-
|
|
94
|
-
- Teammate "section-
|
|
95
|
-
- Teammate "section-
|
|
96
|
-
|
|
97
|
+
Teammate assignments:
|
|
98
|
+
If spec has sections — one teammate per section:
|
|
99
|
+
- Teammate "section-1": Scan and classify {Section 1} (R1–R{N})
|
|
100
|
+
- Teammate "section-2": Scan and classify {Section 2} (R{N+1}–R{M})
|
|
101
|
+
- Teammate "section-3": Scan and classify {Section 3} (R{M+1}–R{P})
|
|
102
|
+
If flat list — chunk into batches of ~8–10:
|
|
103
|
+
- Teammate "batch-1": Scan and classify R1–R10
|
|
104
|
+
- Teammate "batch-2": Scan and classify R11–R20
|
|
105
|
+
- Teammate "batch-3": Scan and classify R21–R30
|
|
106
|
+
(scale teammates to match — aim for 3–5 teammates max)
|
|
97
107
|
|
|
98
108
|
Lead responsibilities:
|
|
99
109
|
- Distribute requirement sections to teammates
|
|
@@ -105,7 +115,7 @@ Lead responsibilities:
|
|
|
105
115
|
|
|
106
116
|
### Fallback: Solo Mode
|
|
107
117
|
|
|
108
|
-
If agent teams are not available or
|
|
118
|
+
If agent teams are not available or there are fewer than 5 requirements, run sequentially:
|
|
109
119
|
- Scan the codebase for each requirement
|
|
110
120
|
- Read source files, test files, config, schema, contracts, and docs
|
|
111
121
|
- 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
|
+
"version": "2.15.2",
|
|
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",
|