@tekyzinc/gsd-t 2.11.0 → 2.11.1

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.11.1] - 2026-02-12
+
+### Changed
+- `gsd-t-resume` now detects same-session vs cross-session mode — skips full state reload when context is already available, auto-resumes at Level 3
+- Added "Conversation vs. Work" rule to global CLAUDE.md template — plain text questions are answered conversationally, workflow only runs when a `/gsd-t-*` command is invoked
+
 ## [2.11.0] - 2026-02-12
 
 ### Added

package/commands/gsd-t-resume.md

@@ -1,8 +1,17 @@
 # GSD-T: Resume — Continue From Last State
 
-You are restoring context and continuing from where the last session left off. This is the first command to run when starting a new Claude Code session on an existing GSD-T project.
+You are resuming work after an interruption. This handles both same-session pauses (user pressed Esc to interject) and cross-session recovery (new Claude Code session).
 
-## Step 1: Load Full State
+## Step 0: Detect Resume Mode
+
+**Same-session** (conversation context still available — you can see prior messages about the active phase/task):
+- Skip to Step 2 — you already have the context loaded
+- Do NOT re-read all state files
+
+**Cross-session** (first command in a new session, no prior conversation context):
+- Run Step 1 to load full state
+
+## Step 1: Load Full State (cross-session only)
 
 Read in this exact order:
 1. `CLAUDE.md` — project context and conventions
@@ -16,16 +25,23 @@ Read in this exact order:
 
 ## Step 2: Determine Current Position
 
-From progress.md, identify:
+From progress.md (or conversation context if same-session), identify:
 - Current milestone and status
 - Which phase we're in
 - Which tasks are done, in progress, or blocked
 - Any pending decisions or user-input-needed items
 - Last entry in the Decision Log
 
-## Step 3: Report Context
+## Step 3: Report and Continue
+
+**Level 3 (Full Auto)**: Log a brief status line and auto-resume from the current task/phase. Do NOT wait for user input.
+
+```
+🔄 Resuming: {milestone name} — {phase} — {next task or action}
+```
+
+**Level 1–2**: Present fuller context and wait for confirmation:
 
-Present to the user:
 ```
 🔄 GSD-T Resuming: {milestone name}
 Phase: {current phase}
@@ -44,7 +60,7 @@ Ready to continue? Or run /user:gsd-t-status for full details.
 ## Step 4: Continue
 
 If $ARGUMENTS specifies what to do next, proceed with that.
-Otherwise, recommend the logical next action based on current state:
+Otherwise, pick up from the logical next action based on current state:
 - Mid-execution → Continue with next unblocked task
 - Between phases → Start next phase
 - Blocked → Explain what's needed to unblock

package/package.json

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

package/templates/CLAUDE-global.md

@@ -149,6 +149,10 @@ Even in development, the user may have:
 
 # Autonomous Execution Rules
 
+## Conversation vs. Work
+
+Only execute GSD-T workflow behavior when a `/gsd-t-*` command is invoked or when actively mid-phase (resumed via `/gsd-t-resume`). **Plain text messages — especially questions — should be answered conversationally.** Do not launch into workflow execution, file reading, or phase advancement from a question or comment. If the user wants work done, they will invoke a command.
+
 ## Prime Rule
 KEEP GOING. Only stop for:
 1. Unrecoverable errors after 2 fix attempts