gsd-opencode 1.4.15 → 1.5.2

package/bin/install.js

@@ -183,7 +183,7 @@ function install(isGlobal) {
   console.log(`  ${green}✓${reset} Installed get-shit-done`);
 
   console.log(`
-  ${green}Done!${reset} Run ${cyan}/gsd:help${reset} to get started.
+  ${green}Done!${reset} Run ${cyan}/gsd-help${reset} to get started.
   `);
 }
 

package/command/gsd/add-phase.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:add-phase
+name: gsd-add-phase
 description: Add phase to end of current milestone in roadmap
 argument-hint: <description>
 allowed-tools:
@@ -19,22 +19,24 @@ Purpose: Add planned work discovered during execution that belongs at the end of
 <execution_context>
 @.planning/ROADMAP.md
 @.planning/STATE.md
+
+Phase description: $ARGUMENTS
 </execution_context>
 
 <process>
 
 <step name="parse_arguments">
 Parse the command arguments:
-- All arguments ($ARGUMENTS) become the phase description
-- Example: `/gsd:add-phase Add authentication` → description = "Add authentication"
-- Example: `/gsd:add-phase Fix critical performance issues` → description = "Fix critical performance issues"
+- All arguments `$ARGUMENTS` become the phase description
+- Example: `/gsd-add-phase Add authentication` → description = "Add authentication"
+- Example: `/gsd-add-phase Fix critical performance issues` → description = "Fix critical performance issues"
 
 If no arguments provided:
 
 ```
 ERROR: Phase description required
-Usage: /gsd:add-phase <description>
-Example: /gsd:add-phase Add authentication system
+Usage: /gsd-add-phase <description>
+Example: /gsd-add-phase Add authentication system
 ```
 
 Exit.
@@ -128,7 +130,7 @@ Add the new phase entry to the roadmap:
    **Plans:** 0 plans
 
    Plans:
-   - [ ] TBD (run /gsd:plan-phase {N} to break down)
+   - [ ] TBD (run /gsd-plan-phase {N} to break down)
 
    **Details:**
    [To be added during planning]
@@ -170,14 +172,14 @@ Project state updated: .planning/STATE.md
 
 **Phase {N}: {description}**
 
-`/gsd:plan-phase {N}`
+`/gsd-plan-phase {N}`
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:add-phase <description>` — add another phase
+- `/gsd-add-phase <description>` — add another phase
 - Review roadmap
 
 ---
@@ -190,8 +192,8 @@ Project state updated: .planning/STATE.md
 
 - Don't modify phases outside current milestone
 - Don't renumber existing phases
-- Don't use decimal numbering (that's /gsd:insert-phase)
-- Don't create plans yet (that's /gsd:plan-phase)
+- Don't use decimal numbering (that's /gsd-insert-phase)
+- Don't create plans yet (that's /gsd-plan-phase)
 - Don't commit changes (user decides when to commit)
   </anti_patterns>
 

package/command/gsd/add-todo.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:add-todo
+name: gsd-add-todo
 description: Capture idea or task as todo from current conversation context
 argument-hint: [optional description]
 allowed-tools:
@@ -17,6 +17,8 @@ Enables "thought → capture → continue" flow without losing context or derail
 
 <context>
 @.planning/STATE.md
+
+Todo title: $ARGUMENTS
 </context>
 
 <process>
@@ -36,8 +38,8 @@ Note existing areas for consistency in infer_area step.
 </step>
 
 <step name="extract_content">
-**With arguments:** Use ($ARGUMENTS) as the title/focus.
-- `/gsd:add-todo Add auth token refresh` → title = "Add auth token refresh"
+**With arguments:** Use `$ARGUMENTS` as the title/focus.
+- `/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
@@ -108,7 +110,7 @@ files:
 
 ## Problem
 
-[problem description - enough context for future Claude to understand weeks later]
+[problem description - enough context for future OpenCode to understand weeks later]
 
 ## Solution
 
@@ -154,7 +156,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>
 
