@tekyzinc/gsd-t 2.13.4 → 2.14.1

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 CHANGED
@@ -2,6 +2,19 @@
2
2
 
3
3
  All notable changes to GSD-T are documented here. Updated with each release.
4
4
 
5
+ ## [2.14.1] - 2026-02-13
6
+
7
+ ### Changed
8
+ - Update Notices section in CLAUDE-global template now handles both `[GSD-T UPDATE]` (update available) and `[GSD-T]` (up to date) version banners
9
+ - Update command in notification changed from raw npm command to `/user:gsd-t-version-update-all`
10
+
11
+ ## [2.14.0] - 2026-02-12
12
+
13
+ ### Added
14
+ - `/user:gsd-t` smart router command — describe what you need in plain language, auto-routes to the correct GSD-T command
15
+ - Intent classification routes to: quick, feature, project, debug, scan, brainstorm, milestone, wave, status, resume, backlog-add, and more
16
+ - Total commands: 36 GSD-T + 3 utility = 39
17
+
5
18
  ## [2.13.4] - 2026-02-12
6
19
 
7
20
  ### Added
package/README.md CHANGED
@@ -18,7 +18,7 @@ A methodology for reliable, parallelizable development using Claude Code with op
18
18
  npx @tekyzinc/gsd-t install
