gsd-opencode 1.4.15 → 1.5.2

package/get-shit-done/workflows/map-codebase.md

@@ -15,7 +15,7 @@ Each agent has fresh context and focuses on specific aspects. Output is concise
 Include enough detail to be useful as reference. Prioritize practical examples (especially code patterns) over arbitrary brevity. A 200-line TESTING.md with real patterns is more valuable than a 74-line summary.
 
 **Always include file paths:**
-Documents are reference material for Claude when planning/executing. Vague descriptions like "UserService handles users" are not actionable. Always include actual file paths formatted with backticks: `src/services/user.ts`. This allows Claude to navigate directly to relevant code without re-searching. Do NOT include line numbers (they go stale), just file paths.
+Documents are reference material for OpenCode when planning/executing. Vague descriptions like "UserService handles users" are not actionable. Always include actual file paths formatted with backticks: `src/services/user.ts`. This allows OpenCode to navigate directly to relevant code without re-searching. Do NOT include line numbers (they go stale), just file paths.
 </philosophy>
 
 <process>
@@ -403,14 +403,14 @@ Created .planning/codebase/:
 
 **Initialize project** — use codebase context for planning
 
-`/gsd:new-project`
+`/gsd-new-project`
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 
 **Also available:**
-- Re-run mapping: `/gsd:map-codebase`
+- Re-run mapping: `/gsd-map-codebase`
 - Review specific file: `cat .planning/codebase/STACK.md`
 - Edit any document before proceeding
 

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

@@ -32,7 +32,7 @@ Decimal phases enable urgent work insertion without renumbering:
 <purpose>
 Create executable phase prompts (PLAN.md files) optimized for parallel execution.
 
-PLAN.md IS the prompt that Claude executes. Plans are grouped into execution waves based on dependencies - independent plans run in parallel, dependent plans wait for predecessors.
+PLAN.md IS the prompt that OpenCode executes. Plans are grouped into execution waves based on dependencies - independent plans run in parallel, dependent plans wait for predecessors.
 </purpose>
 
 <planning_principles>
@@ -136,7 +136,7 @@ Read any existing PLAN.md or DISCOVERY.md in the phase directory.
 
 If roadmap flagged `Research: Likely`, Level 0 (skip) is not available.
 
-For niche domains (3D, games, audio, shaders, ML), suggest `/gsd:research-phase` before plan-phase.
+For niche domains (3D, games, audio, shaders, ML), suggest `/gsd-research-phase` before plan-phase.
 </step>
 
 <step name="read_project_history">
@@ -217,19 +217,19 @@ Understand:
 - Phase goal (from roadmap)
 - What exists already (scan codebase if mid-project)
 - Dependencies met (previous phases complete?)
-- Any {phase}-RESEARCH.md (from /gsd:research-phase)
+- Any {phase}-RESEARCH.md (from /gsd-research-phase)
 - Any DISCOVERY.md (from mandatory discovery)
-- Any {phase}-CONTEXT.md (from /gsd:discuss-phase)
+- Any {phase}-CONTEXT.md (from /gsd-discuss-phase)
 
 ```bash
 # If mid-project, understand current state
 ls -la src/ 2>/dev/null
 cat package.json 2>/dev/null | head -20
 
-# Check for ecosystem research (from /gsd:research-phase)
+# Check for ecosystem research (from /gsd-research-phase)
 cat .planning/phases/XX-name/${PHASE}-RESEARCH.md 2>/dev/null
 
-# Check for phase context (from /gsd:discuss-phase)
+# Check for phase context (from /gsd-discuss-phase)
 cat .planning/phases/XX-name/${PHASE}-CONTEXT.md 2>/dev/null
 ```
 
@@ -237,7 +237,7 @@ cat .planning/phases/XX-name/${PHASE}-CONTEXT.md 2>/dev/null
 
 **If CONTEXT.md exists:** Honor vision, prioritize essential, respect boundaries, incorporate specifics.
 
-**If neither exist:** Suggest /gsd:research-phase for niche domains, /gsd:discuss-phase for simpler domains, or proceed with roadmap only.
+**If neither exist:** Suggest /gsd-research-phase for niche domains, /gsd-discuss-phase for simpler domains, or proceed with roadmap only.
 </step>
 
 <step name="break_into_tasks">
