gsd-opencode 1.4.2 → 1.5.0

package/get-shit-done/workflows/_archive/execute-phase.md

@@ -6,12 +6,12 @@ Analyzes plan dependencies to identify independent plans that can run in paralle
 </purpose>
 
 <when_to_use>
-Use /gsd:execute-phase when:
+Use /gsd-execute-phase when:
 - Phase has multiple unexecuted plans (2+)
 - Want "walk away, come back to completed work" execution
 - Plans have clear dependency boundaries
 
-Use /gsd:execute-plan when:
+Use /gsd-execute-plan when:
 - Executing a single specific plan
 - Want sequential, interactive execution
 - Need checkpoint interactions
@@ -54,8 +54,8 @@ Options:
 
 **1. Parse phase argument:**
 ```bash
-# From command argument: /gsd:execute-phase 10
-# Or: /gsd:execute-phase .planning/phases/10-parallel-execution/
+# From command argument: /gsd-execute-phase 10
+# Or: /gsd-execute-phase .planning/phases/10-parallel-execution/
 PHASE_ARG="$1"
 ```
 
@@ -98,7 +98,7 @@ echo "Unexecuted: ${#UNEXECUTED[@]} plans"
 | Condition | Action |
 |-----------|--------|
 | 0 unexecuted plans | "All plans complete. Nothing to execute." |
-| 1 unexecuted plan | "Single plan - use /gsd:execute-plan instead" |
+| 1 unexecuted plan | "Single plan - use /gsd-execute-plan instead" |
 | 2+ unexecuted plans | Proceed to dependency analysis |
 
 </step>
@@ -363,7 +363,7 @@ cat .planning/config.json 2>/dev/null
 
 **If parallelization.enabled is false:**
 - Fall back to sequential execution
-- Use /gsd:execute-plan for each plan in order
+- Use /gsd-execute-plan for each plan in order
 
 **Checkpoint handling modes:**
 - `foreground`: Plans with checkpoints run in foreground (not parallel)
@@ -781,7 +781,7 @@ Since agents commit independently, git will catch conflicts at commit time if th
 The dependency analysis step should prevent this, but if an agent fails to commit due to conflict:
 - That agent's status will be "failed"
 - Other agents continue normally
-- User can resolve and retry the failed plan with /gsd:execute-plan
+- User can resolve and retry the failed plan with /gsd-execute-plan
 </step>
 
 <step name="create_phase_summary">
@@ -842,15 +842,15 @@ All {N} plans finished via parallel execution.
 
 **Phase {X+1}: {Next Phase Name}** — {Goal from ROADMAP.md}
 
-`/gsd:plan-phase {X+1}`
+`/gsd-plan-phase {X+1}`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:verify-work {X}` — manual acceptance testing
-- `/gsd:discuss-phase {X+1}` — gather context first
+- `/gsd-verify-work {X}` — manual acceptance testing
+- `/gsd-discuss-phase {X+1}` — gather context first
 ```
 
 **If milestone complete:**
@@ -859,7 +859,7 @@ All {N} plans finished via parallel execution.
 
 All {N} phases finished.
 
