@tekyzinc/gsd-t 2.20.3 → 2.20.5

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.20.5] - 2026-02-16
+
+### Added
+- **Next Command Hint**: After each GSD-T phase completes, displays the recommended next command (e.g., `Next → /user:gsd-t-partition`). Full successor mapping for all workflow commands. Skipped during auto-advancing (Level 3 mid-wave)
+
+## [2.20.4] - 2026-02-16
+
+### Changed
+- **Scan always uses team mode**: `gsd-t-scan` and `gsd-t-init-scan-setup` now spawn a team by default. Solo mode only for trivially small codebases (< 5 files) or when teams are explicitly disabled
+
 ## [2.20.3] - 2026-02-16
 
 ### Added

package/commands/gsd-t-init-scan-setup.md

@@ -58,7 +58,7 @@ Execute the full scan workflow (same as `/user:gsd-t-scan`):
 3. Cross-populate findings into living documents (docs/architecture.md, docs/workflows.md, docs/infrastructure.md, docs/requirements.md)
 4. Update README.md with discovered tech stack and setup info
 
-Use team mode if agent teams are enabled. Otherwise run solo.
+Always use team mode for the scan unless the codebase is trivially small (< 5 files) or teams are explicitly disabled.
 
 **If `.gsd-t/techdebt.md` already exists**: Append new findings, don't overwrite.
 

package/commands/gsd-t-scan.md

@@ -13,10 +13,7 @@ Read:
 
 ## Step 2: Full Codebase Scan
 
-Choose solo or team mode:
-
-### Team Mode (recommended for medium-to-large codebases)
-If agent teams are enabled, spawn a team — each dimension is fully independent:
+**Always use Team Mode** unless the codebase is trivially small (< 5 files) or agent teams are explicitly disabled. Each dimension is fully independent — parallel scanning is faster and produces better results.
 
 ```
 Create an agent team to scan this codebase:
@@ -41,7 +38,7 @@ Each teammate: write your findings to your assigned file.
 Lead: synthesize all findings into .gsd-t/techdebt.md when complete.
 ```
 
-### Solo Mode (small codebases or teams not enabled)
+### Solo Mode (fallback — only if < 5 files or teams disabled)
 Work through each dimension sequentially:
 
 Systematically analyze the entire codebase across these dimensions:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "2.20.3",
+  "version": "2.20.5",
   "description": "GSD-T: Contract-Driven Development for Claude Code — 41 slash commands with backlog management, impact analysis, test sync, and milestone archival",
   "author": "Tekyz, Inc.",
   "license": "MIT",

package/templates/CLAUDE-global.md

@@ -333,6 +333,40 @@ If in doubt, skip research and proceed — research if execution reveals gaps.
 - ALWAYS self-verify work by running verification commands
 - NEVER pause to show verification steps — execute them
 
+### Next Command Hint
+
+When a GSD-T command completes (and does NOT auto-advance to the next phase), display a hint showing the recommended next command. Format:
+
+```
+Next → /user:gsd-t-{command}
+```
+
+Successor mapping:
+| Completed | Next |
+|-----------|------|
+| `project` | `gsd-t-milestone` |
+| `feature` | `gsd-t-milestone` |
+| `milestone` | `gsd-t-partition` |
+| `partition` | `gsd-t-plan` (or `gsd-t-discuss` if complex) |
+| `discuss` | `gsd-t-plan` |
+| `plan` | `gsd-t-execute` (or `gsd-t-impact` if risky) |
+| `impact` | `gsd-t-execute` |
+| `execute` | `gsd-t-test-sync` |
+| `test-sync` | `gsd-t-verify` (or `gsd-t-integrate` if multi-domain) |
+| `integrate` | `gsd-t-verify` |
+| `verify` | `gsd-t-complete-milestone` |
+| `complete-milestone` | `gsd-t-status` |
+| `scan` | `gsd-t-promote-debt` or `gsd-t-milestone` |
+| `init` | `gsd-t-scan` or `gsd-t-milestone` |
+| `init-scan-setup` | `gsd-t-milestone` |
+| `gap-analysis` | `gsd-t-milestone` or `gsd-t-feature` |
+| `populate` | `gsd-t-status` |
+| `setup` | `gsd-t-status` |
+
+Commands with no successor (standalone): `quick`, `debug`, `brainstorm`, `status`, `help`, `resume`, `prompt`, `log`, backlog commands.
+
+Skip the hint if auto-advancing (Level 3 mid-wave) — only show when the user needs to manually invoke the next step.
+
 
 # Don't Do These Things