@@ -560,7 +560,7 @@ domain: [optional]
 ---
 ```
 
-**Wave is pre-computed:** Wave numbers are assigned during planning (see `assign_waves` step). `/gsd:execute-phase` reads `wave` directly from frontmatter and groups plans by wave number. No runtime dependency analysis needed.
+**Wave is pre-computed:** Wave numbers are assigned during planning (see `assign_waves` step). `/gsd-execute-phase` reads `wave` directly from frontmatter and groups plans by wave number. No runtime dependency analysis needed.
 
 **Context section - parallel-aware:**
 
@@ -638,20 +638,20 @@ Wave 2: {plan-03}
 [If 1 plan created:]
 **{phase}-01: [Plan Name]** - [objective summary]
 
-`/gsd:execute-plan .planning/phases/XX-name/{phase}-01-PLAN.md`
+`/gsd-execute-plan .planning/phases/XX-name/{phase}-01-PLAN.md`
 
 [If 2+ plans created:]
 **Phase {X}: [Phase Name]** - {N} plans in {M} waves
 
-`/gsd:execute-phase {X}`
+`/gsd-execute-phase {X}`
 
-*`/clear` first - fresh context window*
+*`/new` first - fresh context window*
 
 ---
 
 **Also available:**
 - Review/adjust plans before executing
-[If 2+ plans: - `/gsd:execute-plan {phase}-01-PLAN.md` - run plans one at a time]
+[If 2+ plans: - `/gsd-execute-plan {phase}-01-PLAN.md` - run plans one at a time]
 [If 2+ plans: - View all plans: `ls .planning/phases/XX-name/*-PLAN.md`]
 
 ---
@@ -679,7 +679,7 @@ If you can't specify Files + Action + Verify + Done, the task is too vague.
 - No acceptance criteria committees
 - No sub-sub-sub tasks
 - **No reflexive sequential chaining** (Plan 02 depends on 01 "just because")
-Tasks are instructions for Claude, not Jira tickets.
+Tasks are instructions for OpenCode, not Jira tickets.
 </anti_patterns>
 
 <success_criteria>

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

@@ -1,20 +1,20 @@
 <purpose>
 Comprehensive research on HOW to implement a phase before planning.
 
-Triggered by /gsd:research-phase command when the domain is niche, complex, or Claude's training is likely stale.
+Triggered by /gsd-research-phase command when the domain is niche, complex, or OpenCode's training is likely stale.
 
 Produces RESEARCH.md with ecosystem knowledge that informs quality planning - not just "which library" but "how do experts build this."
 </purpose>
 
 <when_to_use>
-**This workflow is for domains where Claude fails without research:**
+**This workflow is for domains where OpenCode fails without research:**
 - 3D graphics (Three.js, Babylon.js, procedural generation, level design)
 - Game development (physics engines, collision, AI, ECS patterns)
 - Audio/music (Web Audio, DSP, synthesis, MIDI)
 - Shaders (GLSL, Metal, ISF, compute shaders)
 - ML/AI integration (model serving, inference, vector DBs)
 - Real-time systems (WebSockets, WebRTC, CRDT sync)
-- Specialized frameworks with active ecosystems Claude may not know
+- Specialized frameworks with active ecosystems OpenCode may not know
 
 **Skip this for commodity domains:**
 - Standard auth (JWT, OAuth)
@@ -32,7 +32,7 @@ For niche domains, the question isn't library selection - it's:
 - What's the established architecture pattern?
 - What libraries form the standard stack?
 - What problems do people commonly hit?
-- What's SOTA vs what Claude thinks is SOTA?
+- What's SOTA vs what OpenCode thinks is SOTA?
 - What should NOT be hand-rolled?
 </key_insight>
 
@@ -53,7 +53,7 @@ fi
 ```
 Error: Phase ${PHASE} not found in roadmap.
 
-Use /gsd:progress to see available phases.
+Use /gsd-progress to see available phases.
 ```
 Exit workflow.
 
@@ -103,7 +103,7 @@ Load available context to inform research direction:
 cat .planning/PROJECT.md 2>/dev/null | head -50
 ```
 
-**2. Phase context (if exists from /gsd:discuss-phase):**
+**2. Phase context (if exists from /gsd-discuss-phase):**
 ```bash
 cat .planning/phases/${PHASE}-*/${PHASE}-CONTEXT.md 2>/dev/null
 ```
@@ -145,7 +145,7 @@ Categories to consider:
 
 **1. Core Technology:**
 - What's the primary technology/framework?
-- What version is current? (Claude's training may be stale)
+- What version is current? (OpenCode's training may be stale)
 - What's the standard setup/toolchain?
 
 **2. Ecosystem/Stack:**
@@ -193,7 +193,7 @@ Execute research systematically for each domain identified.
 
 **CRITICAL: Source hierarchy - Context7 BEFORE WebSearch**
 
-Claude's training data is 6-18 months stale. Treat pre-existing knowledge as hypothesis, not fact.
+OpenCode's training data is 6-18 months stale. Treat pre-existing knowledge as hypothesis, not fact.
 
 <research_protocol>
 
@@ -247,7 +247,7 @@ Execute research queries and document findings as you go:
 
 **Core Technology Findings:**
 - Current version: [from Context7]
-- Key changes since [Claude's training]: [from docs/WebSearch]
+- Key changes since [OpenCode's training]: [from docs/WebSearch]
 - Setup approach: [verified pattern]
 
 **Ecosystem Stack:**
@@ -292,7 +292,7 @@ Before creating RESEARCH.md, run through research-pitfalls.md checklist:
 - [ ] "What might I have missed?" review completed
 
 **Additional checks for ecosystem research:**
-- [ ] Checked for libraries Claude might not know about
+- [ ] Checked for libraries OpenCode might not know about
 - [ ] Verified version numbers are current
 - [ ] Confirmed patterns still recommended (not deprecated)
 - [ ] Looked for "don't do this" warnings in docs
@@ -371,7 +371,7 @@ Created: .planning/phases/${PHASE}-${SLUG}/${PHASE}-RESEARCH.md
 **Confidence:** [HIGH/MEDIUM/LOW] - [brief reason]
 
 What's next?
-1. Plan this phase (/gsd:plan-phase ${PHASE}) - RESEARCH.md will be loaded automatically
+1. Plan this phase (/gsd-plan-phase ${PHASE}) - RESEARCH.md will be loaded automatically
 2. Dig deeper - Research specific areas more thoroughly
 3. Review full RESEARCH.md
 4. Done for now
@@ -418,7 +418,7 @@ Confirm: "Committed: docs(${PHASE}): complete phase research"
 </success_criteria>
 
 <integration_with_planning>
-When /gsd:plan-phase runs after research:
+When /gsd-plan-phase runs after research:
 
 1. plan-phase detects RESEARCH.md exists in phase directory
 2. RESEARCH.md loaded as @context reference
@@ -428,7 +428,7 @@ When /gsd:plan-phase runs after research:
 6. "Architecture patterns" inform task structure
 7. "Code examples" can be referenced in task actions
 
-This produces higher quality plans because Claude knows:
+This produces higher quality plans because OpenCode knows:
 - What tools experts use
 - What patterns to follow
 - What mistakes to avoid

package/get-shit-done/workflows/resume-project.md

@@ -26,7 +26,7 @@ ls .planning/PROJECT.md 2>/dev/null && echo "Project file exists"
 
 **If STATE.md exists:** Proceed to load_state
 **If only ROADMAP.md/PROJECT.md exist:** Offer to reconstruct STATE.md
-**If .planning/ doesn't exist:** This is a new project - route to /gsd:new-project
+**If .planning/ doesn't exist:** This is a new project - route to /gsd-new-project
 </step>
 
 <step name="load_state">
@@ -121,7 +121,7 @@ Present complete project status to user:
     Task: [task description from agent-history.json]
     Interrupted: [timestamp]
 
-    Resume with: /gsd:resume-task
+    Resume with: /gsd-resume-task
 
 [If deferred issues exist:]
 📋 [N] deferred issues awaiting attention
@@ -141,7 +141,7 @@ Present complete project status to user:
 Based on project state, determine the most logical next action:
 
 **If interrupted agent exists:**
-→ Primary: Resume interrupted agent (/gsd:resume-task)
+→ Primary: Resume interrupted agent (/gsd-resume-task)
 → Option: Start fresh (abandon agent work)
 
 **If .continue-here file exists:**
@@ -178,15 +178,15 @@ Present contextual options based on project state:
 What would you like to do?
 
 [Primary action based on state - e.g.:]
-1. Resume interrupted agent (/gsd:resume-task) [if interrupted agent found]
+1. Resume interrupted agent (/gsd-resume-task) [if interrupted agent found]
    OR
-1. Resume from checkpoint (/gsd:execute-plan .planning/phases/XX-name/.continue-here-02-01.md)
+1. Resume from checkpoint (/gsd-execute-plan .planning/phases/XX-name/.continue-here-02-01.md)
    OR
-1. Execute next plan (/gsd:execute-plan .planning/phases/XX-name/02-02-PLAN.md)
+1. Execute next plan (/gsd-execute-plan .planning/phases/XX-name/02-02-PLAN.md)
    OR
-1. Discuss Phase 3 context (/gsd:discuss-phase 3) [if CONTEXT.md missing]
+1. Discuss Phase 3 context (/gsd-discuss-phase 3) [if CONTEXT.md missing]
    OR
-1. Plan Phase 3 (/gsd:plan-phase 3) [if CONTEXT.md exists or discuss option declined]
+1. Plan Phase 3 (/gsd-plan-phase 3) [if CONTEXT.md exists or discuss option declined]
 
 [Secondary options:]
 2. Review current phase status
@@ -217,9 +217,9 @@ Based on user selection, route to appropriate workflow:
 
   **{phase}-{plan}: [Plan Name]** — [objective from PLAN.md]
 
-  `/gsd:execute-plan [path]`
+  `/gsd-execute-plan [path]`
 
-  *`/clear` first → fresh context window*
+  *`/new` first → fresh context window*
 
   ---
   ```
