gsd-opencode 1.5.0 → 1.6.0

package/command/gsd/progress.md

@@ -1,7 +1,7 @@
 ---
 name: gsd-progress
 description: Check project progress, show context, and route to next action (execute or plan)
-allowed-tools:
+tools:
   - read
   - bash
   - grep
@@ -30,15 +30,21 @@ 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: suggest `/gsd-new-project`.
+
+**If ROADMAP.md missing but PROJECT.md exists:**
+
+This means a milestone was completed and archived. Go to **Route F** (between milestones).
+
+If missing both ROADMAP.md and PROJECT.md: suggest `/gsd-new-project`.
 </step>
 
 <step name="load">
 **Load full project context:**
 
-- Read `.planning/STATE.md` for living memory (position, decisions, issues)
-- Read `.planning/ROADMAP.md` for phase structure and objectives
-- Read `.planning/PROJECT.md` for current state (What This Is, Core Value, Requirements)
+- read `.planning/STATE.md` for living memory (position, decisions, issues)
+- read `.planning/ROADMAP.md` for phase structure and objectives
+- read `.planning/PROJECT.md` for current state (What This Is, Core Value, Requirements)
   </step>
 
 <step name="recent">
@@ -54,7 +60,7 @@ If missing STATE.md or ROADMAP.md: inform what's missing, suggest running `/gsd-
 
 - From STATE.md: current phase, plan number, status
 - Calculate: total plans, completed plans, remaining plans
-- Note any blockers, concerns, or deferred issues
+- Note any blockers or concerns
 - Check for CONTEXT.md: For phases without PLAN.md files, check if `{phase}-CONTEXT.md` exists in phase directory
 - Count pending todos: `ls .planning/todos/pending/*.md 2>/dev/null | wc -l`
 - Check for active debug sessions: `ls .planning/debug/*.md 2>/dev/null | grep -v resolved | wc -l`
@@ -81,8 +87,8 @@ CONTEXT: [✓ if CONTEXT.md exists | - if not]
 - [decision 1 from STATE.md]
 - [decision 2]
 
-## Open Issues
-- [any deferred issues or blockers]
+## Blockers/Concerns
+- [any blockers or concerns from STATE.md]
 
 ## Pending Todos
 - [count] pending — /gsd-check-todos to review
@@ -107,28 +113,28 @@ List files in the current phase directory:
 ```bash
 ls -1 .planning/phases/[current-phase-dir]/*-PLAN.md 2>/dev/null | wc -l
 ls -1 .planning/phases/[current-phase-dir]/*-SUMMARY.md 2>/dev/null | wc -l
-ls -1 .planning/phases/[current-phase-dir]/*-ISSUES.md 2>/dev/null | wc -l
-ls -1 .planning/phases/[current-phase-dir]/*-FIX.md 2>/dev/null | wc -l
-ls -1 .planning/phases/[current-phase-dir]/*-FIX-SUMMARY.md 2>/dev/null | wc -l
+ls -1 .planning/phases/[current-phase-dir]/*-UAT.md 2>/dev/null | wc -l
 ```
 
-State: "This phase has {X} plans, {Y} summaries, {Z} issues files, {W} fix plans."
+State: "This phase has {X} plans, {Y} summaries."
 
-**Step 1.5: Check for unaddressed UAT issues**
+**Step 1.5: Check for unaddressed UAT gaps**
 
-For each *-ISSUES.md file, check if matching *-FIX.md exists.
-For each *-FIX.md file, check if matching *-FIX-SUMMARY.md exists.
+Check for UAT.md files with status "diagnosed" (has gaps needing fixes).
+
+```bash
+# Check for diagnosed UAT with gaps
+grep -l "status: diagnosed" .planning/phases/[current-phase-dir]/*-UAT.md 2>/dev/null
+```
 
 Track:
