pi-gsd 2.0.21 → 2.0.22

package/.gsd/harnesses/pi/get-shit-done/workflows/add-backlog.md

@@ -0,0 +1,132 @@
+<gsd-version v="1.12.4" />
+
+<gsd-arguments>
+  <settings>
+    <keep-extra-args />
+  </settings>
+  <arg name="idea" type="string" optional />
+</gsd-arguments>
+
+<gsd-execute>
+  <display msg="Loading backlog context..." />
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="state" />
+      <arg string="json" />
+      <arg string="--raw" />
+    </args>
+    <outs>
+      <suppress-errors />
+      <out type="string" name="state" />
+    </outs>
+  </shell>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="roadmap" />
+      <arg string="analyze" />
+      <arg string="--raw" />
+    </args>
+    <outs>
+      <suppress-errors />
+      <out type="string" name="roadmap" />
+    </outs>
+  </shell>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="current-timestamp" />
+      <arg string="--raw" />
+    </args>
+    <outs>
+      <out type="string" name="timestamp" />
+    </outs>
+  </shell>
+</gsd-execute>
+
+## Backlog Context (pre-injected by WXP)
+
+**Idea:** <gsd-paste name="idea" />
+
+**Timestamp:** <gsd-paste name="timestamp" />
+
+**State:**
+<gsd-paste name="state" />
+
+**Roadmap Analysis:**
+<gsd-paste name="roadmap" />
+
+---
+
+<purpose>
+Park an idea as a backlog entry (999.x numbered phase) in ROADMAP.md. Zero friction — one command captures an idea without interrupting current work. The idea sits in the backlog until promoted by `/gsd-review-backlog`.
+</purpose>
+
+<process>
+
+<step name="validate_context">
+<!-- State, roadmap, and idea pre-injected above via WXP -->
+
+Check that `.planning/ROADMAP.md` exists (from `state` JSON field `roadmap_exists`).
+
+**If roadmap missing:**
+```
+Error: No ROADMAP.md found. Run /gsd-new-project or /gsd-new-milestone first.
+```
+Exit.
+
+**If idea is empty (no $ARGUMENTS):**
+Ask the user: "What's the idea? (one sentence description)"
+Use the response as `idea`.
+</step>
+
+<step name="find_next_slot">
+From the roadmap analysis JSON, extract the `phases` array. Find all phases where `phase_number` starts with `999` (e.g., `999.1`, `999.2`).
+
+Compute next backlog number:
+- If no 999.x entries exist → use `999.1`
+- Otherwise → use `999.(max_decimal + 1)`, e.g., if `999.3` exists → `999.4`
+
+Set `BACKLOG_NUM` = next available 999.x slot.
+</step>
+
+<step name="add_entry">
+Append to `.planning/ROADMAP.md` under a `## Backlog` section (create the section if missing):
+
+```markdown
+- [ ] **Phase {BACKLOG_NUM}**: {idea}
+```
+
+Use the roadmap `roadmap add-phase` command if available, or append directly:
+
+```bash
+pi-gsd-tools roadmap add-phase "{BACKLOG_NUM}" "{idea}" --raw
+```
+
+If the CLI command fails or is unavailable, append manually to ROADMAP.md.
+</step>
+
+<step name="commit">
+```bash
+pi-gsd-tools commit "docs: add backlog entry {BACKLOG_NUM} - {idea_slug}" --files .planning/ROADMAP.md
+```
+</step>
+
+<step name="confirm">
+```
+✓ Backlog entry added
+
+  Phase {BACKLOG_NUM}: {idea}
+
+---
+
+Review and promote backlog: /gsd-review-backlog
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] ROADMAP.md has new 999.x entry
+- [ ] 999.x number is sequential (no gaps or duplicates)
+- [ ] Entry committed to git
+- [ ] User sees confirmation with the assigned phase number
+</success_criteria>

package/.gsd/harnesses/pi/get-shit-done/workflows/debug.md

@@ -0,0 +1,250 @@
+<gsd-version v="1.12.4" />
+
+<gsd-arguments>
+  <settings>
+    <keep-extra-args />
+  </settings>
+  <arg name="description" type="string" optional />
+</gsd-arguments>
+
+<gsd-execute>
+  <display msg="Loading debug context..." />
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="state" />
+      <arg string="json" />
+      <arg string="--raw" />
+    </args>
+    <outs>
+      <suppress-errors />
+      <out type="string" name="state" />
+    </outs>
+  </shell>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="current-timestamp" />
+      <arg string="--raw" />
+    </args>
+    <outs>
+      <out type="string" name="timestamp" />
+    </outs>
+  </shell>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="agent-skills" />
+      <arg string="gsd-debugger" />
+    </args>
+    <outs>
+      <suppress-errors />
+      <out type="string" name="agent-skills-debugger" />
+    </outs>
+  </shell>
+</gsd-execute>
+
+## Debug Context (pre-injected by WXP)
+
+**Problem:** <gsd-paste name="description" />
+
+**Timestamp:** <gsd-paste name="timestamp" />
+
+**Project State:**
+<gsd-paste name="state" />
+
+**Debugger Skills:**
+<gsd-paste name="agent-skills-debugger" />
+
+---
+
+<purpose>
+Systematic debugging session. Diagnoses failures, errors, and unexpected behavior using structured root-cause analysis. Spawns gsd-debugger with full project context for focused investigation.
+
+For post-mortem investigation of completed phases, use `/gsd-forensics` instead.
+</purpose>
+
+<available_agent_types>
+Valid GSD subagent types (use exact names - do not fall back to 'general-purpose'):
+- gsd-debugger - Diagnoses and fixes issues
+</available_agent_types>
+
+<process>
+
+<step name="gather_context">
+<!-- State, timestamp, and description pre-injected above via WXP -->
+
+Load current phase context:
+
+```bash
+PHASE_INFO=$(pi-gsd-tools roadmap analyze --raw 2>/dev/null || echo "{}")
+```
+
+Extract from state JSON:
+- `current_phase` - what's being worked on
+- `last_activity` - when was the last change
+- `milestone` - current milestone name
+
+If `description` is empty, ask the user:
+```
+What's broken? Describe the symptom in one sentence:
+(e.g. "auth tokens expire immediately", "build fails with missing module", "tests pass locally but fail in CI")
+```
+Store response as `description`.
+</step>
+
+<step name="classify_issue">
+Classify the issue from the description:
+
+| Symptom pattern | Issue type |
+|----------------|------------|
+| Error/exception message | `runtime_error` |
+| Test failures | `test_failure` |
+| Build/compile error | `build_error` |
+| Wrong behavior (no error) | `logic_error` |
+| Performance problem | `performance` |
+| Integration failure | `integration` |
+| Unclear | `unknown` |
+
+Set `ISSUE_TYPE`.
+</step>
+
+<step name="spawn_debugger">
+Display banner:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► DEBUG SESSION
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Issue: {description}
+Type:  {ISSUE_TYPE}
+Phase: {current_phase || "not set"}
+
+◆ Spawning debugger...
+```
+
+Resolve model:
+```bash
+DEBUGGER_MODEL=$(pi-gsd-tools resolve-model gsd-debugger --raw 2>/dev/null || echo "")
+```
+
+Debug prompt:
+```markdown
+<objective>
+Debug the following issue in this project:
+{description}
+
+Issue type: {ISSUE_TYPE}
+Current phase: {current_phase}
+Milestone: {milestone}
+</objective>
+
+<files_to_read>
+- .planning/STATE.md (Project state and recent decisions)
+- .planning/ROADMAP.md (Phase context)
+- ./GEMINI.md or ./CLAUDE.md (Project-specific guidelines, if exists)
+</files_to_read>
+
+${AGENT_SKILLS_DEBUGGER}
+
+<investigation_protocol>
+1. Reproduce: Identify the minimal steps to trigger the issue
+2. Isolate: Narrow down to the failing component/file/function
+3. Root cause: Identify WHY it fails, not just WHERE
+4. Fix: Implement the smallest change that solves the root cause
+5. Verify: Confirm the fix works and doesn't introduce regressions
+
+Always check:
+- Recent commits (git log --oneline -10) for what changed
+- Related files for mismatched interfaces or broken contracts
+- Test suite for existing coverage that should have caught this
+</investigation_protocol>
+
+<output_format>
+## DEBUG COMPLETE
+
+**Root cause:** [one sentence]
+**Fix applied:** [what was changed]
+**Files modified:** [list]
+**Verification:** [how to confirm it's fixed]
+
+OR
+
+## DEBUG BLOCKED
+
+**Investigated:** [what was tried]
+**Blocker:** [what additional info is needed]
+**Next step:** [what the human should provide or check]
+</output_format>
+```
+
+```
+Task(
+  prompt=debug_prompt,
+  subagent_type="gsd-debugger",
+  model="{DEBUGGER_MODEL}",
+  description="Debug: {description}"
+)
+```
+</step>
+
+<step name="handle_return">
+**`## DEBUG COMPLETE`:**
+
+Display root cause, fix, and verification steps. Offer:
+```
+1. Capture as todo (/gsd-add-todo) - if fix not yet applied
+2. Continue with current phase (/gsd-execute-phase)
+3. Done
+```
+
+**`## DEBUG BLOCKED`:**
+
+Display blocker and next steps. Offer:
+```
+1. Provide additional context and retry
+2. Try forensics mode (/gsd-forensics) - deeper investigation
+3. Capture as todo and investigate later
+```
+</step>
+
+<step name="persist_session">
+If the debug session produced a fix or useful findings, offer to save:
+
+```bash
+mkdir -p .planning/debug
+```
+
+Write `.planning/debug/{YYYY-MM-DD}-{slug}.md`:
+```markdown
+---
+created: {timestamp}
+issue: {description}
+type: {ISSUE_TYPE}
+phase: {current_phase}
+status: {resolved|blocked}
+---
+
+## Root Cause
+{root cause summary}
+
+## Fix
+{what was changed}
+
+## Verification
+{how to confirm}
+```
+
+Commit:
+```bash
+pi-gsd-tools commit "docs: debug session - {description_slug}" --files .planning/debug/{filename}
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Problem description captured (from arg or prompt)
+- [ ] Issue classified by type
+- [ ] gsd-debugger spawned with full project context
+- [ ] Root cause identified or blocker surfaced
+- [ ] Fix applied or next steps clear
+- [ ] Session optionally persisted in .planning/debug/
+</success_criteria>

package/.gsd/harnesses/pi/get-shit-done/workflows/execute-phase.md

@@ -8,6 +8,9 @@
     </delimiters>
   </settings>
   <arg name="auto-chain-active" type="flag" flag="--auto" optional />
+  <arg name="no-transition" type="flag" flag="--no-transition" optional />
+  <arg name="gaps-only" type="flag" flag="--gaps-only" optional />
+  <arg name="interactive" type="flag" flag="--interactive" optional />
   <arg name="phase" type="number" />
   <arg name="user-text" type="string" optional />
 </gsd-arguments>

package/.gsd/harnesses/pi/get-shit-done/workflows/list-phase-assumptions.md

@@ -1,5 +1,75 @@
 <gsd-version v="1.12.4" />
 
+<gsd-arguments>
+  <settings>
+    <keep-extra-args />
+  </settings>
+  <arg name="phase" type="number" />
+</gsd-arguments>
+
+<gsd-execute>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="init" />
+      <arg string="phase-op" />
+      <arg name="phase" wrap='"' />
+    </args>
+    <outs>
+      <out type="string" name="init" />
+    </outs>
+  </shell>
+  <if>
+    <condition>
+      <starts-with>
+        <left name="init" />
+        <right type="string" value="@file:" />
+      </starts-with>
+    </condition>
+    <then>
+      <string-op op="split">
+        <args>
+          <arg name="init" />
+          <arg type="string" value="@file:" />
+        </args>
+        <outs>
+          <out type="string" name="init-file" />
+        </outs>
+      </string-op>
+      <shell command="cat">
+        <args>
+          <arg name="init-file" wrap='"' />
+        </args>
+        <outs>
+          <out type="string" name="init" />
+        </outs>
+      </shell>
+    </then>
+  </if>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="state" />
+      <arg string="json" />
+      <arg string="--raw" />
+    </args>
+    <outs>
+      <suppress-errors />
+      <out type="string" name="state" />
+    </outs>
+  </shell>
+</gsd-execute>
+
+## Context (pre-injected by WXP)
+
+**Phase:** <gsd-paste name="phase" />
+
+**Phase Data:**
+<gsd-paste name="init" />
+
+**State:**
+<gsd-paste name="state" />
+
+---
+
 <purpose>
 Surface the agent's assumptions about a phase before planning, enabling users to correct misconceptions early.
 
@@ -9,46 +79,24 @@ Key difference from discuss-phase: This is ANALYSIS of what the agent thinks, no
 <process>
 
 <step name="validate_phase" priority="first">
-Phase number: $ARGUMENTS (required)
+<!-- Phase number, phase data and state are pre-injected above via WXP -->
 
-**If argument missing:**
+Parse `init` JSON for: `phase_found`, `phase_number`, `phase_name`, `phase_slug`, `goal`, `phase_dir`.
 
-```
-Error: Phase number required.
+**If `phase_found` is false:**
 