19
19
  ```
20
20
 
21
- This installs 35 GSD-T commands + 3 utility commands to `~/.claude/commands/` and the global CLAUDE.md to `~/.claude/CLAUDE.md`. Works on Windows, Mac, and Linux.
21
+ This installs 36 GSD-T commands + 3 utility commands to `~/.claude/commands/` and the global CLAUDE.md to `~/.claude/CLAUDE.md`. Works on Windows, Mac, and Linux.
22
22
 
23
23
  ### Start Using It
24
24
 
@@ -89,6 +89,12 @@ This will replace changed command files, back up your CLAUDE.md if customized, a
89
89
 
90
90
  ## Commands Reference
91
91
 
92
+ ### Smart Router
93
+
94
+ | Command | Purpose | Auto |
95
+ |---------|---------|------|
96
+ | `/user:gsd-t {request}` | Describe what you need → auto-routes to the right command | Manual |
97
+
92
98
  ### Help & Onboarding
93
99
 
94
100
  | Command | Purpose | Auto |
@@ -273,8 +279,8 @@ get-stuff-done-teams/
273
279
  ├── LICENSE
274
280
  ├── bin/
275
281
  │ └── gsd-t.js # CLI installer
276
- ├── commands/ # 38 slash commands
277
- │ ├── gsd-t-*.md # 35 GSD-T workflow commands
282
+ ├── commands/ # 39 slash commands
283
+ │ ├── gsd-t-*.md # 36 GSD-T workflow commands
278
284
  │ ├── branch.md # Git branch helper
279
285
  │ ├── checkin.md # Auto-version + commit/push helper
280
286
  │ └── Claude-md.md # Reload CLAUDE.md directives
@@ -11,6 +11,10 @@ Display the full command reference:
11
11
  ║ GSD-T Command Reference ║
12
12
  ╚══════════════════════════════════════════════════════════════════════════════╝
13
13
 
14
+ SMART ROUTER Manual
15
+ ───────────────────────────────────────────────────────────────────────────────
16
+ gsd-t Describe what you need → auto-routes to the right command
17
+
14
18
  GETTING STARTED Manual
15
19
  ───────────────────────────────────────────────────────────────────────────────
16
20
  prompt Help formulate your idea before committing to a command
@@ -122,6 +126,13 @@ RELATED COMMANDS
122
126
 
123
127
  Use these when user asks for help on a specific command:
124
128
 
129
+ ### gsd-t (smart router)
130
+ - **Summary**: Describe what you need in plain language — auto-routes to the right GSD-T command
131
+ - **Auto-invoked**: No
132
+ - **Files**: Reads `CLAUDE.md`, `.gsd-t/progress.md`
133
+ - **Use when**: You don't want to remember which command to use — just describe what you want
134
+ - **Examples**: `/user:gsd-t Fix the login bug`, `/user:gsd-t Add dark mode`, `/user:gsd-t Scan for tech debt`
135
+
125
136
  ### prompt
126
137
  - **Summary**: Help formulate project/feature/milestone prompts through guided questions
127
138
  - **Auto-invoked**: No
@@ -0,0 +1,67 @@
1
+ # GSD-T: Smart Router — Tell GSD-T What You Need
2
+
3
+ You are the GSD-T smart router. The user describes what they want in plain language and you route to the correct GSD-T command automatically.
4
+
5
+ ## Step 1: Load Context
6
+
7
+ Read (if they exist):
8
+ 1. `CLAUDE.md` — project context
9
+ 2. `.gsd-t/progress.md` — current state, active milestone/phase
10
+
11
+ ## Step 2: Analyze Intent
12
+
13
+ From `$ARGUMENTS`, classify the request into one of these categories:
14
+
15
+ | Intent | Route To | Signal Words |
16
+ |--------|----------|--------------|
17
+ | Small fix, tweak, config change, minor addition | `gsd-t-quick` | "fix", "change", "update", "tweak", "add {small thing}", "rename", "move" |
18
+ | Major new feature or capability | `gsd-t-feature` | "add {large feature}", "implement", "build {system}", "create {module}" |
19
+ | Full new project from scratch | `gsd-t-project` | "new project", "start building", "create {app/product}" |
20
+ | Full project onboarding | `gsd-t-init-scan-setup` | "onboard", "set up GSD-T", "initialize" |
21
+ | Define a deliverable chunk | `gsd-t-milestone` | "milestone", "next deliverable", "define {goal}" |
22
+ | Run full cycle on current milestone | `gsd-t-wave` | "run it", "execute", "let it rip", "full cycle", "wave" |
23
+ | Debug or investigate a problem | `gsd-t-debug` | "bug", "broken", "not working", "error", "investigate", "why does" |
24
+ | Understand or audit codebase | `gsd-t-scan` | "audit", "analyze", "scan", "tech debt", "what's wrong with" |
25
+ | Explore ideas or rethink approach | `gsd-t-brainstorm` | "brainstorm", "what if", "explore", "rethink", "ideas for" |
26
+ | Help articulate a vague idea | `gsd-t-prompt` | "I want to", "how should I", "help me think about" |
27
+ | Generate or fix project CLAUDE.md | `gsd-t-setup` | "setup CLAUDE.md", "restructure CLAUDE.md" |
28
+ | Check current progress | `gsd-t-status` | "status", "where are we", "progress", "what's done" |
29
+ | Resume interrupted work | `gsd-t-resume` | "resume", "continue", "pick up where" |
30
+ | Capture something for later | `gsd-t-backlog-add` | "add to backlog", "save for later", "remember to", "todo" |
31
+ | Promote tech debt to milestone | `gsd-t-promote-debt` | "promote debt", "fix tech debt" |
32
+ | Auto-populate docs | `gsd-t-populate` | "populate docs", "fill in docs", "document the codebase" |
33
+
34
+ ### Ambiguous cases:
35
+ - If the request could be `quick` or `feature`, check scope: does it touch 1-2 files (quick) or require multiple domains/files (feature)?
36
+ - If a milestone is active mid-phase, consider whether the request fits within the current work or is a new task
37
+ - If truly ambiguous, ask one clarifying question — don't guess
38
+
39
+ ## Step 3: Confirm and Execute
40
+
41
+ Show a brief one-line confirmation, then execute:
42
+
43
+ ```
44
+ → Routing to gsd-t-{command}: {brief reason}
45
+ ```
46
+
47
+ Then immediately execute that command's full workflow, passing `$ARGUMENTS` through.
48
+
49
+ **Do NOT ask "is this the right command?" — just route and go.** The user can interrupt with Esc if it's wrong.
50
+
51
+ ## Step 4: No Arguments
52
+
53
+ If called with no arguments, show:
54
+
55
+ ```
56
+ Usage: /user:gsd-t {describe what you want}
57
+
58
+ Examples:
59
+ /user:gsd-t Fix the login timeout bug
60
+ /user:gsd-t Add dark mode support
61
+ /user:gsd-t Scan the codebase for tech debt
62
+ /user:gsd-t What's the current progress?
63
+
64
+ I'll route to the right GSD-T command automatically.
65
+ ```
66
+
67
+ $ARGUMENTS
@@ -58,6 +58,12 @@ GSD-T reads all state files and tells you exactly where you left off.
58
58
 
59
59
  ## Commands Reference
60
60
 
61
+ ### Smart Router
62
+
63
+ | Command | Purpose | Auto |
64
+ |---------|---------|------|
65
+ | `/user:gsd-t {request}` | Describe what you need → auto-routes to the right command | Manual |
66
+
61
67
  ### Help & Onboarding
62
68
 
63
69
  | Command | Purpose | Auto |
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@tekyzinc/gsd-t",
3
- "version": "2.13.4",
4
- "description": "GSD-T: Contract-Driven Development for Claude Code — 38 slash commands with backlog management, impact analysis, test sync, and milestone archival",
3
+ "version": "2.14.1",
4
+ "description": "GSD-T: Contract-Driven Development for Claude Code — 39 slash commands with backlog management, impact analysis, test sync, and milestone archival",
5
5
  "author": "Tekyz, Inc.",
6
6
  "license": "MIT",
7
7
  "repository": {
@@ -27,6 +27,7 @@ PROJECT or FEATURE or SCAN
27
27
 
28
28
  | Command | Purpose |
29
29
  |---------|---------|
30
+ | `/user:gsd-t` | Smart router — describe what you need, auto-routes to the right command |
30
31
  | `/user:gsd-t-help` | List all commands or get detailed help |
31
32
  | `/user:gsd-t-prompt` | Help formulate your idea before committing |
32
33
  | `/user:gsd-t-brainstorm` | Creative exploration and idea generation |
@@ -154,13 +155,20 @@ Even in development, the user may have:
154
155
 
155
156
  ## Update Notices
156
157
 
157
- If a `[GSD-T UPDATE]` message appears in session startup context, show it to the user at the **beginning AND end** of your first response. Format it as:
158
+ On session start, a version check hook outputs one of two messages. Show the result to the user at the **beginning** of your first response:
158
159
 
159
- ```
160
- ⬆️ GSD-T update available: {installed} → {latest}
161
- Run: npm update -g @tekyzinc/gsd-t && gsd-t update-all
162
- Changelog: https://github.com/Tekyz-Inc/get-stuff-done-teams/blob/main/CHANGELOG.md
163
- ```
160
+ - If `[GSD-T UPDATE]` appears → update is available. Show:
161
+ ```
162
+ ⬆️ GSD-T update available: {installed} {latest}
163
+ Run: /user:gsd-t-version-update-all
164
+ Changelog: https://github.com/Tekyz-Inc/get-stuff-done-teams/blob/main/CHANGELOG.md
165
+ ```
166
+ Also repeat at the **end** of your first response.
167
+
168
+ - If `[GSD-T]` appears → up to date. Show:
169
+ ```
170
+ GSD-T v{version} — up to date
171
+ ```
164
172
 
165
173
  ## Conversation vs. Work
166
174