@tekyzinc/gsd-t 3.12.12 → 3.12.13

package/bin/gsd-t.js

@@ -1294,9 +1294,9 @@ function showInstallSummary(gsdtCount, utilCount) {
   log(`${BOLD}Quick Start:${RESET}`);
   log(`  ${DIM}$${RESET} cd your-project`);
   log(`  ${DIM}$${RESET} claude`);
-  log(`  ${DIM}>${RESET} /user:gsd-t-init my-project`);
-  log(`  ${DIM}>${RESET} /user:gsd-t-milestone "First Feature"`);
-  log(`  ${DIM}>${RESET} /user:gsd-t-wave`);
+  log(`  ${DIM}>${RESET} /gsd-t-init my-project`);
+  log(`  ${DIM}>${RESET} /gsd-t-milestone "First Feature"`);
+  log(`  ${DIM}>${RESET} /gsd-t-wave`);
   log("");
   log(`${BOLD}Other commands:${RESET}`);
   log(`  ${DIM}$${RESET} npx @tekyzinc/gsd-t status      ${DIM}— check installation${RESET}`);
@@ -1344,7 +1344,7 @@ function initClaudeMd(projectDir, projectName, today) {
         info("CLAUDE.md already contains GSD-T section — skipping");
       } else {
         warn("CLAUDE.md exists but doesn't reference GSD-T");
-        info("Run /user:gsd-t-init inside Claude Code to add GSD-T section");
+        info("Run /gsd-t-init inside Claude Code to add GSD-T section");
       }
     } else { throw e; }
   }
@@ -1513,8 +1513,8 @@ function showInitTree(projectDir) {
   log(`${BOLD}Next steps:${RESET}`);
   log(`  1. Edit CLAUDE.md — add project overview and tech stack`);
   log(`  2. Start Claude Code: ${DIM}claude${RESET}`);
-  log(`  3. Run: ${DIM}/user:gsd-t-populate${RESET}  ${DIM}(if existing codebase)${RESET}`);
-  log(`     Or:  ${DIM}/user:gsd-t-project${RESET}   ${DIM}(if new project)${RESET}`);
+  log(`  3. Run: ${DIM}/gsd-t-populate${RESET}  ${DIM}(if existing codebase)${RESET}`);
+  log(`     Or:  ${DIM}/gsd-t-project${RESET}   ${DIM}(if new project)${RESET}`);
   log("");
 }
 
