gsd-opencode 1.4.2 → 1.5.0

package/command/gsd/plan-phase.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:plan-phase
+name: gsd-plan-phase
 description: Create detailed execution plan for a phase (PLAN.md)
 argument-hint: "[phase]"
 allowed-tools:
@@ -30,7 +30,7 @@ Output: One or more PLAN.md files in the phase directory (.planning/phases/XX-na
 </execution_context>
 
 <context>
-Phase number: ($ARGUMENTS) (optional - auto-detects next unplanned phase if not provided)
+Phase number: $ARGUMENTS (optional - auto-detects next unplanned phase if not provided)
 
 **Load project state first:**
 @.planning/STATE.md
@@ -38,7 +38,7 @@ Phase number: ($ARGUMENTS) (optional - auto-detects next unplanned phase if not
 **Load roadmap:**
 @.planning/ROADMAP.md
 
-**Load phase context if exists (created by /gsd:discuss-phase):**
+**Load phase context if exists (created by /gsd-discuss-phase):**
 Check for and read `.planning/phases/XX-name/{phase}-CONTEXT.md` - contains research findings, clarifications, and decisions from phase discussion.
 
 **Load codebase context if exists:**
@@ -46,8 +46,8 @@ Check for `.planning/codebase/` and load relevant documents based on phase type.
 </context>
 
 <process>
-1. Check .planning/ directory exists (error if not - user should run /gsd:new-project)
-2. If phase number provided via ($ARGUMENTS), validate it exists in roadmap
+1. Check .planning/ directory exists (error if not - user should run /gsd-new-project)
+2. If phase number provided via `$ARGUMENTS`, validate it exists in roadmap
 3. If no phase number, detect next unplanned phase from roadmap
 4. Follow plan-phase.md workflow:
    - Load project state and accumulated decisions

package/command/gsd/progress.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:progress
+name: gsd-progress
 description: Check project progress, show context, and route to next action (execute or plan)
 allowed-tools:
   - read
@@ -25,12 +25,12 @@ If no `.planning/` directory:
 ```
 No planning structure found.
 
-Run /gsd:new-project to start a new project.
+Run /gsd-new-project to start a new project.
 ```
 
 Exit.
 
-If missing STATE.md or ROADMAP.md: inform what's missing, suggest running `/gsd:new-project`.
+If missing STATE.md or ROADMAP.md: inform what's missing, suggest running `/gsd-new-project`.
 </step>
 
 <step name="load">
@@ -85,10 +85,10 @@ CONTEXT: [✓ if CONTEXT.md exists | - if not]
 - [any deferred issues or blockers]
 
 ## Pending Todos
-- [count] pending — /gsd:check-todos to review
+- [count] pending — /gsd-check-todos to review
 
 ## Active Debug Sessions
-- [count] active — /gsd:debug to continue
+- [count] active — /gsd-debug to continue
 (Only show this section if count > 0)
 
 ## What's Next
@@ -147,7 +147,7 @@ Read its `<objective>` section.
 
 **{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
 
-`/gsd:execute-plan [full-path-to-PLAN.md]`
+`/gsd-execute-plan [full-path-to-PLAN.md]`
 
 *`/clear` first → fresh context window*
 
@@ -170,7 +170,7 @@ Check if `{phase}-CONTEXT.md` exists in phase directory.
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 *✓ Context gathered, ready to plan*
 
-`/gsd:plan-phase {phase-number}`
+`/gsd-plan-phase {phase-number}`
 
 *`/clear` first → fresh context window*
 
@@ -186,16 +186,16 @@ Check if `{phase}-CONTEXT.md` exists in phase directory.
 
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 
-`/gsd:plan-phase {phase}`
+`/gsd-plan-phase {phase}`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:discuss-phase {phase}` — gather context first
-- `/gsd:research-phase {phase}` — investigate unknowns
-- `/gsd:list-phase-assumptions {phase}` — see OpenCode's assumptions
+- `/gsd-discuss-phase {phase}` — gather context first
+- `/gsd-research-phase {phase}` — investigate unknowns
+- `/gsd-list-phase-assumptions {phase}` — see OpenCode's assumptions
 
 ---
 ```
@@ -213,15 +213,15 @@ ISSUES.md exists without matching FIX.md. User needs to plan fixes.
 
 **{plan}-ISSUES.md** has {N} issues without a fix plan.
 
-`/gsd:plan-fix {plan}`
+`/gsd-plan-fix {plan}`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:execute-plan [path]` — continue with other work first
-- `/gsd:verify-work {phase}` — run more UAT testing
+- `/gsd-execute-plan [path]` — continue with other work first
+- `/gsd-verify-work {phase}` — run more UAT testing
 
 ---
 ```
@@ -260,16 +260,16 @@ Read ROADMAP.md to get the next phase's name and goal.
 
 **Phase {Z+1}: {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}` — user acceptance test before continuing
-- `/gsd:discuss-phase {Z+1}` — gather context first
-- `/gsd:research-phase {Z+1}` — investigate unknowns
+- `/gsd-verify-work {Z}` — user acceptance test before continuing
+- `/gsd-discuss-phase {Z+1}` — gather context first
+- `/gsd-research-phase {Z+1}` — investigate unknowns
 
 ---
 ```
@@ -289,14 +289,14 @@ All {N} phases finished!
 
 **Complete Milestone** — archive and prepare for next
 
-`/gsd:complete-milestone`
+`/gsd-complete-milestone`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:verify-work` — user acceptance test before completing milestone
+- `/gsd-verify-work` — user acceptance test before completing milestone
 
 ---
 ```
@@ -306,10 +306,10 @@ All {N} phases finished!
 <step name="edge_cases">
 **Handle edge cases:**
 
-- Phase complete but next phase not planned → offer `/gsd:plan-phase [next]`
+- Phase complete but next phase not planned → offer `/gsd-plan-phase [next]`
 - All work complete → offer milestone completion
 - Blockers present → highlight before offering to continue
-- Handoff file exists → mention it, offer `/gsd:resume-work`
+- Handoff file exists → mention it, offer `/gsd-resume-work`
   </step>
 
 </process>
@@ -319,7 +319,7 @@ All {N} phases finished!
 - [ ] Rich context provided (recent work, decisions, issues)
 - [ ] Current position clear with visual progress
 - [ ] What's next clearly explained
-- [ ] Smart routing: /gsd:execute-plan if plan exists, /gsd:plan-phase if not
+- [ ] Smart routing: /gsd-execute-plan if plan exists, /gsd-plan-phase if not
 - [ ] User confirms before any action
 - [ ] Seamless handoff to appropriate gsd command
       </success_criteria>

package/command/gsd/remove-phase.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:remove-phase
+name: gsd-remove-phase
 description: Remove a future phase from roadmap and renumber subsequent phases
 argument-hint: <phase-number>
 allowed-tools:
@@ -19,6 +19,8 @@ Output: Phase deleted, all subsequent phases renumbered, git commit as historica
 <execution_context>
 @.planning/ROADMAP.md
 @.planning/STATE.md
+
+Phase number: $ARGUMENTS
 </execution_context>
 
 <process>
@@ -26,15 +28,15 @@ Output: Phase deleted, all subsequent phases renumbered, git commit as historica
 <step name="parse_arguments">
 Parse the command arguments:
 - Argument is the phase number to remove (integer or decimal)
-- Example: `/gsd:remove-phase 17` → phase = 17
-- Example: `/gsd:remove-phase 16.1` → phase = 16.1
+- Example: `/gsd-remove-phase 17` → phase = 17
+- Example: `/gsd-remove-phase 16.1` → phase = 16.1
 
 If no argument provided:
 
 ```
 ERROR: Phase number required
-Usage: /gsd:remove-phase <phase-number>
-Example: /gsd:remove-phase 17
+Usage: /gsd-remove-phase <phase-number>
+Example: /gsd-remove-phase 17
 ```
 
 Exit.
@@ -80,7 +82,7 @@ Only future phases can be removed:
 - Current phase: {current}
 - Phase {target} is current or completed
 
-To abandon current work, use /gsd:pause-work instead.
+To abandon current work, use /gsd-pause-work instead.
 ```
 
 Exit.
@@ -280,7 +282,7 @@ Current position: Phase {current} of {new-total}
 ## What's Next
 
 Would you like to:
-- `/gsd:progress` — see updated roadmap status
+- `/gsd-progress` — see updated roadmap status
 - Continue with current phase
 - Review roadmap
 

package/command/gsd/research-phase.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:research-phase
+name: gsd-research-phase
 description: Research how to implement a phase before planning
 argument-hint: "[phase]"
 allowed-tools:
@@ -33,7 +33,7 @@ Output: RESEARCH.md with ecosystem knowledge that informs quality planning.
 </execution_context>
 
 <context>
-Phase number: ($ARGUMENTS) (required)
+Phase number: $ARGUMENTS (required)
 
 **Load project state:**
 @.planning/STATE.md

package/command/gsd/resume-work.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:resume-work
+name: gsd-resume-work
 description: Resume work from previous session with full context restoration
 allowed-tools:
   - read

package/command/gsd/status.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:status
+name: gsd-status
 description: Check status of background agents from parallel execution
 argument-hint: "[--wait]"
 allowed-tools:
@@ -9,14 +9,14 @@ allowed-tools:
 ---
 
 <objective>
-Monitor background agent status from /gsd:execute-phase parallel execution.
+Monitor background agent status from /gsd-execute-phase parallel execution.
 
 Shows running/completed agents from agent-history.json.
 With --wait flag, blocks until all agents complete.
 </objective>
 
 <context>
-Arguments: ($ARGUMENTS)
+Arguments: $ARGUMENTS
 </context>
 
 <process>
@@ -32,7 +32,7 @@ If file doesn't exist or has no entries:
 ```
 No background agents tracked.
 
-Run /gsd:execute-phase to spawn parallel agents.
+Run /gsd-execute-phase to spawn parallel agents.
 ```
 Exit.
 </step>
@@ -63,7 +63,7 @@ Background Agents
 Progress: 2/3 complete
 
 ════════════════════════════════════════
-Wait for all: /gsd:status --wait
+Wait for all: /gsd-status --wait
 ```
 
 **Status icons:**
@@ -108,7 +108,7 @@ Update agent-history.json with completion status for each.
 
 All parallel agents finished. Review results:
 
-`/gsd:progress`
+`/gsd-progress`
 
 *`/clear` first → fresh context window*
 

package/command/gsd/verify-work.md

@@ -1,5 +1,5 @@
 ---
-name: gsd:verify-work
+name: gsd-verify-work
 description: Guide manual user acceptance testing of recently built features
 argument-hint: "[optional: phase or plan number, e.g., '4' or '04-02']"
 allowed-tools:
@@ -26,7 +26,7 @@ Output: Validation of features, any issues logged to phase-scoped ISSUES.md
 </execution_context>
 
 <context>
-Scope: ($ARGUMENTS) (optional)
+Scope: $ARGUMENTS (optional)
 - If provided: Test specific phase or plan (e.g., "4" or "04-02")
 - If not provided: Test most recently completed plan
 
@@ -49,7 +49,7 @@ Scope: ($ARGUMENTS) (optional)
    - Present summary with verdict
 4. Offer next steps based on results:
    - If all passed: Continue to next phase
-   - If issues found: `/gsd:plan-fix {phase} {plan}` to create fix plan
+   - If issues found: `/gsd-plan-fix {phase} {plan}` to create fix plan
 </process>
 
 <anti_patterns>

package/get-shit-done/references/checkpoints.md

@@ -1,21 +1,21 @@
 <overview>
 Plans execute autonomously. Checkpoints formalize interaction points where human verification or decisions are needed.
 
-**Core principle:** Claude automates everything with CLI/API. Checkpoints are for verification and decisions, not manual work.
+**Core principle:** Opencode agent automates everything with CLI/API. Checkpoints are for verification and decisions, not manual work.
 </overview>
 
 <checkpoint_types>
 
 ## checkpoint:human-verify (90% of checkpoints)
 
-**When:** Claude completed automated work, human confirms it works correctly.
+**When:** Opencode agent completed automated work, human confirms it works correctly.
 
 **Use for:** Visual UI checks, interactive flows, functional verification, audio/video quality, animation smoothness, accessibility testing.
 
 **Structure:**
 ```xml
 <task type="checkpoint:human-verify" gate="blocking">
-  <what-built>[What Claude automated]</what-built>
+  <what-built>[What Opencode agent automated]</what-built>
   <how-to-verify>[Numbered steps - URLs, commands, expected behavior]</how-to-verify>
   <resume-signal>[How to continue - "approved" or describe issues]</resume-signal>
 </task>
@@ -86,8 +86,8 @@ Plans execute autonomously. Checkpoints formalize interaction points where human
 ```xml
 <task type="checkpoint:human-action" gate="blocking">
   <action>[Unavoidable manual step]</action>
-  <instructions>[What Claude automated] [ONE thing requiring human action]</instructions>
-  <verification>[What Claude checks afterward]</verification>
+  <instructions>[What Opencode agent automated] [ONE thing requiring human action]</instructions>
+  <verification>[What Opencode agent checks afterward]</verification>
   <resume-signal>[How to continue]</resume-signal>
 </task>
 ```
@@ -109,7 +109,7 @@ Plans execute autonomously. Checkpoints formalize interaction points where human
 
 <execution_protocol>
 
-When Claude encounters `type="checkpoint:*"`:
+When Opencode agent encounters `type="checkpoint:*"`:
 
 1. **Stop immediately** - do not proceed to next task
 2. **Display checkpoint clearly:**
@@ -135,9 +135,9 @@ Task [X] of [Y]: [Name]
 
 <authentication_gates>
 
-**Critical:** When Claude tries CLI/API and gets auth error, this is NOT a failure - it's a gate requiring human input to unblock automation.
+**Critical:** When Opencode agent tries CLI/API and gets auth error, this is NOT a failure - it's a gate requiring human input to unblock automation.
 
-**Pattern:** Claude tries automation → auth error → creates checkpoint → you authenticate → Claude retries → continues
+**Pattern:** Opencode agent tries automation → auth error → creates checkpoint → you authenticate → Opencode agent retries → continues
 
 **Gate protocol:**
 1. Recognize it's not a failure - missing auth is expected
@@ -150,7 +150,7 @@ Task [X] of [Y]: [Name]
 
 **Example (Vercel auth gate):**
 ```xml
-<!-- Claude tries to deploy -->
+<!-- Opencode agent tries to deploy -->
 <task type="auto">
   <name>Deploy to Vercel</name>
   <action>Run `vercel --yes` to deploy</action>
@@ -167,7 +167,7 @@ Task [X] of [Y]: [Name]
   <resume-signal>Type "done" when authenticated</resume-signal>
 </task>
 
-<!-- After auth, Claude retries automatically -->
+<!-- After auth, Opencode agent retries automatically -->
 <task type="auto">
   <name>Retry deployment</name>
   <action>Run `vercel --yes` (now authenticated)</action>
@@ -175,14 +175,14 @@ Task [X] of [Y]: [Name]
 ```
 
 **Key distinction:**
-- Pre-planned checkpoint: "I need you to do X" (wrong - Claude should automate)
+- Pre-planned checkpoint: "I need you to do X" (wrong - Opencode agent should automate)
 - Auth gate: "I tried to automate X but need credentials" (correct - unblocks automation)
 
 </authentication_gates>
 
 <automation_reference>
 
-**The rule:** If it has CLI/API, Claude does it. Never ask human to perform automatable work.
+**The rule:** If it has CLI/API, Opencode agent does it. Never ask human to perform automatable work.
 
 | Service | CLI/API | Key Commands | Auth Gate |
 |---------|---------|--------------|-----------|
@@ -201,7 +201,7 @@ Task [X] of [Y]: [Name]
 
 **Quick reference:**
 
-| Action | Automatable? | Claude does it? |
+| Action | Automatable? | Opencode agent does it? |
 |--------|--------------|-----------------|
 | Deploy to Vercel | Yes (`vercel`) | YES |
 | Create Stripe webhook | Yes (API) | YES |
@@ -223,7 +223,7 @@ Task [X] of [Y]: [Name]
 - Make verification executable
 
 **DON'T:**
-- Ask human to do work Claude can automate
+- Ask human to do work Opencode agent can automate
 - Assume knowledge: "Configure the usual settings"
 - Mix multiple verifications in one checkpoint
 - Use checkpoints too frequently (verification fatigue)
@@ -256,7 +256,7 @@ Why bad: Vercel has CLI. Use `vercel --yes`.
 ```
 Why bad: Verification fatigue. Combine into one checkpoint at end.
 
-**GOOD: Claude automates, human verifies once**
+**GOOD: Opencode agent automates, human verifies once**
 ```xml
 <task type="auto">Create schema</task>
 <task type="auto">Create API</task>
@@ -272,16 +272,16 @@ Why bad: Verification fatigue. Combine into one checkpoint at end.
 
 <summary>
 
-**The golden rule:** If Claude CAN automate it, Claude MUST automate it.
+**The golden rule:** If Opencode agent CAN automate it, Opencode agent MUST automate it.
 
 **Checkpoint priority:**
-1. **checkpoint:human-verify** (90%) - Claude automated, human confirms visual/functional correctness
+1. **checkpoint:human-verify** (90%) - Opencode agent automated, human confirms visual/functional correctness
 2. **checkpoint:decision** (9%) - Human makes architectural/technology choices
 3. **checkpoint:human-action** (1%) - Truly unavoidable manual steps with no API/CLI
 
 **When NOT to use checkpoints:**
-- Things Claude can verify programmatically (tests, builds)
-- File operations (Claude can read/write)
+- Things Opencode agent can verify programmatically (tests, builds)
+- File operations (Opencode agent can read/write)
 - Anything with CLI/API available
 
 </summary>

package/get-shit-done/references/continuation-format.md

@@ -44,7 +44,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
 
-`/gsd:execute-plan .planning/phases/02-auth/02-03-PLAN.md`
+`/gsd-execute-plan .planning/phases/02-auth/02-03-PLAN.md`
 
 *`/clear` first → fresh context window*
 
@@ -52,7 +52,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 **Also available:**
 - Review plan before executing
-- `/gsd:list-phase-assumptions 2` — check assumptions
+- `/gsd-list-phase-assumptions 2` — check assumptions
 
 ---
 ```
@@ -69,7 +69,7 @@ Add note that this is the last plan and what comes after:
 **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
 *Final plan in Phase 2*
 
-`/gsd:execute-plan .planning/phases/02-auth/02-03-PLAN.md`
+`/gsd-execute-plan .planning/phases/02-auth/02-03-PLAN.md`
 
 *`/clear` first → fresh context window*
 
@@ -91,15 +91,15 @@ Add note that this is the last plan and what comes after:
 
 **Phase 2: Authentication** — JWT login flow with refresh tokens
 
-`/gsd:plan-phase 2`
+`/gsd-plan-phase 2`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:discuss-phase 2` — gather context first
-- `/gsd:research-phase 2` — investigate unknowns
+- `/gsd-discuss-phase 2` — gather context first
+- `/gsd-research-phase 2` — investigate unknowns
 - Review roadmap
 
 ---
@@ -120,15 +120,15 @@ Show completion status before next action:
 
 **Phase 3: Core Features** — User dashboard, settings, and data export
 
-`/gsd:plan-phase 3`
+`/gsd-plan-phase 3`
 
 *`/clear` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd:discuss-phase 3` — gather context first
-- `/gsd:research-phase 3` — investigate unknowns
+- `/gsd-discuss-phase 3` — gather context first
+- `/gsd-research-phase 3` — investigate unknowns
 - Review what Phase 2 built
 
 ---
@@ -145,11 +145,11 @@ When there's no clear primary action:
 
 **Phase 3: Core Features** — User dashboard, settings, and data export
 
-**To plan directly:** `/gsd:plan-phase 3`
+**To plan directly:** `/gsd-plan-phase 3`
 
-**To discuss context first:** `/gsd:discuss-phase 3`
+**To discuss context first:** `/gsd-discuss-phase 3`
 
-**To research unknowns:** `/gsd:research-phase 3`
+**To research unknowns:** `/gsd-research-phase 3`
 
 *`/clear` first → fresh context window*
 
@@ -169,14 +169,14 @@ All 4 phases shipped
 
 **Plan v1.1** — Enhanced features and optimizations
 
-`/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
 - Review accomplishments before moving on
 
 ---
@@ -220,7 +220,7 @@ Extract: `**02-03: Refresh Token Rotation** — Add /api/auth/refresh with slidi
 ## To Continue
 
 Run `/clear`, then paste:
-/gsd:execute-plan .planning/phases/02-auth/02-03-PLAN.md
+/gsd-execute-plan .planning/phases/02-auth/02-03-PLAN.md
 ```
 
 User has no idea what 02-03 is about.
@@ -228,7 +228,7 @@ User has no idea what 02-03 is about.
 ### Don't: Missing /clear explanation
 
 ```
-`/gsd:plan-phase 3`
+`/gsd-plan-phase 3`
 
 Run /clear first.
 ```
@@ -248,7 +248,7 @@ Sounds like an afterthought. Use "Also available:" instead.
 
 ```
 ```
-/gsd:plan-phase 3
+/gsd-plan-phase 3
 ```
 ```
 

package/get-shit-done/references/git-integration.md

@@ -231,14 +231,14 @@ Each plan produces 2-4 commits (tasks + metadata). Clear, granular, bisectable.
 ## Why Per-Task Commits?
 
 **Context engineering for AI:**
-- Git history becomes primary context source for future Claude sessions
+- Git history becomes primary context source for future Opencode agent sessions
 - `git log --grep="{phase}-{plan}"` shows all work for a plan
 - `git diff <hash>^..<hash>` shows exact changes per task
 - Less reliance on parsing SUMMARY.md = more context for actual work
 
 **Failure recovery:**
 - Task 1 committed ✅, Task 2 failed ❌
-- Claude in next session: sees task 1 complete, can retry task 2
+- Opencode agent in next session: sees task 1 complete, can retry task 2
 - Can `git reset --hard` to last successful task
 
 **Debugging:**
@@ -247,7 +247,7 @@ Each plan produces 2-4 commits (tasks + metadata). Clear, granular, bisectable.
 - Each commit is independently revertable
 
 **Observability:**
-- Solo developer + Claude workflow benefits from granular attribution
+- Solo developer + Opencode agent workflow benefits from granular attribution
 - Atomic commits are git best practice
 - "Commit noise" irrelevant when consumer is Claude, not humans