@tekyzinc/gsd-t 2.10.2 → 2.11.0

package/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.11.0] - 2026-02-12
+
+### Added
+- Autonomy-level-aware auto-advancing for all phase commands — at Level 3 (Full Auto), partition, plan, impact, execute, test-sync, integrate, verify, and complete-milestone auto-advance without waiting for user input
+- Wave error recovery auto-remediates at Level 3 (up to 2 fix attempts before stopping)
+- Discuss phase always pauses for user input regardless of autonomy level
+- Autonomy levels documentation added to GSD-T-README Configuration section
+
+## [2.10.3] - 2026-02-11
+
+### Changed
+- Default autonomy level changed from Level 2 (Standard) to Level 3 (Full Auto) across all templates and commands
+- `gsd-t-init` now sets Level 3 in generated CLAUDE.md
+- `gsd-t-setup` defaults to Level 3 when asking autonomy level
+
 ## [2.10.2] - 2026-02-11
 
 ### Added

package/commands/gsd-t-execute.md

@@ -123,6 +123,11 @@ When all tasks in all domains are complete:
 1. Update `.gsd-t/progress.md` — all tasks marked complete
 2. Set status to `EXECUTED`
 3. List any contract deviations or decisions made during execution
-4. Recommend: proceed to integrate phase
+
+### Autonomy Behavior
+
+**Level 3 (Full Auto)**: Log a brief status line (e.g., "✅ Execute complete — {N}/{N} tasks done") and auto-advance to the next phase. Do NOT wait for user input.
+
+**Level 1–2**: Report completion summary and recommend proceeding to integrate phase. Wait for confirmation.
 
 $ARGUMENTS

package/commands/gsd-t-impact.md

@@ -211,9 +211,10 @@ Validate the test landscape before recommending proceed/block:
 ### If PROCEED WITH CAUTION:
 "⚠️ Impact analysis found {N} items requiring attention:"
 - List the yellow items
-- "These can be addressed during execution. Proceed?"
-- If user confirms, continue
-- If user declines, pause for remediation
+
+**Level 3 (Full Auto)**: Log the caution items and auto-advance to execute. Do NOT wait for user input.
+
+**Level 1–2**: "These can be addressed during execution. Proceed?" Wait for user confirmation. If user declines, pause for remediation.
 
 ### If BLOCK:
 "🛑 Impact analysis found breaking changes that must be addressed first:"

package/commands/gsd-t-init.md

@@ -96,6 +96,9 @@ Create a starter template:
 - Workflows: docs/workflows.md
 - Infrastructure: docs/infrastructure.md
 
+## Autonomy Level
+**Level 3 — Full Auto** (only pause for blockers or completion)
+
 ## Branch Guard
 **Expected branch**: {current branch from `git branch --show-current`}
 

package/commands/gsd-t-integrate.md

@@ -129,8 +129,13 @@ Update `.gsd-t/progress.md`:
 - Add contract audit results
 - Add smoke test results
 - List any new tasks created for gaps
-- Recommend: proceed to verify phase
 
 Commit: `[integration] Wire domains together — all contracts verified`
 
+### Autonomy Behavior
+
+**Level 3 (Full Auto)**: Log a brief status line (e.g., "✅ Integrate complete — all domain boundaries wired, {N} contracts verified") and auto-advance to the next phase. Do NOT wait for user input.
+
+**Level 1–2**: Report integration results and recommend proceeding to verify phase. Wait for confirmation.
+
 $ARGUMENTS

package/commands/gsd-t-partition.md

@@ -184,6 +184,10 @@ Before finishing, verify:
 - [ ] Every contract has an owner and at least one consumer
 - [ ] Integration checkpoints are identified for all cross-domain dependencies
 
-Report the partition to the user with a summary of domains, contracts, and any decisions that need input.
+### Autonomy Behavior
+
+**Level 3 (Full Auto)**: Log a brief status line (e.g., "✅ Partition complete — {N} domains defined, {N} contracts written") and auto-advance to the next phase. Do NOT wait for user input.
+
+**Level 1–2**: Report the partition to the user with a summary of domains, contracts, and any decisions that need input. Wait for confirmation before proceeding.
 
 $ARGUMENTS