@@ -231,15 +231,15 @@ Based on user selection, route to appropriate workflow:
 
   **Phase [N]: [Name]** — [Goal from ROADMAP.md]
 
-  `/gsd:plan-phase [phase-number]`
+  `/gsd-plan-phase [phase-number]`
 
-  *`/clear` first → fresh context window*
+  *`/new` first → fresh context window*
 
   ---
 
   **Also available:**
-  - `/gsd:discuss-phase [N]` — gather context first
-  - `/gsd:research-phase [N]` — investigate unknowns
+  - `/gsd-discuss-phase [N]` — gather context first
+  - `/gsd-research-phase [N]` — investigate unknowns
 
   ---
   ```

package/get-shit-done/workflows/transition.md

@@ -449,7 +449,7 @@ Next: Phase [X+1] — [Name]
 ⚡ Auto-continuing: Plan Phase [X+1] in detail
 ```
 
-Exit skill and invoke [removed - use /command syntax]("/gsd:plan-phase [X+1]")
+Exit skill and invoke [removed - use /command syntax]("/gsd-plan-phase [X+1]")
 
 </if>
 
@@ -464,15 +464,15 @@ Exit skill and invoke [removed - use /command syntax]("/gsd:plan-phase [X+1]")
 
 **Phase [X+1]: [Name]** — [Goal from ROADMAP.md]
 