@@ -174,7 +176,7 @@ Would you like to:
 <success_criteria>
 - [ ] Directory structure exists
 - [ ] Todo file created with valid frontmatter
-- [ ] Problem section has enough context for future Claude
+- [ ] Problem section has enough context for future OpenCode
 - [ ] No duplicates (checked and resolved)
 - [ ] Area consistent with existing todos
 - [ ] STATE.md updated if exists

package/command/gsd/check-todos.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:check-todos
+name: gsd-check-todos
 description: List pending todos and select one to work on
 argument-hint: [area filter]
 allowed-tools:
@@ -19,6 +19,8 @@ Enables reviewing captured ideas and deciding what to work on next.
 <context>
 @.planning/STATE.md
 @.planning/ROADMAP.md
+
+Area filter: $ARGUMENTS
 </context>
 
 <process>
@@ -33,14 +35,14 @@ If 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.
@@ -48,8 +50,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">
@@ -74,7 +76,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
 ```
 
@@ -138,7 +140,7 @@ Use question:
 - 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>
@@ -154,7 +156,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:**
@@ -202,7 +204,7 @@ Confirm: "Committed: docs: start work on todo - [title]"
 <anti_patterns>
 - Don't delete todos — move to done/ when work begins
 - Don't start work without moving to done/ first
-- Don't create plans from this command — route to /gsd:plan-phase or /gsd:add-phase
+- Don't create plans from this command — route to /gsd-plan-phase or /gsd-add-phase
 </anti_patterns>
 
 <success_criteria>

package/command/gsd/complete-milestone.md

@@ -1,6 +1,6 @@
 ---
 type: prompt
-name: gsd:complete-milestone
+name: gsd-complete-milestone
 description: Archive completed milestone and prepare for next version
 argument-hint: <version>
 allowed-tools:
@@ -10,7 +10,7 @@ allowed-tools:
 ---
 
 <objective>
-Mark milestone {{version}} complete, archive to milestones/, and update ROADMAP.md.
+Mark milestone $ARGUMENTS complete, archive to milestones/, and update ROADMAP.md.
 
 Purpose: Create historical record of shipped version, collapse completed work in roadmap, and prepare for next milestone.
 Output: Milestone archived, roadmap reorganized, git tagged.
@@ -31,7 +31,7 @@ Output: Milestone archived, roadmap reorganized, git tagged.
 
 **User input:**
 
-- Version: {{version}} (e.g., "1.0", "1.1", "2.0")
+- Version: $ARGUMENTS (e.g., "1.0", "1.1", "2.0")
   </context>
 
 <process>
@@ -59,7 +59,7 @@ Output: Milestone archived, roadmap reorganized, git tagged.
 
 4. **Archive milestone:**
 
-   - Create `.planning/milestones/v{{version}}-ROADMAP.md`
+   - Create `.planning/milestones/v$ARGUMENTS-ROADMAP.md`
    - Extract full phase details from ROADMAP.md
    - Fill milestone-archive.md template
    - Update ROADMAP.md to one-line summary with link
@@ -74,8 +74,8 @@ Output: Milestone archived, roadmap reorganized, git tagged.
 6. **Commit and tag:**
 
    - Stage: MILESTONES.md, PROJECT.md, ROADMAP.md, STATE.md, archive file
-   - Commit: `chore: archive v{{version}} milestone`
-   - Tag: `git tag -a v{{version}} -m "[milestone summary]"`
+   - Commit: `chore: archive v$ARGUMENTS milestone`
+   - Tag: `git tag -a v$ARGUMENTS -m "[milestone summary]"`
    - Ask about pushing tag
 
 7. **Offer next steps:**
@@ -87,10 +87,10 @@ Output: Milestone archived, roadmap reorganized, git tagged.
 
 <success_criteria>
 
-- Milestone archived to `.planning/milestones/v{{version}}-ROADMAP.md`
+- Milestone archived to `.planning/milestones/v$ARGUMENTS-ROADMAP.md`
 - ROADMAP.md collapsed to one-line entry
 - PROJECT.md updated with current state
-- Git tag v{{version}} created
+- Git tag v$ARGUMENTS created
 - Commit successful
 - User knows next steps
   </success_criteria>

package/command/gsd/consider-issues.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:consider-issues
+name: gsd-consider-issues
 description: Review deferred issues with codebase context, close resolved ones, identify urgent ones
 allowed-tools:
   - read
@@ -154,12 +154,12 @@ Use question with appropriate options based on findings:
 - "Review each first" - Show details before closing
 
 **If urgent issues exist:**
-- "Insert urgent phase" - Create phase to address urgent issues (/gsd:insert-phase)
+- "Insert urgent phase" - Create phase to address urgent issues (/gsd-insert-phase)
 - "Add to current plan" - Include in next plan being created
 - "Defer anyway" - Keep as-is despite urgency
 
 **If natural fits exist:**
-- "Note for phase planning" - Will be picked up during /gsd:plan-phase
+- "Note for phase planning" - Will be picked up during /gsd-plan-phase
 - "Add explicit reminder" - Update issue with "Include in Phase X"
 
 **Always include:**
@@ -182,11 +182,11 @@ Use question with appropriate options based on findings:
 4. Update STATE.md deferred issues count
 
 **If inserting urgent phase:**
-- Display the command for user to run after clearing: `/gsd:insert-phase [after-phase] Address urgent issues ISS-XXX, ISS-YYY`
+- Display the command for user to run after clearing: `/gsd-insert-phase [after-phase] Address urgent issues ISS-XXX, ISS-YYY`
 
 **If noting for phase planning:**
 - Update issue's "Suggested phase" field with specific phase number
-- These will be picked up by /gsd:plan-phase workflow
+- These will be picked up by /gsd-plan-phase workflow
 </step>
 
 </process>

package/command/gsd/create-roadmap.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:create-roadmap
+name: gsd-create-roadmap
 description: Create roadmap with phases for the project
 allowed-tools:
   - read
@@ -12,7 +12,7 @@ allowed-tools:
 <objective>
 Create project roadmap with phase breakdown.
 
-Roadmaps define what work happens in what order. Run after /gsd:new-project.
+Roadmaps define what work happens in what order. Run after /gsd-new-project.
 </objective>
 
 <execution_context>
@@ -31,7 +31,7 @@ Roadmaps define what work happens in what order. Run after /gsd:new-project.
 <step name="validate">
 ```bash
 # Verify project exists