-Usage: /gsd-list-phase-assumptions [phase-number]
-Example: /gsd-list-phase-assumptions 3
 ```
+Error: Phase {phase} not found in roadmap.
 
-Exit workflow.
-
-**If argument provided:**
-Validate phase exists in roadmap:
+Available phases: [list from roadmap]
 
-```bash
-cat .planning/ROADMAP.md | grep -i "Phase ${PHASE}"
-```
-
-**If phase not found:**
-
-```
-Error: Phase ${PHASE} not found in roadmap.
-
-Available phases:
-[list phases from roadmap]
+Usage: /gsd-list-phase-assumptions [phase-number]
+Example: /gsd-list-phase-assumptions 3
 ```
 
 Exit workflow.
 
-**If phase found:**
-Parse phase details from roadmap:
-
-- Phase number
-- Phase name
-- Phase description/goal
-- Any scope details mentioned
-
-Continue to analyze_phase.
+**If `phase_found` is true:** Continue to analyze_phase.
 </step>
 
 <step name="analyze_phase">

package/.gsd/harnesses/pi/get-shit-done/workflows/plan-phase.md

@@ -6,6 +6,10 @@
   </settings>
   <arg name="auto-chain-active" type="flag" flag="--auto" optional />
   <arg name="skip-research" type="flag" flag="--skip-research" optional />
+  <arg name="gaps" type="flag" flag="--gaps" optional />
+  <arg name="skip-verify" type="flag" flag="--skip-verify" optional />
+  <arg name="reviews" type="flag" flag="--reviews" optional />
+  <arg name="text" type="flag" flag="--text" optional />
   <arg name="phase" type="number" />
 </gsd-arguments>