-- `issues_without_fix`: ISSUES.md files without FIX.md
-- `fixes_without_summary`: FIX.md files without FIX-SUMMARY.md
+- `uat_with_gaps`: UAT.md files with status "diagnosed" (gaps need fixing)
 
 **Step 2: Route based on counts**
 
 | Condition | Meaning | Action |
 |-----------|---------|--------|
-| fixes_without_summary > 0 | Unexecuted fix plans exist | Go to **Route A** (with FIX.md) |
-| issues_without_fix > 0 | UAT issues need fix plans | Go to **Route E** |
+| uat_with_gaps > 0 | UAT gaps need fix plans | Go to **Route E** |
 | summaries < plans | Unexecuted plans exist | Go to **Route A** |
 | summaries = plans AND plans > 0 | Phase complete | Go to Step 3 |
 | plans = 0 | Phase not yet planned | Go to **Route B** |
@@ -138,7 +144,7 @@ Track:
 **Route A: Unexecuted plan exists**
 
 Find the first PLAN.md without matching SUMMARY.md.
-Read its `<objective>` section.
+read its `<objective>` section.
 
 ```
 ---
@@ -147,9 +153,9 @@ Read its `<objective>` section.
 
 **{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
 
-`/gsd-execute-plan [full-path-to-PLAN.md]`
+`/gsd-execute-phase {phase}`
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 ```
@@ -172,7 +178,7 @@ Check if `{phase}-CONTEXT.md` exists in phase directory.
 
 `/gsd-plan-phase {phase-number}`
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 ```
@@ -186,15 +192,14 @@ Check if `{phase}-CONTEXT.md` exists in phase directory.
 
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 
-`/gsd-plan-phase {phase}`
+`/gsd-discuss-phase {phase}` — gather context and clarify approach
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd-discuss-phase {phase}` — gather context first
-- `/gsd-research-phase {phase}` — investigate unknowns
+- `/gsd-plan-phase {phase}` — skip discussion, plan directly
 - `/gsd-list-phase-assumptions {phase}` — see OpenCode's assumptions
 
 ---
@@ -202,25 +207,25 @@ Check if `{phase}-CONTEXT.md` exists in phase directory.
 
 ---
 
-**Route E: UAT issues need fix plans**
+**Route E: UAT gaps need fix plans**
 
-ISSUES.md exists without matching FIX.md. User needs to plan fixes.
+UAT.md exists with gaps (diagnosed issues). User needs to plan fixes.
 
 ```
 ---
 
-## ⚠ UAT Issues Found
+## ⚠ UAT Gaps Found
 
-**{plan}-ISSUES.md** has {N} issues without a fix plan.
+**{phase}-UAT.md** has {N} gaps requiring fixes.
 
-`/gsd-plan-fix {plan}`
+`/gsd-plan-phase {phase} --gaps`
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 
 **Also available:**
-- `/gsd-execute-plan [path]` — continue with other work first
+- `/gsd-execute-phase {phase}` — execute phase plans
 - `/gsd-verify-work {phase}` — run more UAT testing
 
 ---
@@ -230,7 +235,7 @@ ISSUES.md exists without matching FIX.md. User needs to plan fixes.
 
 **Step 3: Check milestone status (only when phase complete)**
 
-Read ROADMAP.md and identify:
+read ROADMAP.md and identify:
 1. Current phase number
 2. All phase numbers in the current milestone section
 
@@ -249,7 +254,7 @@ State: "Current phase is {X}. Milestone has {N} phases (highest: {Y})."
 
 **Route C: Phase complete, more phases remain**
 
-Read ROADMAP.md to get the next phase's name and goal.
+read ROADMAP.md to get the next phase's name and goal.
 
 ```
 ---
@@ -260,16 +265,15 @@ 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-discuss-phase {Z+1}` — gather context and clarify approach
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 
 **Also available:**
+- `/gsd-plan-phase {Z+1}` — skip discussion, plan directly
 - `/gsd-verify-work {Z}` — user acceptance test before continuing
-- `/gsd-discuss-phase {Z+1}` — gather context first
-- `/gsd-research-phase {Z+1}` — investigate unknowns
 
 ---
 ```