-[ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md found. Run /gsd:new-project first."; exit 1; }
+[ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md found. Run /gsd-new-project first."; exit 1; }
 ```
 </step>
 
@@ -83,15 +83,15 @@ Roadmap created:
 
 **Phase 1: [Name]** — [Goal from ROADMAP.md]
 
-`/gsd:plan-phase 1`
+`/gsd-plan-phase 1`
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:discuss-phase 1` — gather context first
-- `/gsd:research-phase 1` — investigate unknowns
+- `/gsd-discuss-phase 1` — gather context first
+- `/gsd-research-phase 1` — investigate unknowns
 - Review roadmap
 
 ---

package/command/gsd/debug.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:debug
+name: gsd-debug
 description: Systematic debugging with persistent state across context resets
 argument-hint: [issue description]
 allowed-tools:
@@ -13,7 +13,7 @@ allowed-tools:
 ---
 
 <objective>
-Debug issues using scientific method with a persistent debug document that survives `/clear`.
+Debug issues using scientific method with a persistent debug document that survives `/new`.
 
 If resuming (no arguments and active session exists): pick up where you left off.
 If starting new: gather symptoms, then investigate autonomously.
@@ -25,7 +25,7 @@ If starting new: gather symptoms, then investigate autonomously.
 </execution_context>
 
 <context>
-User's issue: ($ARGUMENTS)
+User's issue: $ARGUMENTS
 
 Check for active debug sessions:
 ```bash
@@ -45,7 +45,7 @@ Follow the workflow in @~/.config/opencode/get-shit-done/workflows/debug.md
 5. **Fix and verify** - Minimal fix, verify against original symptoms
 6. **Archive** - Move to `.planning/debug/resolved/`
 
-**Key principle:** The DEBUG.md is your memory. Update it constantly. It survives `/clear`.
+**Key principle:** The DEBUG.md is your memory. Update it constantly. It survives `/new`.
 </process>
 
 <success_criteria>

package/command/gsd/discuss-milestone.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:discuss-milestone
+name: gsd-discuss-milestone
 description: Gather context for next milestone through adaptive questioning
 ---
 
@@ -7,7 +7,7 @@ description: Gather context for next milestone through adaptive questioning
 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
+Output: Context gathered, then routes to /gsd-new-milestone
 </objective>
 
 <execution_context>
@@ -33,7 +33,7 @@ Output: Context gathered, then routes to /gsd:new-milestone
    - Use question to dig into features they mention
    - Use question to help them articulate what matters most
    - Use question for decision gate (ready / ask more / let me add context)
-4. Hand off to /gsd:new-milestone with gathered context
+4. Hand off to /gsd-new-milestone with gathered context
 
 **CRITICAL: ALL questions use question. Never ask inline text questions.**
 </process>
@@ -43,5 +43,5 @@ Output: Context gathered, then routes to /gsd:new-milestone
 - Project state loaded and presented
 - Previous milestone context summarized
 - Milestone scope gathered through adaptive questioning
-- Context handed off to /gsd:new-milestone
+- Context handed off to /gsd-new-milestone
   </success_criteria>

package/command/gsd/discuss-phase.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:discuss-phase
+name: gsd-discuss-phase
 description: Gather phase context through adaptive questioning before planning
 argument-hint: "[phase]"
 ---
@@ -18,7 +18,7 @@ Output: {phase}-CONTEXT.md capturing the user's vision for the phase
 </execution_context>
 
 <context>
-Phase number: ($ARGUMENTS) (required)
+Phase number: $ARGUMENTS (required)
 
 **Load project state first:**
 @.planning/STATE.md

package/command/gsd/execute-phase.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:execute-phase
+name: gsd-execute-phase
 description: Execute all plans in a phase with wave-based parallelization
 argument-hint: "<phase-number>"
 allowed-tools:
@@ -28,7 +28,7 @@ Context budget: ~15% orchestrator, 100% fresh per subagent.
 </execution_context>
 
 <context>
-Phase: ($ARGUMENTS)
+Phase: $ARGUMENTS
 
 @.planning/ROADMAP.md
 @.planning/STATE.md
@@ -64,8 +64,8 @@ Phase: ($ARGUMENTS)
    - Update ROADMAP.md
 
 6. **Offer next steps**
-   - More phases → `/gsd:plan-phase {next}`
-   - Milestone complete → `/gsd:complete-milestone`
+   - More phases → `/gsd-plan-phase {next}`
+   - Milestone complete → `/gsd-complete-milestone`
 </process>
 
 <wave_execution>

package/command/gsd/execute-plan.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:execute-plan
+name: gsd-execute-plan
 description: Execute a PLAN.md file
 argument-hint: "[path-to-PLAN.md]"
 allowed-tools:
@@ -25,7 +25,7 @@ Context budget: ~15% orchestrator, 100% fresh for subagent.
 </execution_context>
 
 <context>
-Plan path: ($ARGUMENTS)
+Plan path: $ARGUMENTS
 
 @.planning/STATE.md
 @.planning/config.json (if exists)
@@ -33,7 +33,7 @@ Plan path: ($ARGUMENTS)
 
 <process>
 1. **Validate plan exists**
-   - Confirm file at ($ARGUMENTS) exists
+   - Confirm file at $ARGUMENTS exists
    - Error if not found: "Plan not found: {path}"
 
 2. **Check if already executed**