@tekyzinc/gsd-t 2.12.0 → 2.13.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 CHANGED
@@ -2,6 +2,23 @@
2
2
 
3
3
  All notable changes to GSD-T are documented here. Updated with each release.
4
4
 
5
+ ## [2.13.2] - 2026-02-12
6
+
7
+ ### Changed
8
+ - `gsd-t-init-scan-setup` now asks for project folder name, creates it if needed, and `cd`s into it — can be run from anywhere
9
+
10
+ ## [2.13.1] - 2026-02-12
11
+
12
+ ### Changed
13
+ - Update notification now includes changelog link (https://github.com/Tekyz-Inc/get-stuff-done-teams/blob/main/CHANGELOG.md)
14
+
15
+ ## [2.13.0] - 2026-02-12
16
+
17
+ ### Added
18
+ - `/user:gsd-t-init-scan-setup` slash command — full project onboarding combining git setup, init, scan, and setup in one command
19
+ - Prompts for GitHub repo URL if not already connected; skips if remote exists
20
+ - Total commands: 35 GSD-T + 3 utility = 38
21
+
5
22
  ## [2.12.0] - 2026-02-12
6
23
 
7
24
  ### 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 32 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 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.
22
22
 
23
23
  ### Start Using It
24
24
 
@@ -27,10 +27,10 @@ This installs 32 GSD-T commands + 3 utility commands to `~/.claude/commands/` an
27
27
  cd my-project
28
28
  claude
29
29
 
30
- # 2. Need help articulating your idea?
31
- /user:gsd-t-prompt
30
+ # 2. Full onboarding (git + init + scan + setup in one)
31
+ /user:gsd-t-init-scan-setup
32
32
 
33
- # 3. Initialize GSD-T
33
+ # Or step by step:
34
34
  /user:gsd-t-init my-project
35
35
 
36
36
  # 4. Define what you're building
@@ -104,6 +104,7 @@ This will replace changed command files, back up your CLAUDE.md if customized, a
104
104
  |---------|---------|
105
105
  | `/user:gsd-t-setup` | Generate or restructure project CLAUDE.md |
106
106
  | `/user:gsd-t-init` | Initialize GSD-T structure in project |
107
+ | `/user:gsd-t-init-scan-setup` | Full onboarding: git + init + scan + setup in one |
107
108
  | `/user:gsd-t-project` | Full project → milestone roadmap |
108
109
  | `/user:gsd-t-feature` | Major feature → impact analysis + milestones |
109
110
  | `/user:gsd-t-scan` | Deep codebase analysis → techdebt.md |
@@ -272,8 +273,8 @@ get-stuff-done-teams/
272
273
  ├── LICENSE
273
274
  ├── bin/
274
275
  │ └── gsd-t.js # CLI installer
275
- ├── commands/ # 35 slash commands
276
- │ ├── gsd-t-*.md # 32 GSD-T workflow commands
276
+ ├── commands/ # 38 slash commands
277
+ │ ├── gsd-t-*.md # 35 GSD-T workflow commands
277
278
  │ ├── branch.md # Git branch helper
278
279
  │ ├── checkin.md # Auto-version + commit/push helper
279
280
  │ └── Claude-md.md # Reload CLAUDE.md directives
@@ -17,6 +17,7 @@ GETTING STARTED
17
17
  brainstorm Creative exploration, rethinking, and idea generation
18
18
  setup Generate or restructure project CLAUDE.md
19
19
  init Initialize GSD-T structure in current project
20
+ init-scan-setup Full onboarding: git + init + scan + setup in one
20
21
  project New project → requirements → milestone roadmap
21
22
  feature Major feature → impact analysis → milestones
22
23
  scan Deep codebase analysis → techdebt.md
@@ -146,6 +147,13 @@ Use these when user asks for help on a specific command:
146
147
  - **Creates**: `.gsd-t/` directory structure, initial progress.md
147
148
  - **Use when**: Starting GSD-T in a new or existing project
148
149
 
150
+ ### init-scan-setup
151
+ - **Summary**: Full project onboarding — git + init + scan + setup in one command
152
+ - **Auto-invoked**: No
153
+ - **Creates**: `.gsd-t/` structure, `docs/`, `.gsd-t/scan/`, `.gsd-t/techdebt.md`, optimized `CLAUDE.md`
154
+ - **Use when**: Onboarding any project into GSD-T for the first time (new or existing codebase)
155
+ - **Combines**: gsd-t-init → gsd-t-scan → gsd-t-setup, plus git remote setup if needed
156
+
149
157
  ### project
150
158
  - **Summary**: Define a complete new project with requirements and milestone roadmap
151
159
  - **Auto-invoked**: No
@@ -0,0 +1,91 @@
1
+ # GSD-T: Init-Scan-Setup — Full Project Onboarding
2
+
3
+ One command to fully onboard a project into GSD-T. Combines project directory setup, git setup, `gsd-t-init`, `gsd-t-scan`, and `gsd-t-setup` into a single orchestrated flow.
4
+
5
+ Can be run from anywhere — does not require being in the project folder first.
6
+
7
+ ## Step 1: Project Directory
8
+
9
+ If `$ARGUMENTS` includes a folder/project name, use it. Otherwise ask: "What's the project folder name?"
10
+
11
+ 1. Check if the folder exists in the current directory
12
+ - **Exists** → `cd` into it
13
+ - **Does not exist** → Create it, then `cd` into it
14
+ 2. All subsequent steps run from inside this project directory
15
+
16
+ ## Step 2: Git Repository Check
17
+
18
+ 1. Check if the directory is inside a git repo: `git rev-parse --is-inside-work-tree`
19
+ - **Not a git repo** → Run `git init`
20
+ 2. Check for an existing remote: `git remote -v`
21
+ - **No remote found** → Ask the user for the GitHub repository URL, then run:
22
+ ```
23
+ git remote add origin {url}
24
+ ```
25
+ - **Remote exists** → Log it and continue
26
+
27
+ ## Step 3: Initialize Project (gsd-t-init)
28
+
29
+ Execute the full init workflow (same as `/user:gsd-t-init`):
30
+
31
+ 1. Create `.gsd-t/` directory structure (contracts/, domains/, progress.md, backlog.md, backlog-settings.md)
32
+ 2. Ensure `CLAUDE.md` exists (create starter if missing, append GSD-T section if present without it)
33
+ 3. Create `docs/` with all 4 living document templates (skip existing files)
34
+ 4. Ensure `README.md` exists
35
+ 5. Map existing codebase if code exists
36
+ 6. Initialize backlog with auto-derived categories
37
+ 7. Register project in `~/.claude/.gsd-t-projects`
38
+
39
+ **If `.gsd-t/` already exists**: Skip init — it's already done. Log and continue to scan.
40
+
41
+ ## Step 4: Deep Codebase Scan (gsd-t-scan)
42
+
43
+ Execute the full scan workflow (same as `/user:gsd-t-scan`):
44
+
45
+ 1. Scan across all dimensions: architecture, business rules, security, quality, contracts
46
+ 2. Build `.gsd-t/techdebt.md` register
47
+ 3. Cross-populate findings into living documents (docs/architecture.md, docs/workflows.md, docs/infrastructure.md, docs/requirements.md)
48
+ 4. Update README.md with discovered tech stack and setup info
49
+
50
+ Use team mode if agent teams are enabled. Otherwise run solo.
51
+
52
+ **If `.gsd-t/techdebt.md` already exists**: Append new findings, don't overwrite.
53
+
54
+ ## Step 5: Generate Project CLAUDE.md (gsd-t-setup)
55
+
56
+ Execute the full setup workflow (same as `/user:gsd-t-setup`):
57
+
58
+ 1. Read global `~/.claude/CLAUDE.md` to understand what's already covered
59
+ 2. Use scan findings + auto-detection to populate project-specific sections
60
+ 3. Remove any global duplicates from the project CLAUDE.md
61
+ 4. Generate and write the optimized CLAUDE.md
62
+
63
+ At Level 3: skip questions that were auto-detected — only ask what's truly unknown.
64
+ At Level 1-2: ask all targeted questions per the setup workflow.
65
+
66
+ ## Step 6: Report
67
+
68
+ Present a unified summary:
69
+
70
+ ```
71
+ Project Onboarded: {project name}
72
+
73
+ Git: {remote URL or "local only"}
74
+ Init: .gsd-t/ created, docs/ populated
75
+ Scan: {N} tech debt items ({critical} critical, {high} high, {medium} medium, {low} low)
76
+ Setup: CLAUDE.md generated ({N} sections)
77
+ Registry: {registered | already registered}
78
+
79
+ Next steps:
80
+ → Review .gsd-t/techdebt.md for critical items
81
+ → /user:gsd-t-milestone to define your first milestone
82
+ → /user:gsd-t-wave to run a full development cycle
83
+ ```
84
+
85
+ ### Autonomy Behavior
86
+
87
+ **Level 3 (Full Auto)**: Run all steps without pausing. Only stop if git remote is needed (requires user input) or if a scan reveals critical security blockers.
88
+
89
+ **Level 1-2**: Pause after each major step (init, scan, setup) for user review before continuing.
90
+
91
+ $ARGUMENTS
@@ -21,13 +21,13 @@ A methodology for reliable, parallelizable development using Claude Code with op
21
21
  cd my-project
22
22
  claude
23
23
 
24
- # 2. Need help articulating your idea?
25
- /user:gsd-t-prompt
24
+ # 2. Full onboarding (git + init + scan + setup in one)
25
+ /user:gsd-t-init-scan-setup
26
26
 
27
- # 3. Initialize GSD-T
27
+ # Or step by step:
28
28
  /user:gsd-t-init my-project
29
29
 
30
- # 4. Define what you're building
30
+ # 3. Define what you're building
31
31
  /user:gsd-t-milestone "User Authentication System"
32
32
 
33
33
  # 5. Let it rip (auto-advances through all phases)
@@ -73,6 +73,7 @@ GSD-T reads all state files and tells you exactly where you left off.
73
73
  |---------|---------|
74
74
  | `/user:gsd-t-setup` | Generate or restructure project CLAUDE.md |
75
75
  | `/user:gsd-t-init` | Initialize GSD-T structure in project |
76
+ | `/user:gsd-t-init-scan-setup` | Full onboarding: git + init + scan + setup in one |
76
77
  | `/user:gsd-t-project` | Full project → milestone roadmap |
77
78
  | `/user:gsd-t-feature` | Major feature → impact analysis + milestones |
78
79
  | `/user:gsd-t-scan` | Deep codebase analysis → techdebt.md |
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@tekyzinc/gsd-t",
3
- "version": "2.12.0",
4
- "description": "GSD-T: Contract-Driven Development for Claude Code — 37 slash commands with backlog management, impact analysis, test sync, and milestone archival",
3
+ "version": "2.13.2",
4
+ "description": "GSD-T: Contract-Driven Development for Claude Code — 38 slash commands with backlog management, impact analysis, test sync, and milestone archival",
5
5
  "author": "Tekyz, Inc.",
6
6
  "license": "MIT",
7
7
  "repository": {
@@ -36,6 +36,7 @@ PROJECT or FEATURE or SCAN
36
36
  | `/user:gsd-t-promote-debt` | Convert debt items to milestones |
37
37
  | `/user:gsd-t-setup` | Generate or restructure project CLAUDE.md |
38
38
  | `/user:gsd-t-init` | Initialize project structure |
39
+ | `/user:gsd-t-init-scan-setup` | Full onboarding: git + init + scan + setup in one |
39
40
  | `/user:gsd-t-milestone` | Define new milestone |
40
41
  | `/user:gsd-t-partition` | Decompose into domains + contracts |
41
42
  | `/user:gsd-t-discuss` | Multi-perspective design exploration |
@@ -158,6 +159,7 @@ If a `[GSD-T UPDATE]` message appears in session startup context, show it to the
158
159
  ```
159
160
  ⬆️ GSD-T update available: {installed} → {latest}
160
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
161
163
  ```
162
164
 
163
165
  ## Conversation vs. Work