@tekyzinc/gsd-t 2.13.1 → 2.13.3

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.13.3] - 2026-02-12
+
+### Changed
+- `gsd-t-init-scan-setup` now asks "Is {current folder} your project root?" before prompting for a folder name
+
+## [2.13.2] - 2026-02-12
+
+### Changed
+- `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
+
 ## [2.13.1] - 2026-02-12
 
 ### Changed

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

@@ -1,10 +1,26 @@
 # GSD-T: Init-Scan-Setup — Full Project Onboarding
 
-One command to fully onboard a project into GSD-T. Combines git setup, `gsd-t-init`, `gsd-t-scan`, and `gsd-t-setup` into a single orchestrated flow.
+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.
 
-## Step 1: Git Repository Check
+Can be run from anywhere — does not require being in the project folder first.
 
-1. Check if the current directory is inside a git repo: `git rev-parse --is-inside-work-tree`
+## Step 1: Project Directory
+
+First, ask: **"Is `{current directory name}` your project root folder?"**
+
+- **Yes** → Stay here and continue to Step 2
+- **No** → Ask: "What's the project folder name?" (or use `$ARGUMENTS` if provided)
+  1. Check if the folder exists in the current directory
+     - **Exists** → `cd` into it
+     - **Does not exist** → Create it, then `cd` into it
+
+If `$ARGUMENTS` includes a folder/project name, skip the question and use it directly.
+
+All subsequent steps run from inside the project directory.
+
+## Step 2: Git Repository Check
+
+1. Check if the directory is inside a git repo: `git rev-parse --is-inside-work-tree`
    - **Not a git repo** → Run `git init`
 2. Check for an existing remote: `git remote -v`
    - **No remote found** → Ask the user for the GitHub repository URL, then run:
@@ -13,7 +29,7 @@ One command to fully onboard a project into GSD-T. Combines git setup, `gsd-t-in
      ```
    - **Remote exists** → Log it and continue
 
-## Step 2: Initialize Project (gsd-t-init)
+## Step 3: Initialize Project (gsd-t-init)
 
 Execute the full init workflow (same as `/user:gsd-t-init`):
 
@@ -27,7 +43,7 @@ Execute the full init workflow (same as `/user:gsd-t-init`):
 
 **If `.gsd-t/` already exists**: Skip init — it's already done. Log and continue to scan.
 
-## Step 3: Deep Codebase Scan (gsd-t-scan)
+## Step 4: Deep Codebase Scan (gsd-t-scan)
 
 Execute the full scan workflow (same as `/user:gsd-t-scan`):
 
@@ -40,7 +56,7 @@ Use team mode if agent teams are enabled. Otherwise run solo.
 
 **If `.gsd-t/techdebt.md` already exists**: Append new findings, don't overwrite.
 
-## Step 4: Generate Project CLAUDE.md (gsd-t-setup)
+## Step 5: Generate Project CLAUDE.md (gsd-t-setup)
 
 Execute the full setup workflow (same as `/user:gsd-t-setup`):
 
@@ -52,7 +68,7 @@ Execute the full setup workflow (same as `/user:gsd-t-setup`):
 At Level 3: skip questions that were auto-detected — only ask what's truly unknown.
 At Level 1-2: ask all targeted questions per the setup workflow.
 
-## Step 5: Report
+## Step 6: Report
 
 Present a unified summary:
 

package/package.json

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