-`/gsd:complete-milestone`
+`/gsd-complete-milestone`
 ```
 </step>
 
@@ -869,7 +869,7 @@ All {N} phases finished.
 
 **Agent failure during parallel execution:**
 - Log failure but continue with other agents
-- Failed plans can be retried individually with /gsd:execute-plan
+- Failed plans can be retried individually with /gsd-execute-plan
 - Do not automatically retry (may cause cascade failures)
 
 **Merge conflict detected:**
@@ -877,7 +877,7 @@ All {N} phases finished.
 - Present conflicting files to user
 - Options:
   1. Manual resolution
-  2. Re-run sequential with /gsd:execute-plan
+  2. Re-run sequential with /gsd-execute-plan
 
 **Max concurrent limit reached:**
 - Queue excess plans

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

@@ -573,14 +573,14 @@ Tag: v[X.Y]
 
 **Plan Next Milestone** — define v[X.Y+1] features and scope
 
-`/gsd:discuss-milestone`
+`/gsd-discuss-milestone`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:new-milestone` — create directly if scope is clear
+- `/gsd-new-milestone` — create directly if scope is clear
 
 ---
 ```

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

@@ -35,7 +35,7 @@ Extract:
 **Check for milestone context from discuss-milestone:**
 
 If `.planning/MILESTONE-CONTEXT.md` exists:
-- This contains context from `/gsd:discuss-milestone`
+- This contains context from `/gsd-discuss-milestone`
 - Extract: features, suggested name, phase mapping, constraints
 - Use this to pre-populate milestone details (skip prompting for info already gathered)
 
@@ -47,7 +47,7 @@ If `.planning/MILESTONE-CONTEXT.md` exists:
   </step>
 
 <step name="get_milestone_info">
-**If MILESTONE-CONTEXT.md exists (from /gsd:discuss-milestone):**
+**If MILESTONE-CONTEXT.md exists (from /gsd-discuss-milestone):**
 Use the features, scope, and constraints from the context file.
 Use the suggested milestone name from `<scope>` section.
 Use the phase mapping from `<phase_mapping>` section.
@@ -208,7 +208,7 @@ Write new milestone details to `.planning/ROADMAP.md`.
 
 **File to update:** `.planning/ROADMAP.md`
 
-The main ROADMAP.md file holds full phase details for the active milestone. Archive files in `milestones/` are created only when a milestone ships (via `/gsd:complete-milestone`).
+The main ROADMAP.md file holds full phase details for the active milestone. Archive files in `milestones/` are created only when a milestone ships (via `/gsd-complete-milestone`).
 
 **Process:**
 
@@ -241,7 +241,7 @@ Write complete phase sections for all phases in this milestone. Each phase gets
 **Plans**: TBD
 
 Plans:
-- [ ] [N]-01: TBD (run /gsd:plan-phase [N] to break down)
+- [ ] [N]-01: TBD (run /gsd-plan-phase [N] to break down)
 
 #### Phase [N+1]: [Name]
 
@@ -349,7 +349,7 @@ Delete the temporary milestone context file if it exists:
 rm -f .planning/MILESTONE-CONTEXT.md
 ```
 
-This file was a handoff artifact from `/gsd:discuss-milestone`. Now that the milestone is created, the context is persisted in ROADMAP.md and the temporary file is no longer needed.
+This file was a handoff artifact from `/gsd-discuss-milestone`. Now that the milestone is created, the context is persisted in ROADMAP.md and the temporary file is no longer needed.
 </step>
 
 <step name="offer_next">
@@ -366,15 +366,15 @@ Milestone v[X.Y] [Name] created:
 
 **Phase [N]: [Name]** — [Goal from ROADMAP.md]
 
-`/gsd:plan-phase [N]`
+`/gsd-plan-phase [N]`
 
 *`/clear` 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
 - Review roadmap
 
 ---

package/get-shit-done/workflows/create-roadmap.md

@@ -293,7 +293,7 @@ mkdir -p .planning/phases
 Use template from `~/.config/opencode/get-shit-done/templates/roadmap.md`.
 
 Initial roadmaps use integer phases (1, 2, 3...).
-Decimal phases added later via /gsd:insert-phase command (if it exists).
+Decimal phases added later via /gsd-insert-phase command (if it exists).
 
 Write to `.planning/ROADMAP.md` with:
 
@@ -386,7 +386,7 @@ Resume file: None
 **Key points:**
 
 - Project Reference points to PROJECT.md for full context
-- Claude reads PROJECT.md directly for requirements, constraints, decisions
+- Opencode agent reads PROJECT.md directly for requirements, constraints, decisions
 - This file will be read first in every future operation
 - This file will be updated after every execution
 
@@ -430,15 +430,15 @@ Project initialized:
 
 **Phase 1: [Name]** — [Goal from ROADMAP.md]
 
-`/gsd:plan-phase 1`
+`/gsd-plan-phase 1`
 
 *`/clear` 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/get-shit-done/workflows/debug.md

@@ -5,7 +5,7 @@ You are the debugger. The user knows what's wrong (behavior), not why (root caus
 </purpose>
 
 <philosophy>
-**User = reporter. Claude = investigator.**
+**User = reporter. Opencode agent = investigator.**
 
 The user knows:
 - What they expected to happen
@@ -281,7 +281,7 @@ If ELIMINATED:
 
 After significant investigation (5+ evidence entries), check if context is heavy.
 If so, ensure Current Focus is fully updated and suggest:
