@tekyzinc/gsd-t 2.31.13 → 2.31.15

package/commands/gsd-t-help.md

@@ -137,7 +137,7 @@ 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**: Evaluates your request 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 /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.
 - **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`

package/commands/gsd-t-init.md

@@ -90,13 +90,27 @@ Read the project's `CLAUDE.md` (if it exists) to auto-populate backlog settings:
 
 ## Step 5: Initialize Progress File
 
+### Version Detection
+
+Before creating the progress file, determine the starting version:
+
+1. **Check for an existing version** in the project's manifest file (in this priority order):
+   - `package.json` → `version` field
+   - `pyproject.toml` → `[project] version` or `[tool.poetry] version`
+   - `Cargo.toml` → `[package] version`
+   - `setup.py` → `version=` argument
+   - `build.gradle` / `build.gradle.kts` → `version = `
+   - `.version` file → contents as-is
+2. **If a version is found**: Use it as the starting GSD-T version (the project already has its own versioning history).
+3. **If no version is found**: Use `0.1.00` — the standard GSD-T starting point for a brand-new project with no prior releases. The first `gsd-t-complete-milestone` will reset the patch to `0.1.10` (or bump minor/major per milestone scope).
+
 Create `.gsd-t/progress.md`:
 
 ```markdown
 # GSD-T Progress
 
 ## Project: {name from CLAUDE.md or $ARGUMENTS}
-## Version: 0.1.0
+## Version: {detected version, or 0.1.00}
 ## Status: INITIALIZED
 ## Date: {today}
 

package/commands/gsd.md

@@ -8,6 +8,22 @@ Read:
 1. `CLAUDE.md` — project context
 2. `.gsd-t/progress.md` — current state, active milestone/phase
 
+## Step 2a: Continuation Check
+
+Before semantic evaluation, determine if this is a **continuation** of an already-running command.
+
+**Continuation indicators (any = continuation):**
+- Message is a follow-up, answer, acknowledgment, or status report — not a new task request
+- Message contains tool output, code, file content, or work artifacts from ongoing work
+- Message reads as mid-task input (e.g., "both files parse cleanly", "yes continue", "looks good", "done")
+- Progress.md shows an active/in-progress phase AND the message doesn't clearly start a new task
+
+**If continuation detected** → skip Step 2, go to Step 3 using the **continuation format**.
+
+**If NOT a continuation** → proceed to Step 2 (normal semantic evaluation).
+
+---
+
 ## Step 2: Semantic Evaluation
 
 Read the **Command Summaries** section of `commands/gsd-t-help.md` (or the in-memory skill list). For each command, evaluate whether the user's request matches that command's **Summary** and **Use when** criteria.
@@ -43,13 +59,37 @@ When the same request could fit multiple commands at different scales:
 
 ## Step 3: Confirm and Execute
 
-**MANDATORY — before doing anything else, output this line FIRST:**
+**MANDATORY — output one of these lines as the VERY FIRST thing in your response, before any tool calls or other output.**
 
+### New request (from Step 2):
 ```
 → Routing to /user:gsd-t-{command}: {brief reason}
 ```
 
-**CRITICAL: `{command}` MUST be a real GSD-T command slug — never a free-form description.**
+### Continuation (from Step 2a):
+```
+→ /gsd ──▶ continue /user:gsd-t-{last-command}
+```
+
+Where `{last-command}` is:
+1. The command most recently active in this conversation, OR
+2. Inferred from progress.md current phase:
+
+| Phase in progress.md | Command slug |
+|----------------------|--------------|
+| EXECUTE | `execute` |
+| PLAN | `plan` |
+| PARTITION | `partition` |
+| VERIFY | `verify` |
+| INTEGRATE | `integrate` |
+| TEST-SYNC | `test-sync` |
+| COMPLETE | `complete-milestone` |
+| SCAN | `scan` |
+| WAVE | `wave` |
+| QUICK | `quick` |
+| DEBUG | `debug` |
+
+**CRITICAL: `{command}` and `{last-command}` MUST be a real GSD-T command slug — never a free-form description.**
 
 Valid command slugs: `quick`, `debug`, `feature`, `execute`, `milestone`, `project`, `scan`, `gap-analysis`, `plan`, `partition`, `discuss`, `impact`, `integrate`, `verify`, `test-sync`, `complete-milestone`, `wave`, `status`, `populate`, `setup`, `init`, `health`, `log`, `pause`, `resume`, `prd`, `brainstorm`, `prompt`, `backlog-add`, `backlog-list`, `backlog-promote`, `promote-debt`, `triage-and-merge`, `version-update`, `version-update-all`
 
@@ -57,17 +97,18 @@ Valid command slugs: `quick`, `debug`, `feature`, `execute`, `milestone`, `proje
 ```
 → Routing to research + PRD update: reading web app auth code
 → Routing to implementation: adding the login feature
-→ Routing to fix: resolving the bug
+→ /gsd ──▶ continue: mid-task work
 ```
 
 **RIGHT ✅** — always use the exact command slug:
 ```
 → Routing to /user:gsd-t-execute: implement auth feature across backend
 → Routing to /user:gsd-t-debug: investigate login bug before fixing
-→ Routing to /user:gsd-t-quick: small focused change to config file
+→ /gsd ──▶ continue /user:gsd-t-execute
+→ /gsd ──▶ continue /user:gsd-t-quick
 ```
 
-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.
+This MUST be the very first line of your response. Then immediately execute that command's full workflow, passing `$ARGUMENTS` through.
 
 **Do NOT ask "is this the right command?" — just route and go.** The user can interrupt with Esc if it's wrong.
 

package/package.json

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

package/templates/CLAUDE-global.md

@@ -118,7 +118,9 @@ GSD-T tracks project version in `.gsd-t/progress.md` using semantic versioning:
 
 **Patch convention**: Patch numbers are always 2 digits (≥10). When resetting after a minor or major bump, start at **10** (not 0). This keeps patches always 2 characters without leading zeros, so semver stays valid.
 
-- Version is set during `gsd-t-init` (starts at `0.1.10`)
+- Version is set during `gsd-t-init`:
+  - **New project** (no existing manifest version): starts at `0.1.00` — first `complete-milestone` resets patch to `0.1.10`
+  - **Existing repo** (has `package.json`, `pyproject.toml`, `Cargo.toml`, etc. with a version): use that version as the starting point
 - Version is bumped during `gsd-t-complete-milestone` based on milestone scope
 - Version is reflected in: `progress.md`, `README.md`, package manifest (if any), and git tags (`v{version}`)