@tekyzinc/gsd-t 2.14.0 → 2.14.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 +11 -0
- package/commands/gsd-t.md +3 -3
- package/package.json +1 -1
- package/templates/CLAUDE-global.md +14 -7
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,17 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to GSD-T are documented here. Updated with each release.
|
|
4
4
|
|
|
5
|
+
## [2.14.2] - 2026-02-13
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
- Smart router (`/gsd-t`) now displays selected command as the first line of output (mandatory routing confirmation)
|
|
9
|
+
|
|
10
|
+
## [2.14.1] - 2026-02-13
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
- Update Notices section in CLAUDE-global template now handles both `[GSD-T UPDATE]` (update available) and `[GSD-T]` (up to date) version banners
|
|
14
|
+
- Update command in notification changed from raw npm command to `/user:gsd-t-version-update-all`
|
|
15
|
+
|
|
5
16
|
## [2.14.0] - 2026-02-12
|
|
6
17
|
|
|
7
18
|
### Added
|
package/commands/gsd-t.md
CHANGED
|
@@ -38,13 +38,13 @@ From `$ARGUMENTS`, classify the request into one of these categories:
|
|
|
38
38
|
|
|
39
39
|
## Step 3: Confirm and Execute
|
|
40
40
|
|
|
41
|
-
|
|
41
|
+
**MANDATORY — before doing anything else, output this line FIRST:**
|
|
42
42
|
|
|
43
43
|
```
|
|
44
|
-
→ Routing to gsd-t-{command}: {brief reason}
|
|
44
|
+
→ Routing to /user:gsd-t-{command}: {brief reason}
|
|
45
45
|
```
|
|
46
46
|
|
|
47
|
-
Then immediately execute that command's full workflow, passing `$ARGUMENTS` through.
|
|
47
|
+
This MUST be the very first line of your response so the user sees which command was selected. Then immediately execute that command's full workflow, passing `$ARGUMENTS` through.
|
|
48
48
|
|
|
49
49
|
**Do NOT ask "is this the right command?" — just route and go.** The user can interrupt with Esc if it's wrong.
|
|
50
50
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tekyzinc/gsd-t",
|
|
3
|
-
"version": "2.14.
|
|
3
|
+
"version": "2.14.2",
|
|
4
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",
|
|
@@ -155,13 +155,20 @@ Even in development, the user may have:
|
|
|
155
155
|
|
|
156
156
|
## Update Notices
|
|
157
157
|
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
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:
|
|
159
|
+
|
|
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
|
+
```
|
|
165
172
|
|
|
166
173
|
## Conversation vs. Work
|
|
167
174
|
|