@undeemed/get-shit-done-codex 1.20.10 → 1.22.0

package/get-shit-done/workflows/add-tests.md

@@ -1,7 +1,7 @@
 <purpose>
 Generate unit and E2E tests for a completed phase based on its SUMMARY.md, CONTEXT.md, and implementation. Classifies each changed file into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
 
-Users currently hand-craft `/gsd:quick` prompts for test generation after each phase. This workflow standardizes the process with proper classification, quality gates, and gap reporting.
+Users currently hand-craft `$gsd-quick` prompts for test generation after each phase. This workflow standardizes the process with proper classification, quality gates, and gap reporting.
 </purpose>
 
 <required_reading>
@@ -15,15 +15,15 @@ Parse `$ARGUMENTS` for:
 - Phase number (integer, decimal, or letter-suffix) → store as `$PHASE_ARG`
 - Remaining text after phase number → store as `$EXTRA_INSTRUCTIONS` (optional)
 
-Example: `/gsd:add-tests 12 focus on edge cases` → `$PHASE_ARG=12`, `$EXTRA_INSTRUCTIONS="focus on edge cases"`
+Example: `$gsd-add-tests 12 focus on edge cases` → `$PHASE_ARG=12`, `$EXTRA_INSTRUCTIONS="focus on edge cases"`
 
 If no phase argument provided:
 
 ```
 ERROR: Phase number required
-Usage: /gsd:add-tests <phase> [additional instructions]
-Example: /gsd:add-tests 12
-Example: /gsd:add-tests 12 focus on edge cases in the pricing module
+Usage: $gsd-add-tests <phase> [additional instructions]
+Example: $gsd-add-tests 12
+Example: $gsd-add-tests 12 focus on edge cases in the pricing module
 ```
 
 Exit.