-"Context filling up. Safe to /clear - run /gsd:debug to resume."
+"Context filling up. Safe to /clear - run /gsd-debug to resume."
 </step>
 
 <step name="resume_from_file">
@@ -391,7 +391,7 @@ Use question:
 - header: "Next"
 - question: "What now?"
 - options:
-  - "Continue working" - Back to /gsd:progress
+  - "Continue working" - Back to /gsd-progress
   - "Test more" - Verify related functionality
   - "Done" - End session
 </step>

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>
@@ -256,8 +256,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-milestone.md

@@ -24,8 +24,8 @@ Current milestone in progress: v[X.Y] [Name]
 Phases [N]-[M], [P]% complete
 
 Did you want to:
-1. Complete current milestone first (/gsd:complete-milestone)
-2. Add phases to current milestone (/gsd:add-phase)
+1. Complete current milestone first (/gsd-complete-milestone)
+2. Add phases to current milestone (/gsd-add-phase)
 3. Continue anyway - discuss next milestone scope
 
 ```
@@ -113,7 +113,7 @@ Use question:
 - header: "Ready?"
 - question: "Ready to create the milestone, or explore more?"
 - options (ALL THREE REQUIRED):
-  - "Create milestone" - Proceed to /gsd:new-milestone
+  - "Create milestone" - Proceed to /gsd-new-milestone
   - "Ask more questions" - Help me think through this more
   - "Let me add context" - I have more to share
 
@@ -142,7 +142,7 @@ cat > .planning/MILESTONE-CONTEXT.md << 'EOF'
 # Milestone Context
 
 **Generated:** [today's date]
-**Status:** Ready for /gsd:new-milestone
+**Status:** Ready for /gsd-new-milestone
 
 <features>
 ## Features to Build
@@ -187,7 +187,7 @@ cat > .planning/MILESTONE-CONTEXT.md << 'EOF'
 
 ---
 
-*This file is temporary. It will be deleted after /gsd:new-milestone creates the milestone.*
+*This file is temporary. It will be deleted after /gsd-new-milestone creates the milestone.*
 EOF
 ```
 </step>
@@ -214,7 +214,7 @@ Context saved to `.planning/MILESTONE-CONTEXT.md`
 
 **Create Milestone v[X.Y]** — [Theme Name]
 
-`/gsd:new-milestone`
+`/gsd-new-milestone`
 
 *`/clear` first → fresh context window*
 
@@ -232,5 +232,5 @@ Context saved to `.planning/MILESTONE-CONTEXT.md`
 - Features explored with clarifying questions
 - Scope synthesized from features (not asked abstractly)
 - **MILESTONE-CONTEXT.md created** with features, scope, and phase mapping
-- Context handed off to /gsd:new-milestone
+- Context handed off to /gsd-new-milestone
 </success_criteria>

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

@@ -5,7 +5,7 @@ You are a thinking partner, not an interviewer. The user is the visionary — yo
 </purpose>
 
 <philosophy>
-**User = founder/visionary. Claude = builder.**
+**User = founder/visionary. Opencode agent = builder.**
 
 The user doesn't know (and shouldn't need to know):
 - Codebase patterns (you read the code)
@@ -42,7 +42,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.
@@ -190,14 +190,14 @@ Created: .planning/phases/${PHASE}-${SLUG}/${PHASE}-CONTEXT.md
 
 **Phase ${PHASE}: [Name]** — [Goal from ROADMAP.md]
 
-`/gsd:plan-phase ${PHASE}`
+`/gsd-plan-phase ${PHASE}`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:research-phase ${PHASE}` — investigate unknowns
+- `/gsd-research-phase ${PHASE}` — investigate unknowns
 - Review/edit CONTEXT.md before continuing
 
 ---

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

@@ -102,7 +102,7 @@ waves = {
 }
 ```
 
-**No dependency analysis needed.** Wave numbers are pre-computed during `/gsd:plan-phase`.
+**No dependency analysis needed.** Wave numbers are pre-computed during `/gsd-plan-phase`.
 
 Report wave structure to user:
 ```
@@ -314,7 +314,7 @@ Present next steps based on milestone status:
 
 **Phase {X+1}: {Name}** — {Goal}
 
-`/gsd:plan-phase {X+1}`
+`/gsd-plan-phase {X+1}`
 
 *`/clear` first for fresh context*
 ```