package/commands/gsd-t-plan.md

@@ -127,7 +127,11 @@ Update `.gsd-t/progress.md`:
 
 ## Step 6: Report
 
-Present to the user:
+### Autonomy Behavior
+
+**Level 3 (Full Auto)**: Log a brief status line (e.g., "✅ Plan complete — {N} tasks across {N} domains, {execution mode}") and auto-advance to the next phase. Do NOT wait for user input.
+
+**Level 1–2**: Present to the user:
 1. Task count per domain
 2. Dependency graph (which domains block which)
 3. Recommended execution mode:
@@ -136,4 +140,6 @@ Present to the user:
    - **Team parallel**: 15+ tasks with 3+ independent starting points
 4. Any ambiguities found during planning that need user input
 
+Wait for confirmation before proceeding.
+
 $ARGUMENTS

package/commands/gsd-t-setup.md

@@ -79,7 +79,7 @@ Only ask what could NOT be auto-detected. Skip questions where the answer is alr
 **Potential questions** (ask only if not auto-detected):
 
 1. **Branch Guard**: "Which branch should commits target?" (skip if only `main` or `master` exists)
-2. **Autonomy Level**: "What autonomy level? Level 1 (Supervised), Level 2 (Standard — default), Level 3 (Full Auto)" (skip if existing CLAUDE.md already declares it)
+2. **Autonomy Level**: "What autonomy level? Level 1 (Supervised), Level 2 (Standard), Level 3 (Full Auto — default)" (skip if existing CLAUDE.md already declares it)
 3. **Workflow Preferences**: "Any overrides to the global defaults? (Research Policy, Phase Flow)" (skip if user has no overrides)
 4. **Deployed URLs**: "Production, staging, and local URLs?" (skip if found in .env or existing docs)
 5. **Project-specific rules**: "Any 'never do' rules specific to this project?" (skip if existing CLAUDE.md already has them)
@@ -123,7 +123,7 @@ Build the file using this structure. Include only sections that have real conten
 - Infrastructure: docs/infrastructure.md
 
 ## Autonomy Level
-**Level {N} — {Name}** (pause at {description})
+**Level {N} — {Name}** ({description})  <!-- default: Level 3 — Full Auto -->
 
 ## Workflow Preferences
 <!-- Override global defaults. Delete what you don't need to override. -->

package/commands/gsd-t-test-sync.md

@@ -296,4 +296,10 @@ Action Required:
 Generated 5 test tasks → added to current domain
 ```
 
+### Autonomy Behavior
+
+**Level 3 (Full Auto)**: Log the summary and auto-advance to the next phase. If there are failing tests, attempt auto-fix (up to 2 attempts) before continuing. Do NOT wait for user input.
+
+**Level 1–2**: Present the full report and wait for user input before proceeding.
+
 $ARGUMENTS

package/commands/gsd-t-verify.md

@@ -137,7 +137,14 @@ Update `.gsd-t/progress.md`:
 - If FAIL: Set status to `VERIFY-FAILED`, list required remediations
 - Record verification date and summary
 
-Recommend next step:
+### Autonomy Behavior
+
+**Level 3 (Full Auto)**:
+- VERIFIED → Log "✅ Verify complete — all quality gates passed" and auto-advance to complete-milestone. Do NOT wait for user input.
+- CONDITIONAL PASS → Log warnings, treat as VERIFIED, and auto-advance. Do NOT wait for user input.
+- FAIL → Auto-execute remediation tasks (up to 2 fix attempts). If still failing after 2 attempts, STOP and report to user.
+
+**Level 1–2**:
 - VERIFIED → Milestone complete, proceed to next milestone or ship
 - CONDITIONAL PASS → User decides if warnings are acceptable
 - FAIL → Return to execute phase for remediation tasks

package/commands/gsd-t-wave.md

@@ -91,8 +91,16 @@ Work through each phase that hasn't been completed:
 Between each phase:
 1. Update `.gsd-t/progress.md`
 2. Report brief status to user
-3. If any phase produces findings that need user input, STOP and ask
-4. If all clear, continue to next phase
+
+### Autonomy Behavior
+
+**Level 3 (Full Auto)**: Auto-advance to the next phase after logging status. Only STOP for:
+- Destructive Action Guard violations (always)
+- Impact analysis BLOCK verdict (always)
+- Unrecoverable errors after 2 fix attempts
+- The Discuss phase (always pauses for user input, even at Level 3)
+
+**Level 1–2**: If any phase produces findings that need user input, STOP and ask. If all clear, continue to next phase.
 
 Status messages:
 ```