-`/gsd:plan-phase [X+1]`
+`/gsd-plan-phase [X+1]`
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:discuss-phase [X+1]` — gather context first
-- `/gsd:research-phase [X+1]` — investigate unknowns
+- `/gsd-discuss-phase [X+1]` — gather context first
+- `/gsd-research-phase [X+1]` — investigate unknowns
 - Review roadmap
 
 ---
@@ -494,7 +494,7 @@ Phase {X} marked complete.
 ⚡ Auto-continuing: Complete milestone and archive
 ```
 
-Exit skill and invoke [removed - use /command syntax]("/gsd:complete-milestone {version}")
+Exit skill and invoke [removed - use /command syntax]("/gsd-complete-milestone {version}")
 
 </if>
 
@@ -511,9 +511,9 @@ Exit skill and invoke [removed - use /command syntax]("/gsd:complete-milestone {
 
 **Complete Milestone {version}** — archive and prepare for next
 
-`/gsd:complete-milestone {version}`
+`/gsd-complete-milestone {version}`
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 

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

@@ -1,7 +1,7 @@
 <purpose>
 Guide manual user acceptance testing of recently built features. Extract deliverables from SUMMARY.md, generate test checklist, guide user through each test, log issues to phase-scoped file.
 
-The USER performs all testing — Claude generates the checklist, guides the process, and captures issues.
+The USER performs all testing — OpenCode generates the checklist, guides the process, and captures issues.
 </purpose>
 
 <process>
@@ -137,7 +137,7 @@ If any issues found:
 **Actual:** [What actually happened]
 ```
 
-**Note:** Issues go to phase-scoped file, NOT global `.planning/ISSUES.md`. This keeps UAT findings tied to the specific work being tested and enables `/gsd:plan-fix` to address them.
+**Note:** Issues go to phase-scoped file, NOT global `.planning/ISSUES.md`. This keeps UAT findings tied to the specific work being tested and enables `/gsd-plan-fix` to address them.
 </step>
 
 <step name="summarize">
@@ -165,7 +165,7 @@ If any issues found:
 ## Next Steps
 [Based on verdict:]
 - If clean: Suggest proceeding to next phase
-- If issues: Suggest /gsd:plan-fix to address
+- If issues: Suggest /gsd-plan-fix to address
 ```
 </step>
 
@@ -183,7 +183,7 @@ If all passed:
 - "Done" — Finish testing session
 
 If issues found:
-- "Plan fixes" — Create plan to address issues (/gsd:plan-fix)
+- "Plan fixes" — Create plan to address issues (/gsd-plan-fix)
 - "Log and continue" — Issues logged, proceed anyway
 - "Review issues" — Look at logged issues in detail
 - "Done" — Finish testing session

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gsd-opencode",
-  "version": "1.4.15",
+  "version": "1.5.2",
   "description": "A meta-prompting, context engineering and spec-driven development system for OpenCode by TÂCHES.",
   "keywords": [
     "opencode",