@@ -33,36 +33,43 @@ Exit.
 Load phase operation context:
 
 ```bash
-INIT=$(node ~/.claude/get-shit-done/bin/gsd-tools.cjs init phase-op "${PHASE_ARG}")
+INIT=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs init phase-op "${PHASE_ARG}")
 ```
 
 Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`.
 
 Verify the phase directory exists. If not:
+
 ```
 ERROR: Phase directory not found for phase ${PHASE_ARG}
 Ensure the phase exists in .planning/phases/
 ```
+
 Exit.
 
 Read the phase artifacts (in order of priority):
+
 1. `${phase_dir}/*-SUMMARY.md` — what was implemented, files changed
 2. `${phase_dir}/CONTEXT.md` — acceptance criteria, decisions
 3. `${phase_dir}/*-VERIFICATION.md` — user-verified scenarios (if UAT was done)
 
 If no SUMMARY.md exists:
+
 ```
 ERROR: No SUMMARY.md found for phase ${PHASE_ARG}
-This command works on completed phases. Run /gsd:execute-phase first.
+This command works on completed phases. Run $gsd-execute-phase first.
 ```
+
 Exit.
 
 Present banner:
+
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  GSD ► ADD TESTS — Phase ${phase_number}: ${phase_name}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
+
 </step>
 
 <step name="analyze_implementation">
@@ -70,13 +77,14 @@ Extract the list of files modified by the phase from SUMMARY.md ("Files Changed"
 
 For each file, classify into one of three categories:
 
-| Category | Criteria | Test Type |
-|----------|----------|-----------|
-| **TDD** | Pure functions where `expect(fn(input)).toBe(output)` is writable | Unit tests |
-| **E2E** | UI behavior verifiable by browser automation | Playwright/E2E tests |
-| **Skip** | Not meaningfully testable or already covered | None |
+| Category | Criteria                                                          | Test Type            |
+| -------- | ----------------------------------------------------------------- | -------------------- |
+| **TDD**  | Pure functions where `expect(fn(input)).toBe(output)` is writable | Unit tests           |
+| **E2E**  | UI behavior verifiable by browser automation                      | Playwright/E2E tests |
+| **Skip** | Not meaningfully testable or already covered                      | None                 |
 
 **TDD classification — apply when:**
+
 - Business logic: calculations, pricing, tax rules, validation
 - Data transformations: mapping, filtering, aggregation, formatting
 - Parsers: CSV, JSON, XML, custom format parsing
@@ -85,6 +93,7 @@ For each file, classify into one of three categories:
 - Utilities: string manipulation, date handling, number formatting
 
 **E2E classification — apply when:**
+
 - Keyboard shortcuts: key bindings, modifier keys, chord sequences
 - Navigation: page transitions, routing, breadcrumbs, back/forward
 - Form interactions: submit, validation errors, field focus, autocomplete
@@ -94,6 +103,7 @@ For each file, classify into one of three categories:
 - Data grids: sorting, filtering, inline editing, column resize
 
 **Skip classification — apply when:**
+
 - UI layout/styling: CSS classes, visual appearance, responsive breakpoints
 - Configuration: config files, environment variables, feature flags
 - Glue code: dependency injection setup, middleware registration, routing tables
@@ -149,12 +159,14 @@ ls package.json *.sln 2>/dev/null
 ```
 
 Identify:
+
 - Test directory structure (where unit tests live, where E2E tests live)
 - Naming conventions (`.test.ts`, `.spec.ts`, `*Tests.fs`, etc.)
 - Test runner commands (how to execute unit tests, how to execute E2E tests)
 - Test framework (xUnit, NUnit, Jest, Playwright, etc.)
 
 If test structure is ambiguous, ask the user:
+
 ```
 AskUserQuestion(
   header: "Test Structure",
@@ -162,17 +174,20 @@ AskUserQuestion(
   options: [list discovered locations]
 )
 ```
+
 </step>
 
 <step name="generate_test_plan">
 For each approved file, create a detailed test plan.
 
 **For TDD files**, plan tests following RED-GREEN-REFACTOR:
+
 1. Identify testable functions/methods in the file
 2. For each function: list input scenarios, expected outputs, edge cases
 3. Note: since code already exists, tests may pass immediately — that's OK, but verify they test the RIGHT behavior
 
 **For E2E files**, plan tests following RED-GREEN gates:
+
 1. Identify user scenarios from CONTEXT.md/VERIFICATION.md
 2. For each scenario: describe the user action, expected outcome, assertions
 3. Note: RED gate means confirming the test would fail if the feature were broken
@@ -213,6 +228,7 @@ For each approved TDD test:
 1. **Create test file** following discovered project conventions (directory, naming, imports)
 
 2. **Write test** with clear arrange/act/assert structure:
+
    ```
    // Arrange — set up inputs and expected outputs
    // Act — call the function under test
@@ -220,6 +236,7 @@ For each approved TDD test:
    ```
 
 3. **Run the test**:
+
    ```bash
    {discovered test command}
    ```
@@ -235,20 +252,23 @@ For each approved TDD test:
      ```
      Do NOT fix the implementation — this is a test-generation command, not a fix command. Record the finding.
    - **Test fails with error (import, syntax, etc.)**: This is a test error. Fix the test and re-run.
-</step>
+     </step>
 
 <step name="execute_e2e_generation">
 For each approved E2E test:
 
 1. **Check for existing tests** covering the same scenario:
+
    ```bash
    grep -r "{scenario keyword}" {e2e test directory} 2>/dev/null
    ```
+
    If found, extend rather than duplicate.
 
 2. **Create test file** targeting the user scenario from CONTEXT.md/VERIFICATION.md
 
 3. **Run the E2E test**:
+
    ```bash
    {discovered e2e command}
    ```
@@ -295,8 +315,9 @@ Create a test coverage report and present to user:
 ```
 
 Record test generation in project state:
+
 ```bash
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs state-snapshot
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs state-snapshot
 ```
 
 If there are passing tests to commit:
@@ -314,7 +335,7 @@ Present next steps:
 ## ▶ Next Up
 
 {if bugs discovered:}
-**Fix discovered bugs:** `/gsd:quick fix the {N} test failures discovered in phase ${phase_number}`
+**Fix discovered bugs:** `$gsd-quick fix the {N} test failures discovered in phase ${phase_number}`
 
 {if blocked tests:}
 **Resolve test blockers:** {description of what's needed}
@@ -325,16 +346,18 @@ Present next steps:
 ---
 
 **Also available:**
-- `/gsd:add-tests {next_phase}` — test another phase
-- `/gsd:verify-work {phase_number}` — run UAT verification
+- `$gsd-add-tests {next_phase}` — test another phase
+- `$gsd-verify-work {phase_number}` — run UAT verification
 
 ---
 ```
+
 </step>
 
 </process>
 
 <success_criteria>
+
 - [ ] Phase artifacts loaded (SUMMARY.md, CONTEXT.md, optionally VERIFICATION.md)
 - [ ] All changed files classified into TDD/E2E/Skip categories
 - [ ] Classification presented to user and approved
@@ -347,4 +370,4 @@ Present next steps:
 - [ ] Test files committed with proper message
 - [ ] Coverage gaps documented
 - [ ] Next steps presented to user
-</success_criteria>
+      </success_criteria>

package/get-shit-done/workflows/add-todo.md

@@ -27,7 +27,7 @@ Note existing areas from the todos array for consistency in infer_area step.
 
 <step name="extract_content">
 **With arguments:** Use as the title/focus.
-- `/gsd:add-todo Add auth token refresh` → title = "Add auth token refresh"
+- `$gsd-add-todo Add auth token refresh` → title = "Add auth token refresh"
 
 **Without arguments:** Analyze recent conversation to extract:
 - The specific problem, idea, or task discussed
@@ -140,7 +140,7 @@ Would you like to:
 
 1. Continue with current work
 2. Add another todo
-3. View all todos (/gsd:check-todos)
+3. View all todos ($gsd-check-todos)
 ```
 </step>
 

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

@@ -196,7 +196,7 @@ All requirements covered. Cross-phase integration verified. E2E flows complete.
 
 **Complete milestone** — archive and tag
 
-/gsd:complete-milestone {version}
+$gsd-complete-milestone {version}
 
 <sub>/clear first → fresh context window</sub>
 
@@ -233,7 +233,7 @@ All requirements covered. Cross-phase integration verified. E2E flows complete.
 
 **Plan gap closure** — create phases to complete milestone
 
-/gsd:plan-milestone-gaps
+$gsd-plan-milestone-gaps
 
 <sub>/clear first → fresh context window</sub>
 
@@ -241,7 +241,7 @@ All requirements covered. Cross-phase integration verified. E2E flows complete.
 
 **Also available:**
 - cat .planning/v{version}-MILESTONE-AUDIT.md — see full report
-- /gsd:complete-milestone {version} — proceed anyway (accept tech debt)
+- $gsd-complete-milestone {version} — proceed anyway (accept tech debt)
 
 ───────────────────────────────────────────────────────────────
 
@@ -271,11 +271,11 @@ All requirements met. No critical blockers. Accumulated tech debt needs review.
 
 **A. Complete milestone** — accept debt, track in backlog
 
-/gsd:complete-milestone {version}
+$gsd-complete-milestone {version}
 
 **B. Plan cleanup phase** — address debt before completing
 
-/gsd:plan-milestone-gaps
+$gsd-plan-milestone-gaps
 
 <sub>/clear first → fresh context window</sub>
 

package/get-shit-done/workflows/check-todos.md

@@ -21,14 +21,14 @@ If `todo_count` is 0:
 ```
 No pending todos.
 
-Todos are captured during work sessions with /gsd:add-todo.
+Todos are captured during work sessions with $gsd-add-todo.
 
 ---
 
 Would you like to:
 
-1. Continue with current phase (/gsd:progress)
-2. Add a todo now (/gsd:add-todo)
+1. Continue with current phase ($gsd-progress)
+2. Add a todo now ($gsd-add-todo)
 ```
 
 Exit.
@@ -36,8 +36,8 @@ Exit.
 
 <step name="parse_filter">
 Check for area filter in arguments:
-- `/gsd:check-todos` → show all
-- `/gsd:check-todos api` → filter to area:api only
+- `$gsd-check-todos` → show all
+- `$gsd-check-todos api` → filter to area:api only
 </step>
 
 <step name="list_todos">
@@ -55,7 +55,7 @@ Pending Todos:
 ---
 
 Reply with a number to view details, or:
-- `/gsd:check-todos [area]` to filter by area
+- `$gsd-check-todos [area]` to filter by area
 - `q` to exit
 ```
 
@@ -117,7 +117,7 @@ Use AskUserQuestion:
 - question: "What would you like to do with this todo?"
 - options:
   - "Work on it now" — move to done, start working
-  - "Create a phase" — /gsd:add-phase with this scope
+  - "Create a phase" — $gsd-add-phase with this scope
   - "Brainstorm approach" — think through before deciding
   - "Put it back" — return to list
 </step>
@@ -133,7 +133,7 @@ Update STATE.md todo count. Present problem/solution context. Begin work or ask
 Note todo reference in phase planning notes. Keep in pending. Return to list or exit.
 
 **Create a phase:**
-Display: `/gsd:add-phase [description from todo]`
+Display: `$gsd-add-phase [description from todo]`
 Keep in pending. User runs command in fresh context.
 
 **Brainstorm approach:**

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

@@ -44,6 +44,7 @@ ROADMAP=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs roadmap analyze)
 ```
 
 This returns all phases with plan/summary counts and disk status. Use this to verify:
+
 - Which phases belong to this milestone?
 - All phases complete (all plans have summaries)? Check `disk_status === 'complete'` for each.
 - `progress_percent` should be 100%.
@@ -51,6 +52,7 @@ This returns all phases with plan/summary counts and disk status. Use this to ve
 **Requirements completion check (REQUIRED before presenting):**
 
 Parse REQUIREMENTS.md traceability table:
+
 - Count total v1 requirements vs checked-off (`[x]`) requirements
 - Identify any non-Complete rows in the traceability table
 
@@ -79,8 +81,9 @@ Requirements: {N}/{M} v1 requirements checked off
 ```
 
 MUST present 3 options:
+
 1. **Proceed anyway** — mark milestone complete with known gaps
-2. **Run audit first** — `/gsd:audit-milestone` to assess gap severity
+2. **Run audit first** — `$gsd-audit-milestone` to assess gap severity
 3. **Abort** — return to development
 
 If user selects "Proceed anyway": note incomplete requirements in MILESTONES.md under `### Known Gaps` with REQ-IDs and descriptions.
@@ -113,6 +116,7 @@ Ready to mark this milestone as shipped?
 ```
 
 Wait for confirmation.
+
 - "adjust scope": Ask which phases to include.
 - "wait": Stop, user returns when ready.
 
@@ -232,7 +236,8 @@ Update PROJECT.md inline. Update "Last updated" footer:
 
 ```markdown
 ---
-*Last updated: [date] after v[X.Y] milestone*
+
+_Last updated: [date] after v[X.Y] milestone_
 ```
 
 **Example full evolution (v1.0 → v1.1 prep):**
@@ -371,6 +376,7 @@ ARCHIVE=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs milestone complete "v[X.
 ```
 
 The CLI handles:
+
 - Creating `.planning/milestones/` directory
 - Archiving ROADMAP.md to `milestones/v[X.Y]-ROADMAP.md`
 - Archiving REQUIREMENTS.md to `milestones/v[X.Y]-REQUIREMENTS.md` with archive header
@@ -387,16 +393,19 @@ Verify: `✅ Milestone archived to .planning/milestones/`
 AskUserQuestion(header="Archive Phases", question="Archive phase directories to milestones/?", options: "Yes — move to milestones/v[X.Y]-phases/" | "Skip — keep phases in place")
 
 If "Yes": move phase directories to the milestone archive:
+
 ```bash
 mkdir -p .planning/milestones/v[X.Y]-phases
 # For each phase directory in .planning/phases/:
 mv .planning/phases/{phase-dir} .planning/milestones/v[X.Y]-phases/
 ```
+
 Verify: `✅ Phase directories archived to .planning/milestones/v[X.Y]-phases/`
 
-If "Skip": Phase directories remain in `.planning/phases/` as raw execution history. Use `/gsd:cleanup` later to archive retroactively.
+If "Skip": Phase directories remain in `.planning/phases/` as raw execution history. Use `$gsd-cleanup` later to archive retroactively.
 
 After archival, the AI still handles:
+
 - Reorganizing ROADMAP.md with milestone grouping (requires judgment)
 - Full PROJECT.md evolution review (requires understanding)
 - Deleting original ROADMAP.md and REQUIREMENTS.md
@@ -443,13 +452,14 @@ rm .planning/REQUIREMENTS.md
 **Append to living retrospective:**
 
 Check for existing retrospective:
+
 ```bash
 ls .planning/RETROSPECTIVE.md 2>/dev/null
 ```
 
 **If exists:** Read the file, append new milestone section before the "## Cross-Milestone Trends" section.
 
-**If doesn't exist:** Create from template at `~/.claude/get-shit-done/templates/retrospective.md`.
+**If doesn't exist:** Create from template at `~/.codex/get-shit-done/templates/retrospective.md`.
 
 **Gather retrospective data:**
 
@@ -468,22 +478,28 @@ ls .planning/RETROSPECTIVE.md 2>/dev/null
 **Phases:** {phase_count} | **Plans:** {plan_count}
 
 ### What Was Built
+
 {Extract from SUMMARY.md one-liners}
 
 ### What Worked
+
 {Patterns that led to smooth execution}
 
 ### What Was Inefficient
+
 {Missed opportunities, rework, bottlenecks}
 
 ### Patterns Established
+
 {New conventions discovered during this milestone}
 
 ### Key Lessons
+
 {Specific, actionable takeaways}
 
 ### Cost Observations
-- Model mix: {X}% opus, {Y}% sonnet, {Z}% haiku
+
+- Model mix: {breakdown of model usage}
 - Sessions: {count}
 - Notable: {efficiency observation}
 ```
@@ -493,8 +509,9 @@ ls .planning/RETROSPECTIVE.md 2>/dev/null
 If the "## Cross-Milestone Trends" section exists, update the tables with new data from this milestone.
 
 **Commit:**
+
 ```bash
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs commit "docs: update retrospective for v${VERSION}" --files .planning/RETROSPECTIVE.md
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs commit "docs: update retrospective for v${VERSION}" --files .planning/RETROSPECTIVE.md
 ```
 
 </step>
@@ -515,6 +532,7 @@ See: .planning/PROJECT.md (updated [today])
 ```
 
 **Accumulated Context:**
+
 - Clear decisions summary (full log in PROJECT.md)
 - Clear resolved blockers
 - Keep open blockers for next milestone
@@ -665,6 +683,7 @@ Confirm: "Tagged: v[X.Y]"
 Ask: "Push tag to remote? (y/n)"
 
 If yes:
+
 ```bash
 git push origin v[X.Y]
 ```
@@ -678,6 +697,7 @@ Commit milestone completion.
 ```bash
 node ~/.codex/get-shit-done/bin/gsd-tools.cjs commit "chore: complete v[X.Y] milestone" --files .planning/milestones/v[X.Y]-ROADMAP.md .planning/milestones/v[X.Y]-REQUIREMENTS.md .planning/milestones/v[X.Y]-MILESTONE-AUDIT.md .planning/MILESTONES.md .planning/PROJECT.md .planning/STATE.md
 ```
+
 ```
 
 Confirm: "Committed: chore: complete v[X.Y] milestone"
@@ -687,13 +707,16 @@ Confirm: "Committed: chore: complete v[X.Y] milestone"
 <step name="offer_next">
 
 ```
+
 ✅ Milestone v[X.Y] [Name] complete
 
 Shipped:
+
 - [N] phases ([M] plans, [P] tasks)
 - [One sentence of what shipped]
 
 Archived:
+
 - milestones/v[X.Y]-ROADMAP.md
 - milestones/v[X.Y]-REQUIREMENTS.md
 
@@ -706,11 +729,12 @@ Tag: v[X.Y]
 
 **Start Next Milestone** — questioning → research → requirements → roadmap
 
-`/gsd:new-milestone`
+`$gsd-new-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
+
 ```
 
 </step>
@@ -758,6 +782,7 @@ Milestone completion is successful when:
 - [ ] Known gaps recorded in MILESTONES.md if user proceeded with incomplete requirements
 - [ ] RETROSPECTIVE.md updated with milestone section
 - [ ] Cross-milestone trends updated
-- [ ] User knows next step (/gsd:new-milestone)
+- [ ] User knows next step ($gsd-new-milestone)
 
 </success_criteria>
+```

package/get-shit-done/workflows/diagnose-issues.md

@@ -201,7 +201,7 @@ Agents only diagnose—plan-phase --gaps handles fixes (no fix application).
 
 **Agent times out:**
 - Check DEBUG-{slug}.md for partial progress
-- Can resume with /gsd:debug
+- Can resume with $gsd-debug
 
 **All agents fail:**
 - Something systemic (permissions, git, etc.)

package/get-shit-done/workflows/discovery-phase.md

@@ -4,7 +4,7 @@ Produces DISCOVERY.md (for Level 2-3) that informs PLAN.md creation.
 
 Called from plan-phase.md's mandatory_discovery step with a depth parameter.
 
-NOTE: For comprehensive ecosystem research ("how do experts build this"), use /gsd:research-phase instead, which produces RESEARCH.md.
+NOTE: For comprehensive ecosystem research ("how do experts build this"), use $gsd-research-phase instead, which produces RESEARCH.md.
 </purpose>
 
 <depth_levels>
@@ -252,8 +252,8 @@ Confidence: [level]
 
 What's next?
 
-1. Discuss phase context (/gsd:discuss-phase [current-phase])
-2. Create phase plan (/gsd:plan-phase [current-phase])
+1. Discuss phase context ($gsd-discuss-phase [current-phase])
+2. Create phase plan ($gsd-plan-phase [current-phase])
 3. Refine discovery (dig deeper)
 4. Review discovery
 

package/get-shit-done/workflows/discuss-phase.md

@@ -107,7 +107,7 @@ Phase: "API documentation"
 
 <process>
 
-**Express path available:** If you already have a PRD or acceptance criteria document, use `/gsd:plan-phase {phase} --prd path/to/prd.md` to skip this discussion and go straight to planning.
+**Express path available:** If you already have a PRD or acceptance criteria document, use `$gsd-plan-phase {phase} --prd path/to/prd.md` to skip this discussion and go straight to planning.
 
 <step name="initialize" priority="first">
 Phase number from argument (required).
@@ -122,7 +122,7 @@ Parse JSON for: `commit_docs`, `phase_found`, `phase_dir`, `phase_number`, `phas
 ```
 Phase [X] not found in roadmap.
 
-Use /gsd:progress to see available phases.
+Use $gsd-progress to see available phases.
 ```
 Exit workflow.
 
@@ -157,7 +157,7 @@ Use AskUserQuestion:
 - header: "Plans exist"
 - question: "Phase [X] already has {plan_count} plan(s) created without user context. Your decisions here won't affect existing plans unless you replan."
 - options:
-  - "Continue and replan after" — Capture context, then run /gsd:plan-phase {X} to replan
+  - "Continue and replan after" — Capture context, then run $gsd-plan-phase {X} to replan
   - "View existing plans" — Show plans before deciding
   - "Cancel" — Skip discuss-phase
 
@@ -397,14 +397,14 @@ Created: .planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md
 
 **Phase ${PHASE}: [Name]** — [Goal from ROADMAP.md]
 
-`/gsd:plan-phase ${PHASE}`
+`$gsd-plan-phase ${PHASE}`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/gsd:plan-phase ${PHASE} --skip-research` — plan without research
+- `$gsd-plan-phase ${PHASE} --skip-research` — plan without research
 - Review/edit CONTEXT.md before continuing
 
 ---
@@ -486,7 +486,7 @@ Task(
     2. Follow ALL steps: initialize, validate, load context, research, plan, verify, auto-advance
     3. When spawning agents (gsd-phase-researcher, gsd-planner, gsd-plan-checker), use Task with specified subagent_type and model
     4. For step 14 (auto-advance to execute): spawn execute-phase as a Task with DIRECT file reference — tell it to read execute-phase.md. Include @file refs to execute-phase.md, checkpoints.md, tdd.md, model-profile-resolution.md. Pass --no-transition flag so execute-phase returns results instead of chaining further.
-    5. Do NOT use the Skill tool or /gsd: commands. Read workflow .md files directly.
+    5. Do NOT use the Skill tool or $gsd- commands. Read workflow .md files directly.
     6. Return: PHASE COMPLETE (full pipeline success), PLANNING COMPLETE (planning done but execute failed/skipped), PLANNING INCONCLUSIVE, or GAPS FOUND
     </instructions>
   ",
@@ -504,23 +504,23 @@ Task(
 
   Auto-advance pipeline finished: discuss → plan → execute
 
-  Next: /gsd:discuss-phase ${NEXT_PHASE} --auto
+  Next: $gsd-discuss-phase ${NEXT_PHASE} --auto
   <sub>/clear first → fresh context window</sub>
   ```
 - **PLANNING COMPLETE** → Planning done, execution didn't complete:
   ```
   Auto-advance partial: Planning complete, execution did not finish.
-  Continue: /gsd:execute-phase ${PHASE}
+  Continue: $gsd-execute-phase ${PHASE}
   ```
 - **PLANNING INCONCLUSIVE / CHECKPOINT** → Stop chain:
   ```
   Auto-advance stopped: Planning needs input.
-  Continue: /gsd:plan-phase ${PHASE}
+  Continue: $gsd-plan-phase ${PHASE}
   ```
 - **GAPS FOUND** → Stop chain:
   ```
   Auto-advance stopped: Gaps found during execution.
-  Continue: /gsd:plan-phase ${PHASE} --gaps
+  Continue: $gsd-plan-phase ${PHASE} --gaps
   ```
 
 **If neither `--auto` nor config enabled:**