@@ -147,25 +155,28 @@ If the user interrupts or the session needs to end:
 - Report blocking issues
 - Generate remediation tasks
 - Add to appropriate domain
-- Ask: "Address blockers now, or pause?"
-- If address: execute remediation tasks, re-run impact
-- If pause: save state, exit
+
+**Level 3 (Full Auto)**: Auto-execute remediation tasks, then re-run impact analysis. Only STOP if remediation fails after 2 attempts.
+
+**Level 1–2**: Ask: "Address blockers now, or pause?" If address: execute remediation tasks, re-run impact. If pause: save state, exit.
 
 ### If tests fail during execute:
 - Pause execution
 - Report failing tests
 - Generate fix tasks
-- Ask: "Fix now or continue?"
-- If fix: execute fix tasks, re-run tests
-- If continue: note failures, proceed (will catch in verify)
+
+**Level 3 (Full Auto)**: Auto-execute fix tasks and re-run tests (up to 2 fix attempts). If still failing, STOP and report to user.
+
+**Level 1–2**: Ask: "Fix now or continue?" If fix: execute fix tasks, re-run tests. If continue: note failures, proceed (will catch in verify).
 
 ### If verify fails:
 - Report failures
 - Generate remediation tasks
 - Do NOT run complete-milestone
-- Ask: "Address issues now?"
-- If yes: execute remediation, re-run verify
-- If no: save state with VERIFY_FAILED status
+
+**Level 3 (Full Auto)**: Auto-execute remediation tasks and re-run verify (up to 2 attempts). If still failing, STOP and report to user.
+
+**Level 1–2**: Ask: "Address issues now?" If yes: execute remediation, re-run verify. If no: save state with VERIFY_FAILED status.
 
 ## Workflow Visualization
 

package/docs/GSD-T-README.md

@@ -250,6 +250,16 @@ Verify with: `/user:gsd-t-help`
 
 GSD-T respects your project's `CLAUDE.md` for conventions and autonomy level.
 
+### Autonomy Levels
+
+| Level | Phase Behavior |
+|-------|---------------|
+| **Level 1: Supervised** | Pauses at each phase for confirmation |
+| **Level 2: Standard** | Pauses at milestones |
+| **Level 3: Full Auto** (default) | Auto-advances through all phases. Only stops for: Destructive Action Guard, impact BLOCK verdicts, unrecoverable errors (after 2 fix attempts), and the Discuss phase |
+
+Set in your project's `CLAUDE.md` under `## Autonomy Level`.
+
 Recommended `.gsd-t/config.json`:
 
 ```json

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "2.10.2",
+  "version": "2.11.0",
   "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

@@ -213,10 +213,10 @@ Projects can specify an autonomy level in their project CLAUDE.md:
 | Level | Behavior |
 |-------|----------|
 | **Level 1: Supervised** | Pause at each phase for confirmation |
-| **Level 2: Standard** | Pause only at milestones (default) |
-| **Level 3: Full Auto** | Only pause for blockers or project completion |
+| **Level 2: Standard** | Pause only at milestones |
+| **Level 3: Full Auto** | Only pause for blockers or project completion (default) |
 
-If not specified, use Level 2.
+If not specified, use Level 3.
 
 ## Workflow Preferences (Defaults — override in project CLAUDE.md)
 

package/templates/CLAUDE-project.md

@@ -4,7 +4,7 @@
 {Brief project description — what problem does this solve and for whom?}
 
 ## Autonomy Level
-**Level 2 — Standard** (pause at milestones)
+**Level 3 — Full Auto** (only pause for blockers or completion)
 <!-- Options: Level 1 (Supervised), Level 2 (Standard), Level 3 (Full Auto) -->
 
 ## Tech Stack