@tekyzinc/gsd-t 2.15.0 → 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 +10 -0
- package/commands/gsd-t-gap-analysis.md +53 -12
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,16 @@
|
|
|
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
|
+
|
|
10
|
+
## [2.15.1] - 2026-02-13
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
- `gsd-t-gap-analysis` now uses agent team mode automatically — one teammate per requirement section for parallel scanning and classification, with solo fallback
|
|
14
|
+
|
|
5
15
|
## [2.15.0] - 2026-02-13
|
|
6
16
|
|
|
7
17
|
### Added
|
|
@@ -48,20 +48,16 @@ Review each requirement for ambiguity. If any are unclear:
|
|
|
48
48
|
Discuss now or proceed with assumptions?
|
|
49
49
|
```
|
|
50
50
|
|
|
51
|
-
## Step 4: System Scan
|
|
51
|
+
## Step 4: System Scan + Gap Classification (Team Mode)
|
|
52
52
|
|
|
53
|
-
|
|
54
|
-
- Source files relevant to each requirement
|
|
55
|
-
- Test files for coverage evidence
|
|
56
|
-
- Configuration and schema files
|
|
57
|
-
- Existing contracts in `.gsd-t/contracts/`
|
|
58
|
-
- Documentation in `docs/`
|
|
53
|
+
Automatically use agent teams to scan and classify requirements in parallel.
|
|
59
54
|
|
|
60
|
-
|
|
55
|
+
### Team Distribution Strategy
|
|
61
56
|
|
|
62
|
-
|
|
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)
|
|
63
59
|
|
|
64
|
-
|
|
60
|
+
### Classification Reference
|
|
65
61
|
|
|
66
62
|
| Status | Meaning | Action Needed |
|
|
67
63
|
|--------|---------|---------------|
|
|
@@ -70,8 +66,6 @@ For each requirement, classify with evidence:
|
|
|
70
66
|
| **Incorrect** | Code exists but doesn't match the requirement | Fix implementation |
|
|
71
67
|
| **Not Implemented** | No code exists for this requirement | Build from scratch |
|
|
72
68
|
|
|
73
|
-
Assign severity to gaps:
|
|
74
|
-
|
|
75
69
|
| Severity | Criteria |
|
|
76
70
|
|----------|----------|
|
|
77
71
|
| **Critical** | Incorrect implementation — existing code actively contradicts the requirement |
|
|
@@ -79,6 +73,53 @@ Assign severity to gaps:
|
|
|
79
73
|
| **Medium** | Not implemented — required but no code exists yet |
|
|
80
74
|
| **Low** | Not implemented — nice-to-have or can be deferred |
|
|
81
75
|
|
|
76
|
+
### Team Execution
|
|
77
|
+
|
|
78
|
+
```
|
|
79
|
+
Create an agent team for gap analysis:
|
|
80
|
+
|
|
81
|
+
ALL TEAMMATES must read before starting:
|
|
82
|
+
1. CLAUDE.md — project conventions
|
|
83
|
+
2. docs/architecture.md — system structure
|
|
84
|
+
3. docs/requirements.md — existing requirements
|
|
85
|
+
4. .gsd-t/contracts/ — domain interfaces
|
|
86
|
+
|
|
87
|
+
Classification rules:
|
|
88
|
+
- For each requirement, search the codebase for relevant code
|
|
89
|
+
- Cite specific files and line numbers as evidence
|
|
90
|
+
- Classify as: Implemented / Partial / Incorrect / Not Implemented
|
|
91
|
+
- Assign severity: Critical / High / Medium / Low
|
|
92
|
+
- Flag assumptions with [ASSUMED: {reason}]
|
|
93
|
+
|
|
94
|
+
Output format per requirement:
|
|
95
|
+
| ID | Requirement | Status | Severity | Evidence |
|
|
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)
|
|
107
|
+
|
|
108
|
+
Lead responsibilities:
|
|
109
|
+
- Distribute requirement sections to teammates
|
|
110
|
+
- Collect classification results from each teammate
|
|
111
|
+
- Resolve conflicts (two teammates found different evidence for the same code)
|
|
112
|
+
- Merge all results into the unified gap analysis document
|
|
113
|
+
- Update .gsd-t/progress.md after completion
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
### Fallback: Solo Mode
|
|
117
|
+
|
|
118
|
+
If agent teams are not available or there are fewer than 5 requirements, run sequentially:
|
|
119
|
+
- Scan the codebase for each requirement
|
|
120
|
+
- Read source files, test files, config, schema, contracts, and docs
|
|
121
|
+
- Classify each requirement with evidence
|
|
122
|
+
|
|
82
123
|
## Step 6: Generate Gap Analysis Document
|
|
83
124
|
|
|
84
125
|
Create `.gsd-t/gap-analysis.md`:
|
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",
|