@@ -325,7 +325,7 @@ MILESTONE COMPLETE!
 
 All {N} phases executed.
 
-`/gsd:complete-milestone`
+`/gsd-complete-milestone`
 ```
 </step>
 
@@ -380,7 +380,7 @@ Each subagent: Fresh 200k context
 
 If phase execution was interrupted (context limit, user exit, error):
 
-1. Run `/gsd:execute-phase {phase}` again
+1. Run `/gsd-execute-phase {phase}` again
 2. discover_plans finds completed SUMMARYs
 3. Skips completed plans
 4. Resumes from first incomplete plan

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

@@ -1069,7 +1069,7 @@ TASK_COMMITS+=("Task ${TASK_NUM}: ${TASK_COMMIT}")
 - Each task independently revertable
 - Git bisect finds exact failing task
 - Git blame traces line to specific task context
-- Clear history for Claude in future sessions
+- Clear history for Opencode agent in future sessions
 - Better observability for AI-automated workflow
 
 </task_commit>
@@ -1077,7 +1077,7 @@ TASK_COMMITS+=("Task ${TASK_NUM}: ${TASK_COMMIT}")
 <step name="checkpoint_protocol">
 When encountering `type="checkpoint:*"`:
 
-**Critical: Claude automates everything with CLI/API before checkpoints.** Checkpoints are for verification and decisions, not manual work.
+**Critical: Opencode agent automates everything with CLI/API before checkpoints.** Checkpoints are for verification and decisions, not manual work.
 
 **Display checkpoint clearly:**
 
@@ -1129,7 +1129,7 @@ Options:
 **For checkpoint:human-action (1% - rare, only for truly unavoidable manual steps):**
 
 ```
-I automated: [what Claude already did via CLI/API]
+I automated: [what Opencode agent already did via CLI/API]
 
 Need your help with: [the ONE thing with no CLI/API - email link, 2FA code]
 
@@ -1224,7 +1224,7 @@ You will NOT be resumed. A new agent continues from where you stopped, using you
 
 **How to know if you were spawned:**
 
-If you're reading this workflow because an orchestrator spawned you (vs running directly from /gsd:execute-plan), the orchestrator's prompt will include checkpoint return instructions. Follow those instructions when you hit a checkpoint.
+If you're reading this workflow because an orchestrator spawned you (vs running directly from /gsd-execute-plan), the orchestrator's prompt will include checkpoint return instructions. Follow those instructions when you hit a checkpoint.
 
 **If running in main context (not spawned):**
 
@@ -1609,18 +1609,18 @@ Use question:
 - header: "Phase Issues"
 - question: "[N] issues were logged during this phase. Review now?"
 - options:
-  - "Review issues" - Analyze with /gsd:consider-issues
+  - "Review issues" - Analyze with /gsd-consider-issues
   - "Continue" - Address later, proceed to next work
 
 **If "Review issues" selected:**
-- Invoke: `[removed - use /command syntax]("/gsd:consider-issues")`
+- Invoke: `[removed - use /command syntax]("/gsd-consider-issues")`
 - After consider-issues completes, return to offer_next
 
 **If "Continue" selected or no issues found:**
 - Proceed to offer_next step
 
 **In YOLO mode:**
-- Note issues were logged but don't prompt: `📋 [N] issues logged this phase (review later with /gsd:consider-issues)`
+- Note issues were logged but don't prompt: `📋 [N] issues logged this phase (review later with /gsd-consider-issues)`
 - Continue to offer_next automatically
 </step>
 
@@ -1683,14 +1683,14 @@ Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
 
 **{phase}-{next-plan}: [Plan Name]** — [objective from next PLAN.md]
 
