@tekyzinc/gsd-t 2.15.0 → 2.15.1

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.15.1] - 2026-02-13
+
+### Changed
+- `gsd-t-gap-analysis` now uses agent team mode automatically — one teammate per requirement section for parallel scanning and classification, with solo fallback
+
 ## [2.15.0] - 2026-02-13
 
 ### Added

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

@@ -48,20 +48,11 @@ Review each requirement for ambiguity. If any are unclear:
 Discuss now or proceed with assumptions?
 ```
 
-## Step 4: System Scan
+## Step 4: System Scan + Gap Classification (Team Mode)
 
-Scan the existing codebase to understand current state. Read:
-- Source files relevant to each requirement
-- Test files for coverage evidence
-- Configuration and schema files
-- Existing contracts in `.gsd-t/contracts/`
-- Documentation in `docs/`
+Automatically use agent teams to scan and classify requirements in parallel. Each teammate handles one requirement section independently.
 
-Build an understanding of what exists before classifying.
-
-## Step 5: Gap Classification
-
-For each requirement, classify with evidence:
+### Classification Reference
 
 | Status | Meaning | Action Needed |
 |--------|---------|---------------|
@@ -70,8 +61,6 @@ For each requirement, classify with evidence:
 | **Incorrect** | Code exists but doesn't match the requirement | Fix implementation |
 | **Not Implemented** | No code exists for this requirement | Build from scratch |
 
-Assign severity to gaps:
-
 | Severity | Criteria |
 |----------|----------|
 | **Critical** | Incorrect implementation — existing code actively contradicts the requirement |
@@ -79,6 +68,48 @@ Assign severity to gaps:
 | **Medium** | Not implemented — required but no code exists yet |
 | **Low** | Not implemented — nice-to-have or can be deferred |
 
+### Team Execution
+
+```
+Create an agent team for gap analysis:
+
+ALL TEAMMATES must read before starting:
+  1. CLAUDE.md — project conventions
+  2. docs/architecture.md — system structure
+  3. docs/requirements.md — existing requirements
+  4. .gsd-t/contracts/ — domain interfaces
+
+Classification rules:
+  - For each requirement, search the codebase for relevant code
+  - Cite specific files and line numbers as evidence
+  - Classify as: Implemented / Partial / Incorrect / Not Implemented
+  - Assign severity: Critical / High / Medium / Low
+  - Flag assumptions with [ASSUMED: {reason}]
+
+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)
+
+Lead responsibilities:
+- Distribute requirement sections to teammates
+- Collect classification results from each teammate
+- Resolve conflicts (two teammates found different evidence for the same code)
+- Merge all results into the unified gap analysis document
+- Update .gsd-t/progress.md after completion
+```
+
+### Fallback: Solo Mode
+
+If agent teams are not available or the spec has only 1 section, run sequentially:
+- Scan the codebase for each requirement
+- Read source files, test files, config, schema, contracts, and docs
+- Classify each requirement with evidence
+
 ## Step 6: Generate Gap Analysis Document
 
 Create `.gsd-t/gap-analysis.md`:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "2.15.0",
+  "version": "2.15.1",
   "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",