get-shit-done-cc 1.5.30 → 1.6.0

package/commands/gsd/progress.md

@@ -323,21 +323,12 @@ Ready to plan the next milestone.
 
 ## ▶ Next Up
 
-**Discuss Next Milestone** — figure out what to build next
+**Start Next Milestone** — questioning → research → requirements → roadmap
 
-`/gsd:discuss-milestone`
+`/gsd:new-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
----
-
-**Next milestone flow:**
-1. `/gsd:discuss-milestone` — thinking partner, creates context file
-2. `/gsd:new-milestone` — update PROJECT.md with new goals
-3. `/gsd:research-project` — (optional) research ecosystem
-4. `/gsd:define-requirements` — scope what to build
-5. `/gsd:create-roadmap` — plan how to build it
-
 ---
 ```
 

package/commands/gsd/verify-work.md

@@ -61,6 +61,150 @@ Phase: $ARGUMENTS (optional)
 - Don't fix issues during testing — log as gaps, diagnose after all tests complete
 </anti_patterns>
 
+<offer_next>
+Output this markdown directly (not as a code block). Route based on UAT results:
+
+| Status | Route |
+|--------|-------|
+| All tests pass + more phases | Route A (next phase) |
+| All tests pass + last phase | Route B (milestone complete) |
+| Issues found + fix plans ready | Route C (execute fixes) |
+| Issues found + planning blocked | Route D (manual intervention) |
+
+---
+
+**Route A: All tests pass, more phases remain**
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► PHASE {Z} VERIFIED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Phase {Z}: {Name}**
+
+{N}/{N} tests passed
+UAT complete ✓
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
+
+/gsd:discuss-phase {Z+1} — gather context and clarify approach
+
+<sub>/clear first → fresh context window</sub>
+
+───────────────────────────────────────────────────────────────
+
+**Also available:**
+- /gsd:plan-phase {Z+1} — skip discussion, plan directly
+- /gsd:execute-phase {Z+1} — skip to execution (if already planned)
+
+───────────────────────────────────────────────────────────────
+
+---
+
+**Route B: All tests pass, milestone complete**
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► PHASE {Z} VERIFIED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Phase {Z}: {Name}**
+
+{N}/{N} tests passed
+Final phase verified ✓
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Audit milestone** — verify requirements, cross-phase integration, E2E flows
+
+/gsd:audit-milestone
+
+<sub>/clear first → fresh context window</sub>
+
+───────────────────────────────────────────────────────────────
+
+**Also available:**
+- /gsd:complete-milestone — skip audit, archive directly
+
+───────────────────────────────────────────────────────────────
+
+---
+
+**Route C: Issues found, fix plans ready**
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► PHASE {Z} ISSUES FOUND ⚠
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Phase {Z}: {Name}**
+
+{N}/{M} tests passed
+{X} issues diagnosed
+Fix plans verified ✓
+
+### Issues Found
+
+{List issues with severity from UAT.md}
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Execute fix plans** — run diagnosed fixes
+
+/gsd:execute-phase {Z}
+
+<sub>/clear first → fresh context window</sub>
+
+───────────────────────────────────────────────────────────────
+
+**Also available:**
+- cat .planning/phases/{phase_dir}/*-PLAN.md — review fix plans
+- /gsd:plan-phase {Z} --gaps — regenerate fix plans
+
+───────────────────────────────────────────────────────────────
+
+---
+
+**Route D: Issues found, planning blocked**
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► PHASE {Z} BLOCKED ✗
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Phase {Z}: {Name}**
+
+{N}/{M} tests passed
+Fix planning blocked after {X} iterations
+
+### Unresolved Issues
+
+{List blocking issues from planner/checker output}
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Manual intervention required**
+
+Review the issues above and either:
+1. Provide guidance for fix planning
+2. Manually address blockers
+3. Accept current state and continue
+
+───────────────────────────────────────────────────────────────
+
+**Options:**
+- /gsd:plan-phase {Z} --gaps — retry fix planning with guidance
+- /gsd:discuss-phase {Z} — gather more context before replanning
+
+───────────────────────────────────────────────────────────────
+</offer_next>
+
 <success_criteria>
 - [ ] UAT.md created with tests from SUMMARY.md
 - [ ] Tests presented one at a time with expected behavior

package/get-shit-done/references/continuation-format.md

@@ -167,18 +167,12 @@ All 4 phases shipped
 
 ## ▶ Next Up
 
-**Plan v1.1** — Enhanced features and optimizations
+**Start v1.1** — questioning → research → requirements → roadmap
 
-`/gsd:discuss-milestone`
+`/gsd:new-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
----
-
-**Also available:**
-- `/gsd:new-milestone` — create directly if scope is clear
-- Review accomplishments before moving on
-
 ---
 ```
 

package/get-shit-done/references/questioning.md

@@ -16,8 +16,9 @@ Don't interrogate. Collaborate. Don't follow a script. Follow the thread.
 
 By the end of questioning, you need enough clarity to write a PROJECT.md that downstream phases can act on:
 
-- **research-project** needs: what domain to research, what the user already knows, what unknowns exist
-- **create-roadmap** needs: clear enough vision to decompose into phases, what "done" looks like
+- **Research** needs: what domain to research, what the user already knows, what unknowns exist
+- **Requirements** needs: clear enough vision to scope v1 features
+- **Roadmap** needs: clear enough vision to decompose into phases, what "done" looks like
 - **plan-phase** needs: specific requirements to break into tasks, context for implementation choices
 - **execute-phase** needs: success criteria to verify against, the "why" behind requirements
 

package/get-shit-done/templates/requirements.md

@@ -52,7 +52,7 @@ Explicitly excluded. Documented to prevent scope creep.
 
 ## Traceability
 
-Which phases cover which requirements. Updated by create-roadmap.
+Which phases cover which requirements. Updated during roadmap creation.
 
 | Requirement | Phase | Status |
 |-------------|-------|--------|
@@ -97,9 +97,9 @@ Which phases cover which requirements. Updated by create-roadmap.
 - Anti-features from research belong here with warnings
 
 **Traceability:**
-- Empty initially, populated by create-roadmap
+- Empty initially, populated during roadmap creation
 - Each requirement maps to exactly one phase
-- Unmapped requirements = roadmap gap (error in create-roadmap)
+- Unmapped requirements = roadmap gap
 
 **Status Values:**
 - Pending: Not started

package/get-shit-done/templates/research-project/SUMMARY.md

@@ -151,7 +151,7 @@ Phases with standard patterns (skip research-phase):
 
 **Implications for Roadmap:**
 - This is the most important section
-- Directly informs create-roadmap workflow
+- Directly informs roadmap creation
 - Be explicit about phase suggestions and rationale
 - Include research flags for each suggested phase
 
@@ -162,9 +162,9 @@ Phases with standard patterns (skip research-phase):
 - MEDIUM = community consensus, multiple sources agree
 - LOW = single source or inference
 
-**Integration with create-roadmap:**
-- This file is loaded as @context in create-roadmap
+**Integration with roadmap creation:**
+- This file is loaded as context during roadmap creation
 - Phase suggestions here become starting point for roadmap
-- Research flags inform detect_research_needs step
+- Research flags inform phase planning
 
 </guidelines>

package/get-shit-done/workflows/complete-milestone.md

@@ -528,7 +528,7 @@ Archive requirements and prepare for fresh requirements in next milestone.
    ✅ REQUIREMENTS.md deleted (fresh one needed for next milestone)
    ```
 
-**Important:** The next milestone workflow starts with `/gsd:define-requirements` to create a fresh REQUIREMENTS.md. PROJECT.md's Validated section carries the cumulative record across milestones.
+**Important:** The next milestone workflow starts with `/gsd:new-milestone` which includes requirements definition. PROJECT.md's Validated section carries the cumulative record across milestones.
 
 </step>
 
@@ -681,21 +681,12 @@ Tag: v[X.Y]
 
 ## ▶ Next Up
 
-**Discuss Next Milestone** — figure out what to build next
+**Start Next Milestone** — questioning → research → requirements → roadmap
 
-`/gsd:discuss-milestone`
+`/gsd:new-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
----
-
-**Next milestone flow:**
-1. `/gsd:discuss-milestone` — thinking partner, creates context file
-2. `/gsd:new-milestone` — update PROJECT.md with new goals
-3. `/gsd:research-project` — (optional) research ecosystem
-4. `/gsd:define-requirements` — scope what to build
-5. `/gsd:create-roadmap` — plan how to build it
-
 ---
 ```
 
@@ -754,6 +745,6 @@ Milestone completion is successful when:
 - [ ] STATE.md updated with fresh project reference
 - [ ] Git tag created (v[X.Y])
 - [ ] Milestone commit made (includes archive files and deletion)
-- [ ] User knows next steps (starting with /gsd:define-requirements)
+- [ ] User knows next step (/gsd:new-milestone)
 
 </success_criteria>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-shit-done-cc",
-  "version": "1.5.30",
+  "version": "1.6.0",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
   "bin": {
     "get-shit-done-cc": "bin/install.js"

package/commands/gsd/create-roadmap.md

@@ -1,145 +0,0 @@
----
-name: gsd:create-roadmap
-description: Create roadmap with phases for the project
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - AskUserQuestion
-  - Glob
-  - Task
----
-
-<!--
-DEPRECATED: This command is now integrated into /gsd:new-project
-
-The unified /gsd:new-project flow includes roadmap creation as Phase 8,
-using the gsd-roadmapper agent for heavy lifting.
-
-This standalone command is kept for users who want to:
-- Recreate roadmap after significant scope changes
-- Create roadmap for a project initialized before this integration
-- Replace an existing roadmap
-
-For new projects, use /gsd:new-project instead.
-
-Deprecated: 2026-01-16
--->
-
-<objective>
-Create project roadmap with phase breakdown.
-
-Roadmaps define what work happens in what order. Phases map to requirements.
-
-**Note:** For new projects, `/gsd:new-project` includes roadmap creation. Use this command to recreate roadmap later.
-</objective>
-
-<execution_context>
-@~/.claude/get-shit-done/workflows/create-roadmap.md
-@~/.claude/get-shit-done/templates/roadmap.md
-@~/.claude/get-shit-done/templates/state.md
-</execution_context>
-
-<context>
-@.planning/PROJECT.md
-@.planning/config.json
-@.planning/REQUIREMENTS.md
-@.planning/research/SUMMARY.md (if exists)
-</context>
-
-<process>
-
-<step name="validate">
-```bash
-# Verify project exists
-[ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md found. Run /gsd:new-project first."; exit 1; }
-
-# Verify requirements exist
-[ -f .planning/REQUIREMENTS.md ] || { echo "ERROR: No REQUIREMENTS.md found. Run /gsd:define-requirements first."; exit 1; }
-```
-</step>
-
-<step name="check_existing">
-Check if roadmap already exists:
-
-```bash
-[ -f .planning/ROADMAP.md ] && echo "ROADMAP_EXISTS" || echo "NO_ROADMAP"
-```
-
-**If ROADMAP_EXISTS:**
-Use AskUserQuestion:
-- header: "Roadmap exists"
-- question: "A roadmap already exists. What would you like to do?"
-- options:
-  - "View existing" - Show current roadmap
-  - "Replace" - Create new roadmap (will overwrite)
-  - "Cancel" - Keep existing roadmap
-
-If "View existing": `cat .planning/ROADMAP.md` and exit
-If "Cancel": Exit
-If "Replace": Continue with workflow
-</step>
-
-<step name="create_roadmap">
-Follow the create-roadmap.md workflow starting from identify_phases step.
-
-The workflow handles:
-- Loading requirements
-- Phase identification mapped to requirements
-- Requirement coverage validation (no orphaned requirements)
-- Research flags for each phase
-- Confirmation gates (respecting config mode)
-- ROADMAP.md creation with requirement mappings
-- STATE.md initialization
-- REQUIREMENTS.md traceability update
-- Phase directory creation
-- Git commit
-</step>
-
-<step name="done">
-```
-Roadmap created:
-- Roadmap: .planning/ROADMAP.md
-- State: .planning/STATE.md
-- [N] phases defined
-
----
-
-## ▶ Next Up
-
-**Phase 1: [Name]** — [Goal from ROADMAP.md]
-
-`/gsd:discuss-phase 1` — gather context and clarify approach
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/gsd:plan-phase 1` — skip discussion, plan directly
-- Review roadmap
-
----
-```
-</step>
-
-</process>
-
-<output>
-- `.planning/ROADMAP.md`
-- `.planning/STATE.md`
-- `.planning/phases/XX-name/` directories
-</output>
-
-<success_criteria>
-- [ ] PROJECT.md validated
-- [ ] REQUIREMENTS.md validated
-- [ ] All v1 requirements mapped to phases (no orphans)
-- [ ] Success criteria derived for each phase (2-5 observable behaviors)
-- [ ] Success criteria cross-checked against requirements (gaps resolved)
-- [ ] ROADMAP.md created with phases, requirement mappings, and success criteria
-- [ ] STATE.md initialized
-- [ ] REQUIREMENTS.md traceability section updated
-- [ ] Phase directories created
-- [ ] Changes committed
-</success_criteria>

package/commands/gsd/define-requirements.md

@@ -1,134 +0,0 @@
----
-name: gsd:define-requirements
-description: Define what "done" looks like with checkable requirements
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - AskUserQuestion
----
-
-<!--
-DEPRECATED: This command is now integrated into /gsd:new-project
-
-The unified /gsd:new-project flow includes requirements definition as Phase 7.
-This standalone command is kept for users who want to:
-- Redefine requirements mid-project
-- Add new requirements after initial project setup
-- Adjust v1/v2 scope boundaries
-
-For new projects, use /gsd:new-project instead.
-
-Deprecated: 2026-01-16
--->
-
-<objective>
-Define concrete, checkable requirements for v1.
-
-Two modes:
-1. **With research** — Transform FEATURES.md into scoped requirements
-2. **Without research** — Gather requirements through questioning
-
-Output: `.planning/REQUIREMENTS.md`
-
-**Note:** For new projects, `/gsd:new-project` includes requirements definition. Use this command to redefine requirements later.
-</objective>
-
-<execution_context>
-@~/.claude/get-shit-done/workflows/define-requirements.md
-@~/.claude/get-shit-done/templates/requirements.md
-</execution_context>
-
-<context>
-@.planning/PROJECT.md
-@.planning/research/FEATURES.md (if exists)
-@.planning/research/SUMMARY.md (if exists)
-</context>
-
-<process>
-
-<step name="validate">
-```bash
-# Verify project exists
-[ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md found. Run /gsd:new-project first."; exit 1; }
-
-# Check for research
-[ -f .planning/research/FEATURES.md ] && echo "HAS_RESEARCH" || echo "NO_RESEARCH"
-
-# Check if requirements already exist
-[ -f .planning/REQUIREMENTS.md ] && echo "REQUIREMENTS_EXISTS" || echo "NO_REQUIREMENTS"
-```
-</step>
-
-<step name="check_existing">
-**If REQUIREMENTS_EXISTS:**
-
-Use AskUserQuestion:
-- header: "Requirements exist"
-- question: "Requirements already defined. What would you like to do?"
-- options:
-  - "View existing" — Show current requirements
-  - "Replace" — Define requirements fresh (will overwrite)
-  - "Cancel" — Keep existing requirements
-
-If "View existing": Read and display `.planning/REQUIREMENTS.md`, then exit
-If "Cancel": Exit
-If "Replace": Continue with workflow
-</step>
-
-<step name="execute">
-**If HAS_RESEARCH:**
-Follow the define-requirements.md workflow:
-- Load research features from FEATURES.md
-- Present features by category
-- Ask user to scope each category (v1 / v2 / out of scope)
-- Capture any additions research missed
-- Generate REQUIREMENTS.md with checkable list
-
-**If NO_RESEARCH:**
-Gather requirements through questioning:
-- Read PROJECT.md for core value and context
-- Ask: "What are the main things users need to be able to do?"
-- For each capability mentioned, probe for specifics
-- Group into categories (Authentication, Content, etc.)
-- For each category, ask what's v1 vs v2 vs out of scope
-- Generate REQUIREMENTS.md with checkable list
-
-Same output format either way — the difference is source (research vs conversation).
-</step>
-
-<step name="done">
-```
-Requirements defined:
-
-- Requirements: .planning/REQUIREMENTS.md
-- v1 scope: [N] requirements across [M] categories
-- v2 scope: [X] requirements deferred
-- Out of scope: [Y] requirements excluded
-
----
-
-## ▶ Next Up
-
-**Create roadmap** — phases mapped to requirements
-
-`/gsd:create-roadmap`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] PROJECT.md validated
-- [ ] Features gathered (from research OR questioning)
-- [ ] User scoped each category (v1/v2/out of scope)
-- [ ] User had opportunity to add missing requirements
-- [ ] REQUIREMENTS.md created with checkable list
-- [ ] Requirements committed to git
-- [ ] User knows next step (create-roadmap)
-</success_criteria>

package/commands/gsd/discuss-milestone.md

@@ -1,47 +0,0 @@
----
-name: gsd:discuss-milestone
-description: Gather context for next milestone through adaptive questioning
----
-
-<objective>
-Help you figure out what to build in the next milestone through collaborative thinking.
-
-Purpose: After completing a milestone, explore what features you want to add, improve, or fix. Features first — scope and phases derive from what you want to build.
-Output: Context gathered, then routes to /gsd:new-milestone
-</objective>
-
-<execution_context>
-@~/.claude/get-shit-done/workflows/discuss-milestone.md
-</execution_context>
-
-<context>
-**Load project state first:**
-@.planning/STATE.md
-
-**Load project:**
-@.planning/PROJECT.md
-
-**Load milestones (if exists):**
-@.planning/MILESTONES.md
-</context>
-
-<process>
-1. Verify previous milestone complete (or acknowledge active milestone)
-2. Present context from previous milestone (accomplishments, phase count)
-3. Follow discuss-milestone.md workflow with **ALL questions using AskUserQuestion**:
-   - Use AskUserQuestion: "What do you want to add, improve, or fix?" with feature categories
-   - Use AskUserQuestion to dig into features they mention
-   - Use AskUserQuestion to help them articulate what matters most
-   - Use AskUserQuestion for decision gate (ready / ask more / let me add context)
-4. Hand off to /gsd:new-milestone with gathered context
-
-**CRITICAL: ALL questions use AskUserQuestion. Never ask inline text questions.**
-</process>
-
-<success_criteria>
-
-- Project state loaded and presented
-- Previous milestone context summarized
-- Milestone scope gathered through adaptive questioning
-- Context handed off to /gsd:new-milestone
-  </success_criteria>