@tekyzinc/gsd-t 2.24.6 → 2.24.7

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.24.7] - 2026-02-18
+
+### Changed
+- **Next Command Hint redesigned**: Replaced plain `Next →` text with GSD-style "Next Up" visual block — divider lines, `▶ Next Up` header, phase name with description, command in backticks, and alternatives section. Format designed to trigger Claude Code's prompt suggestion engine, making the next command appear as ghost text in the user's input field
+
 ## [2.24.6] - 2026-02-18
 
 ### Added

package/package.json

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

package/templates/CLAUDE-global.md

@@ -361,33 +361,51 @@ If in doubt, skip research and proceed — research if execution reveals gaps.
 
 ### 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:
+When a GSD-T command completes (and does NOT auto-advance to the next phase), display a "Next Up" block at the very end of your response. This format is designed to trigger Claude Code's prompt suggestion engine — making the next command appear as ghost text in the user's input field.
+
+**MANDATORY format** — use this exact structure:
+
+```
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**{Phase Name}** — {one-line description of what happens next}
+
+`/user:gsd-t-{command}`
+
+───────────────────────────────────────────────────────────────
+```
+
+If there are alternative commands that also make sense, add them:
 
 ```
-Next → /user:gsd-t-{command}
+**Also available:**
+- `/user:gsd-t-{alt-1}` — {description}
+- `/user:gsd-t-{alt-2}` — {description}
 ```
 
 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` |
+| Completed | Next | Also available |
+|-----------|------|----------------|
+| `project` | `milestone` | |
+| `feature` | `milestone` | |
+| `milestone` | `partition` | |
+| `partition` | `plan` | `discuss` (if complex) |
+| `discuss` | `plan` | |
+| `plan` | `execute` | `impact` (if risky) |
+| `impact` | `execute` | |
+| `execute` | `test-sync` | |
+| `test-sync` | `verify` | `integrate` (if multi-domain) |
+| `integrate` | `verify` | |
+| `verify` | `complete-milestone` | |
+| `complete-milestone` | `status` | |
+| `scan` | `promote-debt` | `milestone` |
+| `init` | `scan` | `milestone` |
+| `init-scan-setup` | `milestone` | |
+| `gap-analysis` | `milestone` | `feature` |
+| `populate` | `status` | |
+| `setup` | `status` | |
 
 Commands with no successor (standalone): `quick`, `debug`, `brainstorm`, `status`, `help`, `resume`, `prompt`, `log`, backlog commands.