@@ -1687,7 +1687,7 @@ function showStatusProject() {
     }
   } else if (hasClaudeMd) {
     info("CLAUDE.md found but no .gsd-t/ directory");
-    info("Run /user:gsd-t-init inside Claude Code to set up");
+    info("Run /gsd-t-init inside Claude Code to set up");
   } else {
     info("Not in a GSD-T project directory");
     info(`Run 'npx @tekyzinc/gsd-t init' to set up this directory`);
@@ -1945,6 +1945,19 @@ function exportUniversalRulesForNpm() {
 }
 
 async function doUpdateAll() {
+  // Step 1: Upgrade the globally-installed npm package FIRST. Without this,
+  // `update-all` would only propagate command files — but the global `gsd-t`
+  // binary itself could stay pinned to an older version (e.g., user stuck
+  // on v3.11.11 while npm registry has v3.12.12). See CHANGELOG v3.12.13.
+  // Guard with an env flag to prevent re-exec loops.
+  if (!process.env.GSDT_POST_UPGRADE) {
+    const upgraded = await upgradeGlobalBinary();
+    if (upgraded.reexec) {
+      reexecUpdateAll();
+      return;
+    }
+  }
+
   await updateGlobalCommands();
   heading("Updating registered projects...");
   log("");
@@ -1969,6 +1982,65 @@ async function doUpdateAll() {
   showUpdateAllSummary(projects.length, counts, playwrightMissing, swaggerMissing, syncCount);
 }
 
+// Upgrade the globally-installed @tekyzinc/gsd-t to @latest. Returns
+// { upgraded: bool, reexec: bool, error?: string }.
+// - reexec=true when the on-disk version after `npm install -g` is newer than
+//   the currently-running PKG_VERSION, meaning we need to hand off to the
+//   freshly-installed binary so the new code drives propagation.
+// - reexec=false when already at latest, or when the install failed (we
+//   continue with the current binary and still propagate command files).
+async function upgradeGlobalBinary() {
+  heading("Upgrading global @tekyzinc/gsd-t to latest...");
+  try {
+    execFileSync("npm", ["install", "-g", "@tekyzinc/gsd-t@latest"], {
+      stdio: "inherit",
+      env: process.env,
+    });
+  } catch (e) {
+    warn(`Global npm install failed: ${e.message || e}`);
+    info("Continuing with current binary — command files will still be propagated.");
+    return { upgraded: false, reexec: false, error: String(e.message || e) };
+  }
+
+  // Read the freshly-installed global package's version. If it's newer than
+  // the currently-running process, signal a re-exec.
+  let newVersion = null;
+  try {
+    const prefix = execFileSync("npm", ["prefix", "-g"], { encoding: "utf8" }).trim();
+    const globalPkgJson = path.join(prefix, "lib", "node_modules", "@tekyzinc", "gsd-t", "package.json");
+    if (fs.existsSync(globalPkgJson)) {
+      newVersion = JSON.parse(fs.readFileSync(globalPkgJson, "utf8")).version;
+    }
+  } catch {
+    // Best-effort; fall through.
+  }
+
+  if (newVersion && newVersion !== PKG_VERSION) {
+    success(`Global binary upgraded: v${PKG_VERSION} → v${newVersion}`);
+    info("Handing off to the newly-installed binary for propagation...");
+    return { upgraded: true, reexec: true };
+  }
+  success(`Global binary already at latest (v${PKG_VERSION})`);
+  return { upgraded: true, reexec: false };
+}
+
+// Hand execution to the newly-installed global `gsd-t update-all`. Sets the
+// GSDT_POST_UPGRADE env flag so the child does not recurse into another
+// upgrade attempt.
+function reexecUpdateAll() {
+  const env = Object.assign({}, process.env, { GSDT_POST_UPGRADE: "1" });
+  try {
+    execFileSync("gsd-t", ["update-all"], { stdio: "inherit", env });
+  } catch (e) {
+    // Surface the child's exit code; execFileSync throws with .status on
+    // non-zero exit. Fall through to re-throw so the caller exits cleanly.
+    if (e && typeof e.status === "number") {
+      process.exit(e.status);
+    }
+    throw e;
+  }
+}
+
 async function updateGlobalCommands() {
   if (getInstalledVersion() !== PKG_VERSION) {
     await doInstall({ update: true });
@@ -2718,7 +2790,7 @@ function parseHeadlessFlags(args) {
  * Build the claude -p invocation string for a GSD-T command.
  *
  * Non-interactive `claude -p` mode requires the bare `/gsd-t-X` form — the
- * `/user:gsd-t-X` namespace prefix is rejected as "Unknown command" even
+ * `/gsd-t-X` namespace prefix is rejected as "Unknown command" even
  * though interactive mode accepts both. Verified by M36 Phase 0 Spike A
  * (2026-04-15). See .gsd-t/M36-spike-findings.md.
  */
@@ -3378,8 +3450,8 @@ function showHelp() {
   log(`  ${DIM}$${RESET} npx @tekyzinc/gsd-t init my-saas-app`);
   log(`  ${DIM}$${RESET} npx @tekyzinc/gsd-t update\n`);
   log(`${BOLD}After installing, use in Claude Code:${RESET}`);
-  log(`  ${DIM}>${RESET} /user:gsd-t-project "Build a task management app"`);
-  log(`  ${DIM}>${RESET} /user:gsd-t-wave\n`);
+  log(`  ${DIM}>${RESET} /gsd-t-project "Build a task management app"`);
+  log(`  ${DIM}>${RESET} /gsd-t-wave\n`);
   log(`${DIM}Docs: https://github.com/Tekyz-Inc/get-stuff-done-teams${RESET}\n`);
 }
 

package/commands/gsd-t-backlog-promote.md

@@ -13,14 +13,14 @@ Parse $ARGUMENTS to extract:
 - `<position>` — the entry number to promote
 
 If no position is provided, show an error:
-"Usage: `/user:gsd-t-backlog-promote <position>`"
+"Usage: `/gsd-t-backlog-promote <position>`"
 
 ## Step 2: Find and Display Entry
 
 Find the entry at the specified position in `.gsd-t/backlog.md`.
 
 If the position doesn't exist, show an error:
-"No backlog entry at position {position}. Run `/user:gsd-t-backlog-list` to see available entries."
+"No backlog entry at position {position}. Run `/gsd-t-backlog-list` to see available entries."
 
 Display the entry to the user:
 ```
@@ -88,10 +88,10 @@ After classification is confirmed:
 
 Based on the classification, present the command for the user to invoke:
 
-- **Milestone**: "Run `/user:gsd-t-milestone {refined description}`"
-- **Quick**: "Run `/user:gsd-t-quick {refined description}`"
-- **Debug**: "Run `/user:gsd-t-debug {refined description}`"
-- **Feature**: "Run `/user:gsd-t-feature {refined description}`"
+- **Milestone**: "Run `/gsd-t-milestone {refined description}`"
+- **Quick**: "Run `/gsd-t-quick {refined description}`"
+- **Debug**: "Run `/gsd-t-debug {refined description}`"
+- **Feature**: "Run `/gsd-t-feature {refined description}`"
 
 Display the full command with the refined description ready to copy.
 

package/commands/gsd-t-complete-milestone.md

@@ -3,8 +3,8 @@
 You are finalizing a completed milestone. Your job is to archive the milestone documentation, create a git tag, and prepare for the next milestone.
 
 This command is:
-- **Auto-invoked** by `/user:gsd-t-verify` (Step 8) after all quality gates pass — at ALL autonomy levels
-- **Auto-invoked** by `/user:gsd-t-wave` as part of the VERIFY+COMPLETE phase
+- **Auto-invoked** by `/gsd-t-verify` (Step 8) after all quality gates pass — at ALL autonomy levels
+- **Auto-invoked** by `/gsd-t-wave` as part of the VERIFY+COMPLETE phase
 - **Standalone** when user wants to manually close a milestone
 
 ## Step 1: Verify Completion
@@ -14,7 +14,7 @@ Read:
 2. `.gsd-t/verify-report.md` — confirm all checks passed
 
 If status is not VERIFIED:
-"⚠️ Milestone not yet verified. Run `/user:gsd-t-verify` first, or use `--force` to complete anyway."
+"⚠️ Milestone not yet verified. Run `/gsd-t-verify` first, or use `--force` to complete anyway."
 
 If `--force` flag provided, proceed with warning in archive.
 
@@ -76,7 +76,7 @@ Refer to `.gsd-t/contracts/goal-backward-contract.md` for the full verification
   {findings table}
 
   Options:
-  1. Fix the findings and re-run /user:gsd-t-verify
+  1. Fix the findings and re-run /gsd-t-verify
   2. Override with explicit acknowledgment: re-run this command with --force-goal-backward
 
   Proceed with option 1 (recommended) or acknowledge to force completion?
@@ -493,8 +493,8 @@ Summary:
 
 Next steps:
 - Push tags: git push origin v{version}
-- Start next milestone: /user:gsd-t-milestone "{next name}"
-- Or view roadmap: /user:gsd-t-status
+- Start next milestone: /gsd-t-milestone "{next name}"
+- Or view roadmap: /gsd-t-status
 ```
 
 ## Step 13: Update Roadmap (if exists)
@@ -510,7 +510,7 @@ If `.gsd-t/roadmap.md` exists:
 "Cannot complete — verification found issues. Address them first or use `--force`."
 
 ### If no milestone active:
-"No active milestone to complete. Run `/user:gsd-t-status` to see state."
+"No active milestone to complete. Run `/gsd-t-status` to see state."
 
 ### If git operations fail:
 - Still create archive

package/commands/gsd-t-design-audit.md

@@ -400,7 +400,7 @@ If ANY CRITICAL or HIGH deviations were found, automatically prompt the fix work
 The audit report at `.gsd-t/design-audit-{page-name}-{YYYY-MM-DD}.md`
 has the exact Figma values for each deviation.
 
-`/user:gsd-t-quick fix all CRITICAL and HIGH deviations from .gsd-t/design-audit-{page-name}-{YYYY-MM-DD}.md — use the Figma values in the report as the source of truth`
+`/gsd-t-quick fix all CRITICAL and HIGH deviations from .gsd-t/design-audit-{page-name}-{YYYY-MM-DD}.md — use the Figma values in the report as the source of truth`
 
 ───────────────────────────────────────────────────────────────
 ```
@@ -414,7 +414,7 @@ If ONLY MEDIUM or LOW deviations remain, show:
 
 **{N} MEDIUM + {N} LOW deviations.** These are minor — fix if you want pixel-perfect.
 
-`/user:gsd-t-quick fix MEDIUM and LOW deviations from .gsd-t/design-audit-{page-name}-{YYYY-MM-DD}.md`
+`/gsd-t-quick fix MEDIUM and LOW deviations from .gsd-t/design-audit-{page-name}-{YYYY-MM-DD}.md`
 
 ───────────────────────────────────────────────────────────────
 ```
@@ -427,7 +427,7 @@ After fixes are applied, **re-run the audit automatically** to verify. Loop unti
 
 ## Rules
 
-- **You write ZERO code during the audit phase (Steps 1-5).** Report only. Code changes happen in Step 6 via `/user:gsd-t-quick`.
+- **You write ZERO code during the audit phase (Steps 1-5).** Report only. Code changes happen in Step 6 via `/gsd-t-quick`.
 - **You do NOT "look close" at anything.** Every property gets an exact value from Figma and an exact value from the build. They match or they don't.
 - **You do NOT skip widgets.** Every widget in the Figma AND every widget in the build gets audited.
 - **You MUST call `get_design_context` per widget node — NOT `get_screenshot`.** `get_design_context` returns structured code, component properties, and design tokens. `get_screenshot` returns only a visual image that you cannot extract exact values from. Using `get_screenshot` for widget extraction defeats the entire purpose of structured comparison — you end up eyeballing instead of measuring. The ONLY acceptable use of `get_screenshot` is for the built page (Step 2) where you need to see what was actually rendered. For Figma source data, ALWAYS use `get_design_context`.

package/commands/gsd-t-design-build.md

@@ -40,7 +40,7 @@ Pass any of these as `$ARGUMENTS`:
 ## Prerequisites
 
 - Design contracts must exist in `.gsd-t/contracts/design/` with an `INDEX.md`
-- If no contracts exist, run `/user:gsd-t-design-decompose` first
+- If no contracts exist, run `/gsd-t-design-decompose` first
 
 ## Why a JS Orchestrator?
 

package/commands/gsd-t-design-decompose.md

@@ -471,7 +471,7 @@ This domain owns the following design contracts:
 - Pages: (none — pages owned by page-assembly domain)
 ```
 
-If `.gsd-t/domains/` does NOT exist yet, suggest the user run `/user:gsd-t-partition` next, with a note that design contracts should be partitioned into domains:
+If `.gsd-t/domains/` does NOT exist yet, suggest the user run `/gsd-t-partition` next, with a note that design contracts should be partitioned into domains:
 - **design-system domain** owns element contracts
 - **widgets domain** owns widget contracts
 - **pages domain** owns page assembly + routing
@@ -494,11 +494,11 @@ Display:
 
 **Design Build** — build UI from contracts with tiered review gates (elements → widgets → pages)
 
-`/user:gsd-t-design-build`
+`/gsd-t-design-build`
 
 **Also available:**
-- `/user:gsd-t-partition` — if you need domain boundaries before building
-- `/user:gsd-t-plan` — if you need task lists before building
+- `/gsd-t-partition` — if you need domain boundaries before building
+- `/gsd-t-plan` — if you need task lists before building
 
 ───────────────────────────────────────────────────────────────
 ```

package/commands/gsd-t-execute.md

@@ -66,7 +66,7 @@ This calls `getSessionStatus()` (v2.0.0) which reads `.gsd-t/.context-meter-stat
 
 Use the returned `threshold` as the gate signal for the rest of this run. The gate logic is in Step 3.5; do NOT skip it. If the Context Meter hook isn't installed (`.gsd-t/.context-meter-state.json` missing and doctor reports it), run `gsd-t doctor` to diagnose — the gate still works via the heuristic fallback but real-time readings give much better guardrails.
 
-Why: every `/user:gsd-t-execute` invocation is a fresh orchestrator session and needs a current reading of context utilization before spawning any subagents. The authoritative source is the Context Meter state file; the fallback keeps the gate functional on projects that haven't installed the hook yet.
+Why: every `/gsd-t-execute` invocation is a fresh orchestrator session and needs a current reading of context utilization before spawning any subagents. The authoritative source is the Context Meter state file; the fallback keeps the gate functional on projects that haven't installed the hook yet.
 
 ## Step 1: Load State
 

package/commands/gsd-t-feature.md

@@ -1,6 +1,6 @@
 # GSD-T: Feature — Add a Major Feature to an Existing Project
 
-You are the lead agent planning a significant new feature for an existing codebase. Unlike `/user:gsd-t-project` (greenfield), this command respects and builds on what already exists — existing patterns, schema, auth, conventions, and contracts.
+You are the lead agent planning a significant new feature for an existing codebase. Unlike `/gsd-t-project` (greenfield), this command respects and builds on what already exists — existing patterns, schema, auth, conventions, and contracts.
 
 ## Step 0.5: Scan Freshness Auto-Refresh
 
@@ -154,7 +154,7 @@ The feature may be a single milestone or multiple, depending on scope:
 ### Single Milestone (if feature is focused):
 - 2-4 domains, < 15 tasks total
 - Minimal impact on existing contracts
-- Skip roadmap, go straight to: "Run `/user:gsd-t-partition` to begin"
+- Skip roadmap, go straight to: "Run `/gsd-t-partition` to begin"
 
 ### Multiple Milestones (if feature is complex):
 Apply these sequencing rules:
@@ -267,7 +267,7 @@ Present:
 4. Any conflicts with existing work
 5. Recommended starting point
 
-Ask: "Ready to start? Run `/user:gsd-t-partition` for Milestone {N}."
+Ask: "Ready to start? Run `/gsd-t-partition` for Milestone {N}."
 
 $ARGUMENTS
 

package/commands/gsd-t-gap-analysis.md

@@ -224,13 +224,13 @@ Show the recommended groupings and offer promotion paths:
 ## Recommended Next Steps
 
 1. {Milestone name} — {N} gaps ({critical} critical, {high} high)
-   → /user:gsd-t-milestone "{name}"
+   → /gsd-t-milestone "{name}"
 
 2. {Feature name} — {N} gaps
-   → /user:gsd-t-feature "{name}"
+   → /gsd-t-feature "{name}"
 
 3. Quick fixes — {N} items
-   → /user:gsd-t-quick "{description}"
+   → /gsd-t-quick "{description}"
 
 Promote any of these now, or review the gap analysis first?
 ```

package/commands/gsd-t-health.md

@@ -131,9 +131,9 @@ After repair, re-run the checks and report the final state.
 ## Step 6: Next Steps
 
 If HEALTHY → "✅ GSD-T structure is healthy — all required files present."
-If DEGRADED with --repair done → "✅ Repaired {N} missing files. Run /user:gsd-t-health again to confirm."
-If DEGRADED without --repair → "⚠ Run /user:gsd-t-health --repair to create {N} missing files."
-If BROKEN → "🔴 Project structure is broken. Run /user:gsd-t-health --repair or /user:gsd-t-init to rebuild."
+If DEGRADED with --repair done → "✅ Repaired {N} missing files. Run /gsd-t-health again to confirm."
+If DEGRADED without --repair → "⚠ Run /gsd-t-health --repair to create {N} missing files."
+If BROKEN → "🔴 Project structure is broken. Run /gsd-t-health --repair or /gsd-t-init to rebuild."
 
 $ARGUMENTS
 

package/commands/gsd-t-help.md

@@ -84,8 +84,8 @@ BACKLOG                                                                Manual
   backlog-settings    Manage types, apps, categories, and defaults
 
 ───────────────────────────────────────────────────────────────────────────────
-Type /user:gsd-t-help {command} for detailed help on any command.
-Example: /user:gsd-t-help impact
+Type /gsd-t-help {command} for detailed help on any command.
+Example: /gsd-t-help impact
 ╚══════════════════════════════════════════════════════════════════════════════╝
 ```
 
@@ -94,7 +94,7 @@ Example: /user:gsd-t-help impact
 When user provides a command name, show detailed help:
 
 ```
-/user:gsd-t-help {command}
+/gsd-t-help {command}
 ```
 
 ### Command Details Format:
@@ -108,7 +108,7 @@ SUMMARY
   {One-line description}
 
 USAGE
-  /user:gsd-t-{command} [arguments]
+  /gsd-t-{command} [arguments]
 
 WHEN TO USE
   • {Use case 1}
@@ -131,8 +131,8 @@ FILES CREATED/UPDATED
   • {file 2}
 
 EXAMPLES
-  /user:gsd-t-{command}
-  /user:gsd-t-{command} "with argument"
+  /gsd-t-{command}
+  /gsd-t-{command} "with argument"
 
 RELATED COMMANDS
   • {related 1} — {why related}
@@ -149,10 +149,10 @@ Use these when user asks for help on a specific command:
 - **Summary**: Describe what you need in plain language — auto-routes to the right GSD-T command using semantic evaluation
 - **Auto-invoked**: Yes — via UserPromptSubmit hook when prompt does not start with `/`
 - **Files**: Reads `CLAUDE.md`, `.gsd-t/progress.md`, command summaries from `gsd-t-help`
-- **How it works**: First checks if this is a continuation of an ongoing command (mid-task follow-up, status report, or acknowledgment) — if so, outputs `→ /gsd ──▶ continue /user:gsd-t-{last-command}` and resumes. For new requests, evaluates against every command's purpose and "Use when" criteria. Commands that match get shortlisted, best fit is selected. Shows runner-up when close.
+- **How it works**: First checks if this is a continuation of an ongoing command (mid-task follow-up, status report, or acknowledgment) — if so, outputs `→ /gsd ──▶ continue /gsd-t-{last-command}` and resumes. For new requests, evaluates against every command's purpose and "Use when" criteria. Commands that match get shortlisted, best fit is selected. Shows runner-up when close.
 - **Auto-route**: After `gsd-t install`, any plain text message (no leading `/`) is automatically routed through `/gsd`. Slash commands pass through unchanged. Binary detection — no heuristics.
 - **Use when**: You don't want to remember which command to use — just describe what you want
-- **Examples**: `/user:gsd Fix the login bug`, `/user:gsd Add dark mode`, `/user:gsd Scan for tech debt`
+- **Examples**: `/gsd Fix the login bug`, `/gsd Add dark mode`, `/gsd Scan for tech debt`
 - **Auto-route examples**: `Fix the login bug` (no slash needed), `Add dark mode`, `Scan for tech debt`
 
 ### prd
@@ -228,7 +228,7 @@ Use these when user asks for help on a specific command:
 - **Use when**: Ready to define specific implementation tasks
 - **Note (M22)**: Tasks auto-split if estimated scope exceeds 70% context window — guarantees fresh dispatch works
 - **Note (M26)**: Pre-mortem step now also reads rules.jsonl for historical failure patterns via getPreMortemRules
-- **Note (M38)**: Conversational use cases (formerly `/user:gsd-t-prompt`, `/user:gsd-t-brainstorm`, `/user:gsd-t-discuss`) are now handled by the Smart Router's conversational mode — just describe what you want via `/user:gsd` or plain text.
+- **Note (M38)**: Conversational use cases (formerly `/gsd-t-prompt`, `/gsd-t-brainstorm`, `/gsd-t-discuss`) are now handled by the Smart Router's conversational mode — just describe what you want via `/gsd` or plain text.
 
 ### impact
 - **Summary**: Analyze downstream effects of planned changes
@@ -433,7 +433,7 @@ Did you mean one of these?
   • {closest match 1}
   • {closest match 2}
 
-Run /user:gsd-t-help for full command list.
+Run /gsd-t-help for full command list.
 ```
 
 $ARGUMENTS

package/commands/gsd-t-impact.md

@@ -3,7 +3,7 @@
 You are analyzing the downstream effects of planned changes before execution. Your job is to identify what might break, what needs updating, and what risks exist.
 
 This command is:
-- **Auto-invoked** between plan and execute phases in `/user:gsd-t-wave`
+- **Auto-invoked** between plan and execute phases in `/gsd-t-wave`
 - **Standalone** when user wants to evaluate potential changes
 
 ## Step 1: Load Context
@@ -273,7 +273,7 @@ Validate the test landscape before recommending proceed/block:
 - List the red items
 - Generate remediation tasks
 - Add tasks to current domain's task list
-- "Run `/user:gsd-t-execute` to address these first, then re-run impact analysis."
+- "Run `/gsd-t-execute` to address these first, then re-run impact analysis."
 - Do NOT proceed to execute phase
 
 ## Standalone Mode
@@ -281,7 +281,7 @@ Validate the test landscape before recommending proceed/block:
 When run independently (not as part of wave):
 
 ```
-/user:gsd-t-impact "considering adding user roles to the auth system"
+/gsd-t-impact "considering adding user roles to the auth system"
 ```
 
 1. Ask clarifying questions about the change

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

@@ -64,7 +64,7 @@ All subsequent steps run from inside the project directory.
 
 ## Step 3: Initialize Project (gsd-t-init)
 
-Execute the full init workflow (same as `/user:gsd-t-init`):
+Execute the full init workflow (same as `/gsd-t-init`):
 
 1. Create `.gsd-t/` directory structure (contracts/, domains/, progress.md, backlog.md, backlog-settings.md, token-log.md, qa-issues.md)
 2. Ensure `CLAUDE.md` exists (create starter if missing, append GSD-T section if present without it)
@@ -101,7 +101,7 @@ If the project has source code, graph indexing (`.gsd-t/graph/`) will run as par
 
 ## Step 4: Deep Codebase Scan (gsd-t-scan)
 
-Execute the full scan workflow (same as `/user:gsd-t-scan`):
+Execute the full scan workflow (same as `/gsd-t-scan`):
 
 1. Scan across all dimensions: architecture, business rules, security, quality, contracts
 2. Build `.gsd-t/techdebt.md` register
@@ -114,7 +114,7 @@ Always use team mode for the scan unless the codebase is trivially small (< 5 fi
 
 ## Step 5: Generate Project CLAUDE.md (gsd-t-setup)
 
-Execute the full setup workflow (same as `/user:gsd-t-setup`):
+Execute the full setup workflow (same as `/gsd-t-setup`):
 
 1. Read global `~/.claude/CLAUDE.md` to understand what's already covered
 2. Use scan findings + auto-detection to populate project-specific sections
@@ -139,8 +139,8 @@ Project Onboarded: {project name}
 
 Next steps:
   → Review .gsd-t/techdebt.md for critical items
-  → /user:gsd-t-milestone to define your first milestone
-  → /user:gsd-t-wave to run a full development cycle
+  → /gsd-t-milestone to define your first milestone
+  → /gsd-t-wave to run a full development cycle
 ```
 
 ### Autonomy Behavior

package/commands/gsd-t-init.md

@@ -154,7 +154,7 @@ Read the project's `CLAUDE.md` (if it exists) to auto-populate backlog settings:
 1. **Apps**: Scan for app names, service names, or product names (look for headings, "Tech Stack" sections, or named components). Populate the `## Apps` section in `backlog-settings.md` with discovered names (lowercase).
 2. **Categories**: Scan for domain concepts, module names, and technical areas (e.g., "authentication", "payments", "api", "database"). Populate the `## Categories` section.
 3. **Default App**: Set `**Default App:**` to the most prominent app found (the one mentioned most, or the first one). If only one app is found, use it.
-4. **If nothing found**: Leave the placeholder values from the template — the user can configure later via `/user:gsd-t-backlog-settings`.
+4. **If nothing found**: Leave the placeholder values from the template — the user can configure later via `/gsd-t-backlog-settings`.
 
 ## Step 5: Initialize Progress File
 
@@ -366,10 +366,10 @@ After initialization:
 Tell the user:
 1. What was created (including backlog files: `.gsd-t/backlog.md` and `.gsd-t/backlog-settings.md`)
 2. What they should fill in (CLAUDE.md details, requirements)
-3. Backlog settings status: whether apps/categories were auto-derived from CLAUDE.md or need manual configuration via `/user:gsd-t-backlog-settings`
+3. Backlog settings status: whether apps/categories were auto-derived from CLAUDE.md or need manual configuration via `/gsd-t-backlog-settings`
 4. Recommended next step:
-   - New project: "Define your milestone, then run /user:gsd-t-partition"
-   - Existing code: "I've mapped the codebase. Ready for /user:gsd-t-partition {milestone}"
+   - New project: "Define your milestone, then run /gsd-t-partition"
+   - Existing code: "I've mapped the codebase. Ready for /gsd-t-partition {milestone}"
 
 $ARGUMENTS
 

package/commands/gsd-t-log.md

@@ -8,7 +8,7 @@ Read:
 1. `.gsd-t/progress.md` — current Decision Log entries
 2. Note the **last entry's timestamp** — this is the cutoff; only commits after this time need processing
 
-If `.gsd-t/progress.md` doesn't exist, inform user: "No GSD-T state found. Run `/user:gsd-t-init` first."
+If `.gsd-t/progress.md` doesn't exist, inform user: "No GSD-T state found. Run `/gsd-t-init` first."
 
 ## Step 2: Get Recent Commits
 

package/commands/gsd-t-milestone.md

@@ -44,7 +44,7 @@ Before formal partitioning, do a quick assessment:
 
 - **Complexity estimate**: Simple (1-2 domains), Medium (3-4), Complex (5+)
 - **Recommended approach**:
-  - Simple: Consider using /user:gsd-t-quick for each piece
+  - Simple: Consider using /gsd-t-quick for each piece
   - Medium: Standard partition → plan → execute flow
   - Complex: Partition → discuss → plan → execute → integrate → verify
 
@@ -78,7 +78,7 @@ Before proceeding to partition:
 If the user wants to proceed immediately, execute the partition workflow (same as gsd-t-partition) for this milestone.
 
 Otherwise, set status to DEFINED and remind them:
-"Run /user:gsd-t-partition to decompose into domains, or /user:gsd-t-discuss to explore approaches first."
+"Run /gsd-t-partition to decompose into domains, or /gsd-t-discuss to explore approaches first."
 
 $ARGUMENTS
 

package/commands/gsd-t-pause.md

@@ -54,7 +54,7 @@ Create `.gsd-t/continue-here-{timestamp}.md`:
 {$ARGUMENTS if provided, otherwise: _No note provided._}
 
 ## Resume Command
-/user:gsd-t-resume
+/gsd-t-resume
 ```
 
 ## Step 4: Confirm to User
@@ -67,7 +67,7 @@ Output:
 Saved position: .gsd-t/continue-here-{timestamp}.md
 Next action:    {next action summary}
 
-To resume: /user:gsd-t-resume
+To resume: /gsd-t-resume
 ```
 
 ## Step 5: Do NOT Stop Work (unless user asked to pause all work)

package/commands/gsd-t-prd.md

@@ -291,13 +291,13 @@ Next steps:
 
 For a new project:
 ```
-/user:gsd-t-project {one-line summary}
+/gsd-t-project {one-line summary}
 ```
 Then paste the PRD when prompted. The PRD's requirements table becomes docs/requirements.md. The architecture section seeds docs/architecture.md. The milestone sequence becomes your roadmap.
 
 For a feature on an existing project:
 ```
-/user:gsd-t-feature {one-line summary}
+/gsd-t-feature {one-line summary}
 ```
 Then paste the PRD when prompted.
 

package/commands/gsd-t-project.md

@@ -200,7 +200,7 @@ Present:
 4. Any scope decisions you made and why
 5. Questions or trade-offs that need user input
 
-Ask: "Ready to start Milestone 1? Run `/user:gsd-t-partition` to decompose it into domains."
+Ask: "Ready to start Milestone 1? Run `/gsd-t-partition` to decompose it into domains."
 
 Or if the user wants to review first: "Review the roadmap in `.gsd-t/roadmap.md` and let me know if you want to adjust scope or ordering."
 

package/commands/gsd-t-resume.md

@@ -149,7 +149,7 @@ Progress:
 Next up: {specific next action}
 Blockers: {any pending items} | None
 
-Ready to continue? Or run /user:gsd-t-status for full details.
+Ready to continue? Or run /gsd-t-status for full details.
 ```
 
 ## Step 4: Continue
@@ -171,9 +171,9 @@ When the resumed work reaches a natural handoff point, do NOT print a "Next Up"
 |--------------------------|-----------------|
 | A task (mid-wave, tasks remaining) | next task in the same wave |
 | The last task of a wave (waves remaining) | next wave |
-| The last task of the last wave | `/user:gsd-t-verify` (which auto-invokes `/user:gsd-t-complete-milestone` per verify Step 8) |
-| `/user:gsd-t-verify` (VERIFIED or VERIFIED-WITH-WARNINGS) | `/user:gsd-t-complete-milestone` (verify already spawns this — do not re-invoke) |
-| `/user:gsd-t-complete-milestone` | honor any outstanding multi-step user directive (see below) |
+| The last task of the last wave | `/gsd-t-verify` (which auto-invokes `/gsd-t-complete-milestone` per verify Step 8) |
+| `/gsd-t-verify` (VERIFIED or VERIFIED-WITH-WARNINGS) | `/gsd-t-complete-milestone` (verify already spawns this — do not re-invoke) |
+| `/gsd-t-complete-milestone` | honor any outstanding multi-step user directive (see below) |
 
 **Never stop at "Wave N complete" or "Task N done" and wait.** The only stopping points are:
 1. VERIFY-FAILED (report failures)

package/commands/gsd-t-scan.md

@@ -235,7 +235,7 @@ Operations implemented independently in 2+ places — candidates for extraction
 If none found: `✅ No shared service candidates detected.`
 
 > **Note**: These candidates should seed Step 1.6 (Consumer Surface Identification) the next
-> time `/user:gsd-t-partition` is run. Copy the "Consumer Surfaces Detected" table into
+> time `/gsd-t-partition` is run. Copy the "Consumer Surfaces Detected" table into
 > partition's Step 1.6.1 to skip re-research.
 
 ## Complexity Hotspots
@@ -442,7 +442,7 @@ Can be scheduled: During next maintenance window
 Combines: all "Shared Service Candidates" from quality.md Reusability Analysis
 Estimated effort: {assessment}
 Should be prioritized: BEFORE adding new consumer surfaces to the system
-Note: Use `/user:gsd-t-partition` Step 1.6 to design the SharedCore domain
+Note: Use `/gsd-t-partition` Step 1.6 to design the SharedCore domain
 ```
 
 ## Step 5: Update Living Documents
@@ -563,7 +563,7 @@ If `.gsd-t/progress.md` exists:
 
 If `.gsd-t/roadmap.md` exists:
 - Do NOT auto-add milestones — present suggestions to user
-- User decides which to promote with `/user:gsd-t-promote-debt`
+- User decides which to promote with `/gsd-t-promote-debt`
 
 If `CLAUDE.md` exists:
 - Suggest updates for any patterns or conventions discovered during scan