get-shit-done-cc 1.5.29 → 1.6.0

package/get-shit-done/workflows/verify-work.md

@@ -334,28 +334,180 @@ Spawning parallel debug agents to investigate each issue.
 - Spawn parallel debug agents for each issue
 - Collect root causes
 - Update UAT.md with root causes
-- Proceed to `offer_gap_closure`
+- Proceed to `plan_gap_closure`
 
 Diagnosis runs automatically - no user prompt. Parallel agents investigate simultaneously, so overhead is minimal and fixes are more accurate.
 </step>
 
-<step name="offer_gap_closure">
-**Offer next steps after diagnosis:**
+<step name="plan_gap_closure">
+**Auto-plan fixes from diagnosed gaps:**
 
+Display:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► PLANNING FIXES
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+◆ Spawning planner for gap closure...
 ```
----
 
-## Diagnosis Complete
+Spawn gsd-planner in --gaps mode:
 
-| Gap | Root Cause |
-|-----|------------|
-| {truth 1} | {root_cause} |
-| {truth 2} | {root_cause} |
-...
+```
+Task(
+  prompt="""
+<planning_context>
+
+**Phase:** {phase_number}
+**Mode:** gap_closure
+
+**UAT with diagnoses:**
+@.planning/phases/{phase_dir}/{phase}-UAT.md
+
+**Project State:**
+@.planning/STATE.md
+
+**Roadmap:**
+@.planning/ROADMAP.md
+
+</planning_context>
+
+<downstream_consumer>
+Output consumed by /gsd:execute-phase
+Plans must be executable prompts.
+</downstream_consumer>
+""",
+  subagent_type="gsd-planner",
+  description="Plan gap fixes for Phase {phase}"
+)
+```
+
+On return:
+- **PLANNING COMPLETE:** Proceed to `verify_gap_plans`
+- **PLANNING INCONCLUSIVE:** Report and offer manual intervention
+</step>
+
+<step name="verify_gap_plans">
+**Verify fix plans with checker:**
+
+Display:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► VERIFYING FIX PLANS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+◆ Spawning plan checker...
+```
+
+Initialize: `iteration_count = 1`
+
+Spawn gsd-plan-checker:
+
+```
+Task(
+  prompt="""
+<verification_context>
+
+**Phase:** {phase_number}
+**Phase Goal:** Close diagnosed gaps from UAT
+
+**Plans to verify:**
+@.planning/phases/{phase_dir}/*-PLAN.md
+
+</verification_context>
+
+<expected_output>
+Return one of:
+- ## VERIFICATION PASSED — all checks pass
+- ## ISSUES FOUND — structured issue list
+</expected_output>
+""",
+  subagent_type="gsd-plan-checker",
+  description="Verify Phase {phase} fix plans"
+)
+```
+
+On return:
+- **VERIFICATION PASSED:** Proceed to `present_ready`
+- **ISSUES FOUND:** Proceed to `revision_loop`
+</step>
+
+<step name="revision_loop">
+**Iterate planner ↔ checker until plans pass (max 3):**
+
+**If iteration_count < 3:**
+
+Display: `Sending back to planner for revision... (iteration {N}/3)`
+
+Spawn gsd-planner with revision context:
+
+```
+Task(
+  prompt="""
+<revision_context>
+
+**Phase:** {phase_number}
+**Mode:** revision
+
+**Existing plans:**
+@.planning/phases/{phase_dir}/*-PLAN.md
+
+**Checker issues:**
+{structured_issues_from_checker}
+
+</revision_context>
+
+<instructions>
+Read existing PLAN.md files. Make targeted updates to address checker issues.
+Do NOT replan from scratch unless issues are fundamental.
+</instructions>
+""",
+  subagent_type="gsd-planner",
+  description="Revise Phase {phase} plans"
+)
+```
+
+After planner returns → spawn checker again (verify_gap_plans logic)
+Increment iteration_count
+
+**If iteration_count >= 3:**
+
+Display: `Max iterations reached. {N} issues remain.`
+
+Offer options:
+1. Force proceed (execute despite issues)
+2. Provide guidance (user gives direction, retry)
+3. Abandon (exit, user runs /gsd:plan-phase manually)
+
+Wait for user response.
+</step>
+
+<step name="present_ready">
+**Present completion and next steps:**
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► FIXES READY ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Phase {X}: {Name}** — {N} gap(s) diagnosed, {M} fix plan(s) created
+
+| Gap | Root Cause | Fix Plan |
+|-----|------------|----------|
+| {truth 1} | {root_cause} | {phase}-04 |
+| {truth 2} | {root_cause} | {phase}-04 |
+
+Plans verified and ready for execution.
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Execute fixes** — run fix plans
+
+`/clear` then `/gsd:execute-phase {phase}`
 
-Next steps:
-- `/gsd:plan-phase {phase} --gaps` — Create fix plans from diagnosed gaps
-- `/gsd:verify-work {phase}` — Re-test after fixes
+───────────────────────────────────────────────────────────────
 ```
 </step>
 
@@ -403,5 +555,9 @@ Default to **major** if unclear. User can correct if needed.
 - [ ] Severity inferred from description (never asked)
 - [ ] Batched writes: on issue, every 5 passes, or completion
 - [ ] Committed on completion
-- [ ] Clear next steps based on results (plan-phase --gaps if issues)
+- [ ] If issues: parallel debug agents diagnose root causes
+- [ ] If issues: gsd-planner creates fix plans (gap_closure mode)
+- [ ] If issues: gsd-plan-checker verifies fix plans
+- [ ] If issues: revision loop until plans pass (max 3 iterations)
+- [ ] Ready for `/gsd:execute-phase` when complete
 </success_criteria>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-shit-done-cc",
-  "version": "1.5.29",
+  "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:plan-phase 1`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/gsd:discuss-phase 1` — gather context first
-- 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>