-`/gsd:execute-plan .planning/phases/{phase-dir}/{phase}-{next-plan}-PLAN.md`
+`/gsd-execute-plan .planning/phases/{phase-dir}/{phase}-{next-plan}-PLAN.md`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:verify-work {phase}-{plan}` — manual acceptance testing before continuing
+- `/gsd-verify-work {phase}-{plan}` — manual acceptance testing before continuing
 - Review what was built before continuing
 
 ---
@@ -1744,16 +1744,16 @@ All {Y} plans finished.
 
 **Phase {Z+1}: {Next Phase Name}** — {Goal from ROADMAP.md}
 
-`/gsd:plan-phase {Z+1}`
+`/gsd-plan-phase {Z+1}`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:verify-work {Z}` — manual acceptance testing before continuing
-- `/gsd:discuss-phase {Z+1}` — gather context first
-- `/gsd:research-phase {Z+1}` — investigate unknowns
+- `/gsd-verify-work {Z}` — manual acceptance testing before continuing
+- `/gsd-discuss-phase {Z+1}` — gather context first
+- `/gsd-research-phase {Z+1}` — investigate unknowns
 - Review phase accomplishments before continuing
 
 ---
@@ -1784,15 +1784,15 @@ Milestone is 100% done.
 
 **Complete Milestone** — archive and prepare for next
 
-`/gsd:complete-milestone`
+`/gsd-complete-milestone`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:verify-work` — manual acceptance testing before completing milestone
-- `/gsd:add-phase <description>` — add another phase before completing
+- `/gsd-verify-work` — manual acceptance testing before completing milestone
+- `/gsd-add-phase <description>` — add another phase before completing
 - Review accomplishments before archiving
 
 ---

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

@@ -1,7 +1,7 @@
 <purpose>
 Surface Claude's assumptions about a phase before planning, enabling users to correct misconceptions early.
 
-Key difference from discuss-phase: This is ANALYSIS of what Claude thinks, not INTAKE of what user knows. No file output - purely conversational to prompt discussion.
+Key difference from discuss-phase: This is ANALYSIS of what Opencode agent thinks, not INTAKE of what user knows. No file output - purely conversational to prompt discussion.
 </purpose>
 
 <process>
@@ -14,8 +14,8 @@ Phase number: $ARGUMENTS (required)
 ```
 Error: Phase number required.
 
-Usage: /gsd:list-phase-assumptions [phase-number]
-Example: /gsd:list-phase-assumptions 3
+Usage: /gsd-list-phase-assumptions [phase-number]
+Example: /gsd-list-phase-assumptions 3
 ```
 
 Exit workflow.
@@ -53,13 +53,13 @@ Continue to analyze_phase.
 Based on roadmap description and project context, identify assumptions across five areas:
 
 **1. Technical Approach:**
-What libraries, frameworks, patterns, or tools would Claude use?
+What libraries, frameworks, patterns, or tools would Opencode agent use?
 - "I'd use X library because..."
 - "I'd follow Y pattern because..."
 - "I'd structure this as Z because..."
 
 **2. Implementation Order:**
-What would Claude build first, second, third?
+What would Opencode agent build first, second, third?
 - "I'd start with X because it's foundational"
 - "Then Y because it depends on X"
 - "Finally Z because..."
@@ -71,13 +71,13 @@ What's included vs excluded in Claude's interpretation?
 - "Boundary ambiguities: G could go either way"
 
 **4. Risk Areas:**
-Where does Claude expect complexity or challenges?
+Where does Opencode agent expect complexity or challenges?
 - "The tricky part is X because..."
 - "Potential issues: Y, Z"
 - "I'd watch out for..."
 
 **5. Dependencies:**
-What does Claude assume exists or needs to be in place?
+What does Opencode agent assume exists or needs to be in place?
 - "This assumes X from previous phases"
 - "External dependencies: Y, Z"
 - "This will be consumed by..."
@@ -153,8 +153,8 @@ Present next steps:
 
 ```
 What's next?
-1. Discuss context (/gsd:discuss-phase ${PHASE}) - Let me ask you questions to build comprehensive context
-2. Plan this phase (/gsd:plan-phase ${PHASE}) - Create detailed execution plans
+1. Discuss context (/gsd-discuss-phase ${PHASE}) - Let me ask you questions to build comprehensive context
+2. Plan this phase (/gsd-plan-phase ${PHASE}) - Create detailed execution plans
 3. Re-examine assumptions - I'll analyze again with your corrections
 4. Done for now
 ```

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 agent 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 agent 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*
 
 ---
 
 **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 agent 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,12 +638,12 @@ 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*
 
@@ -651,7 +651,7 @@ Wave 2: {plan-03}
 
 **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`]
 
 ---