@@ -291,7 +295,7 @@ All {N} phases finished!
 
 `/gsd-complete-milestone`
 
-*`/clear` first → fresh context window*
+*`/new` first → fresh context window*
 
 ---
 
@@ -301,6 +305,32 @@ All {N} phases finished!
 ---
 ```
 
+---
+
+**Route F: Between milestones (ROADMAP.md missing, PROJECT.md exists)**
+
+A milestone was completed and archived. Ready to start the next milestone cycle.
+
+read MILESTONES.md to find the last completed milestone version.
+
+```
+---
+
+## ✓ Milestone v{X.Y} Complete
+
+Ready to plan the next milestone.
+
+## ▶ Next Up
+
+**Start Next Milestone** — questioning → research → requirements → roadmap
+
+`/gsd-new-milestone`
+
+*`/new` first → fresh context window*
+
+---
+```
+
 </step>
 
 <step name="edge_cases">
@@ -319,7 +349,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-phase if plans exist, /gsd-plan-phase if not
 - [ ] User confirms before any action
 - [ ] Seamless handoff to appropriate gsd command
       </success_criteria>

package/command/gsd/remove-phase.md

@@ -2,7 +2,7 @@
 name: gsd-remove-phase
 description: Remove a future phase from roadmap and renumber subsequent phases
 argument-hint: <phase-number>
-allowed-tools:
+tools:
   - read
   - write
   - bash
@@ -19,8 +19,6 @@ 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>
@@ -54,7 +52,7 @@ Parse current phase number from STATE.md "Current Position" section.
 </step>
 
 <step name="validate_phase_exists">
-Verify that target phase exists in ROADMAP.md:
+Verify the target phase exists in ROADMAP.md:
 
 1. Search for `### Phase {target}:` heading
 2. If not found:
@@ -68,7 +66,7 @@ Verify that target phase exists in ROADMAP.md:
 </step>
 
 <step name="validate_future_phase">
-Verify that the phase is a future phase (not started):
+Verify the phase is a future phase (not started):
 
 1. Compare target phase to current phase from STATE.md
 2. Target must be > current phase number
@@ -108,7 +106,7 @@ Exit.
 </step>
 
 <step name="gather_phase_info">
-Collect information about phase being removed:
+Collect information about the phase being removed:
 
 1. Extract phase name from ROADMAP.md heading: `### Phase {target}: {Name}`
 2. Find phase directory: `.planning/phases/{target}-{slug}/`
@@ -149,7 +147,7 @@ Wait for confirmation.
 </step>
 
 <step name="delete_phase_directory">
-Delete target phase directory if it exists:
+Delete the target phase directory if it exists:
 
 ```bash
 if [ -d ".planning/phases/{target}-{slug}" ]; then
@@ -181,7 +179,7 @@ Also rename decimal phase directories:
 <step name="rename_files_in_directories">
 Rename plan files inside renumbered directories:
 
-For each renumbered directory, rename files that contain phase number:
+For each renumbered directory, rename files that contain the phase number:
 
 ```bash
 # Inside 17-dashboard (was 18-dashboard):
@@ -197,14 +195,14 @@ Also handle CONTEXT.md and DISCOVERY.md (these don't have phase prefixes, so no
 <step name="update_roadmap">
 Update ROADMAP.md:
 
-1. **Remove phase section entirely:**
-   - Delete from `### Phase {target}:` to next phase heading (or section end)
+1. **Remove the phase section entirely:**
+   - Delete from `### Phase {target}:` to the next phase heading (or section end)
 
 2. **Remove from phase list:**
    - Delete line `- [ ] **Phase {target}: {Name}**` or similar
 
 3. **Remove from Progress table:**
-   - Delete row for Phase {target}
+   - Delete the row for Phase {target}
 
 4. **Renumber all subsequent phases:**
    - `### Phase 18:` → `### Phase 17:`
@@ -214,14 +212,14 @@ Update ROADMAP.md:
 
 5. **Update dependency references:**
    - `**Depends on:** Phase 18` → `**Depends on:** Phase 17`
-   - For phase that depended on removed phase:
+   - For the phase that depended on the removed phase:
      - `**Depends on:** Phase 17` (removed) → `**Depends on:** Phase 16`
 
 6. **Renumber decimal phases:**
    - `### Phase 17.1:` → `### Phase 16.1:` (if integer 17 removed)
    - Update all references consistently
 
-Write updated ROADMAP.md.
+write updated ROADMAP.md.
 </step>
 
 <step name="update_state">
@@ -233,16 +231,16 @@ Update STATE.md:
 2. **Recalculate progress percentage:**
    - New percentage based on completed plans / new total plans
 
-Do NOT add a "Roadmap Evolution" note - git commit is record.
+Do NOT add a "Roadmap Evolution" note - the git commit is the record.
 
-Write updated STATE.md.
+write updated STATE.md.
 </step>
 
 <step name="update_file_contents">
 Search for and update phase references inside plan files:
 
 ```bash
-# Find files that reference to old phase numbers
+# Find files that reference the old phase numbers
 grep -r "Phase 18" .planning/phases/17-*/ 2>/dev/null
 grep -r "Phase 19" .planning/phases/18-*/ 2>/dev/null
 # etc.
@@ -252,7 +250,7 @@ Update any internal references to reflect new numbering.
 </step>
 
 <step name="commit">
-Stage and commit removal:
+Stage and commit the removal:
 
 ```bash
 git add .planning/
@@ -297,7 +295,7 @@ Would you like to:
 - Don't remove completed phases (have SUMMARY.md files)
 - Don't remove current or past phases
 - Don't leave gaps in numbering - always renumber
-- Don't add "removed phase" notes to STATE.md - git commit is record
+- Don't add "removed phase" notes to STATE.md - git commit is the record
 - Don't ask about each decimal phase - just renumber them
 - Don't modify completed phase directories
 </anti_patterns>
@@ -310,7 +308,7 @@ Would you like to:
 - Simpler operation
 
 **No subsequent phases to renumber:**
-- Removing last phase (e.g., Phase 20 when that's the end)
+- Removing the last phase (e.g., Phase 20 when that's the end)
 - Just delete and update ROADMAP.md, no renumbering needed
 
 **Phase directory doesn't exist:**

package/command/gsd/research-phase.md

@@ -1,91 +1,179 @@
 ---
 name: gsd-research-phase
-description: Research how to implement a phase before planning
+description: Research how to implement a phase (standalone - usually use /gsd-plan-phase instead)
 argument-hint: "[phase]"
-allowed-tools:
+tools:
   - read
   - bash
-  - glob
-  - grep
-  - write
-  - webfetch
-  - websearch
-  - mcp__context7__*
 ---
 
 <objective>
-Comprehensive research on HOW to implement a phase before planning.
+Research how to implement a phase. Spawns gsd-phase-researcher agent with phase context.
 
-This is for niche/complex domains where OpenCode's training data is sparse or outdated. Research discovers:
-- What libraries exist for this problem
-- What architecture patterns experts use
-- What standard stack looks like
-- What problems people commonly hit
-- What NOT to hand-roll (use existing solutions)
+**Note:** This is a standalone research command. For most workflows, use `/gsd-plan-phase` which integrates research automatically.
 
-Output: RESEARCH.md with ecosystem knowledge that informs quality planning.
-</objective>
+**Use this command when:**
+- You want to research without planning yet
+- You want to re-research after planning is complete
+- You need to investigate before deciding if a phase is feasible
+
+**Orchestrator role:** Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.
 
-<execution_context>
-@~/.config/opencode/get-shit-done/workflows/research-phase.md
-@~/.config/opencode/get-shit-done/templates/research.md
-@~/.config/opencode/get-shit-done/references/research-pitfalls.md
-</execution_context>
+**Why subagent:** Research burns context fast (webfetch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.
+</objective>
 
 <context>
 Phase number: $ARGUMENTS (required)
 
-**Load project state:**
-@.planning/STATE.md
+Normalize phase input in step 1 before any directory lookups.
+</context>
+
+<process>
+
+## 1. Normalize and Validate Phase
+
+```bash
+# Normalize phase number (8 → 08, but preserve decimals like 2.1 → 02.1)
+if [[ "$ARGUMENTS" =~ ^[0-9]+$ ]]; then
+  PHASE=$(printf "%02d" "$ARGUMENTS")
+elif [[ "$ARGUMENTS" =~ ^([0-9]+)\.([0-9]+)$ ]]; then
+  PHASE=$(printf "%02d.%s" "${BASH_REMATCH[1]}" "${BASH_REMATCH[2]}")
+else
+  PHASE="$ARGUMENTS"
+fi
+
+grep -A5 "Phase ${PHASE}:" .planning/ROADMAP.md 2>/dev/null
+```
+
+**If not found:** Error and exit. **If found:** Extract phase number, name, description.
+
+## 2. Check Existing Research
+
+```bash
+ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
+```
+
+**If exists:** Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.
+
+**If doesn't exist:** Continue.
+
+## 3. Gather Phase Context
+
+```bash
+grep -A20 "Phase ${PHASE}:" .planning/ROADMAP.md
+cat .planning/REQUIREMENTS.md 2>/dev/null
+cat .planning/phases/${PHASE}-*/${PHASE}-CONTEXT.md 2>/dev/null
+grep -A30 "### Decisions Made" .planning/STATE.md 2>/dev/null
+```
+
+Present summary with phase description, requirements, prior decisions.
+
+## 4. Spawn gsd-researcher Agent
+
+Research modes: ecosystem (default), feasibility, implementation, comparison.
+
+```markdown
+<research_type>
+Phase Research — investigating HOW to implement a specific phase well.
+</research_type>
+
+<key_insight>
+The question is NOT "which library should I use?"
+
+The question is: "What do I not know that I don't know?"
 
-**Load roadmap:**
-@.planning/ROADMAP.md
+For this phase, discover:
+- What's the established architecture pattern?
+- What libraries form the standard stack?
+- What problems do people commonly hit?
+- What's SOTA vs what OpenCode's training thinks is SOTA?
+- What should NOT be hand-rolled?
+</key_insight>
 
-**Load phase context if exists:**
-Check for `.planning/phases/XX-name/{phase}-CONTEXT.md` - bonus context from discuss-phase.
+<objective>
+Research implementation approach for Phase {phase_number}: {phase_name}
+Mode: ecosystem
+</objective>
+
+<context>
+**Phase description:** {phase_description}
+**Requirements:** {requirements_list}
+**Prior decisions:** {decisions_if_any}
+**Phase context:** {context_md_content}
 </context>
 
-<process>
-1. Validate phase number argument (error if missing or invalid)
-2. Check if phase exists in roadmap - extract phase description
-3. Check if RESEARCH.md already exists (offer to update or use existing)
-4. Load CONTEXT.md if it exists (bonus context for research direction)
-5. Follow research-phase.md workflow:
-   - Analyze phase to identify knowledge gaps
-   - Determine research domains (architecture, ecosystem, patterns, pitfalls)
-   - Execute comprehensive research via Context7, official docs, WebSearch
-   - Cross-verify all findings
-   - Create RESEARCH.md with actionable ecosystem knowledge
-6. Offer next steps (plan phase)
-</process>
+<downstream_consumer>
+Your RESEARCH.md will be loaded by `/gsd-plan-phase` which uses specific sections:
+- `## Standard Stack` → Plans use these libraries
+- `## Architecture Patterns` → Task structure follows these
+- `## Don't Hand-Roll` → Tasks NEVER build custom solutions for listed problems
+- `## Common Pitfalls` → Verification steps check for these
+- `## Code Examples` → Task actions reference these patterns
+
+Be prescriptive, not exploratory. "Use X" not "Consider X or Y."
+</downstream_consumer>
+
+<quality_gate>
+Before declaring complete, verify:
+- [ ] All domains investigated (not just some)
+- [ ] Negative claims verified with official docs
+- [ ] Multiple sources for critical claims
+- [ ] Confidence levels assigned honestly
+- [ ] Section names match what plan-phase expects
+</quality_gate>
+
+<output>
+write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
+</output>
+```
+
+```
+Task(
+  prompt=filled_prompt,
+  subagent_type="gsd-phase-researcher",
+  description="Research Phase {phase}"
+)
+```
+
+## 5. Handle Agent Return
 
-<when_to_use>
-**Use research-phase for:**
-- 3D graphics (Three.js, WebGL, procedural generation)
-- Game development (physics, collision, AI, procedural content)
-- Audio/music (Web Audio API, DSP, synthesis)
-- Shaders (GLSL, Metal, ISF)
-- ML/AI integration (model serving, inference, pipelines)
-- Real-time systems (WebSockets, WebRTC, sync)
-- Specialized frameworks with active ecosystems
-- Any domain where "how do experts do this" matters
-
-**Skip research-phase for:**
-- Standard web dev (auth, CRUD, REST APIs)
-- Well-known patterns (forms, validation, testing)
-- Simple integrations (Stripe, SendGrid with clear docs)
-- Commodity features OpenCode handles well
-</when_to_use>
+**`## RESEARCH COMPLETE`:** Display summary, offer: Plan phase, Dig deeper, Review full, Done.
+
+**`## CHECKPOINT REACHED`:** Present to user, get response, spawn continuation.
+
+**`## RESEARCH INCONCLUSIVE`:** Show what was attempted, offer: Add context, Try different mode, Manual.
+
+## 6. Spawn Continuation Agent
+
+```markdown
+<objective>
+Continue research for Phase {phase_number}: {phase_name}
+</objective>
+
+<prior_state>
+Research file: @.planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
+</prior_state>
+
+<checkpoint_response>
+**Type:** {checkpoint_type}
+**Response:** {user_response}
+</checkpoint_response>
+```
+
+```
+Task(
+  prompt=continuation_prompt,
+  subagent_type="gsd-phase-researcher",
+  description="Continue research Phase {phase}"
+)
+```
+
+</process>
 
 <success_criteria>
 - [ ] Phase validated against roadmap
-- [ ] Domain/ecosystem identified from phase description
-- [ ] Comprehensive research executed (Context7 + official docs + WebSearch)
-- [ ] All WebSearch findings cross-verified with authoritative sources
-- [ ] RESEARCH.md created with ecosystem knowledge
-- [ ] Standard stack/libraries identified
-- [ ] Architecture patterns documented
-- [ ] Common pitfalls catalogued
-- [ ] What NOT to hand-roll is clear
-- [ ] User knows next steps (plan phase)
+- [ ] Existing research checked
+- [ ] gsd-phase-researcher spawned with context
+- [ ] Checkpoints handled correctly
+- [ ] User knows next steps
 </success_criteria>

package/command/gsd/resume-work.md

@@ -1,7 +1,7 @@
 ---
 name: gsd-resume-work
 description: Resume work from previous session with full context restoration
-allowed-tools:
+tools:
   - read
   - bash
   - write
@@ -11,7 +11,7 @@ allowed-tools:
 <objective>
 Restore complete project context and resume work seamlessly from previous session.
 
-Routes to resume-project workflow which handles:
+Routes to the resume-project workflow which handles:
 
 - STATE.md loading (or reconstruction if missing)
 - Checkpoint detection (.continue-here files)
@@ -25,7 +25,7 @@ Routes to resume-project workflow which handles:
 </execution_context>
 
 <process>
-**Follow resume-project workflow** from `@~/.config/opencode/get-shit-done/workflows/resume-project.md`.
+**Follow the resume-project workflow** from `@~/.config/opencode/get-shit-done/workflows/resume-project.md`.
 
 The workflow handles all resumption logic including: