gsd-opencode 1.20.4 → 1.22.1

package/agents/gsd-roadmapper.md

@@ -1,6 +1,7 @@
 ---
 name: gsd-roadmapper
 description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
+mode: subagent
 tools:
   read: true
   write: true
@@ -8,6 +9,14 @@ tools:
   glob: true
   grep: true
 color: "#800080"
+skills:
+  - gsd-roadmapper-workflow
+# hooks:
+#   PostToolUse:
+#     - matcher: "write|edit"
+#       hooks:
+#         - type: command
+#           command: "npx eslint --fix $FILE 2>/dev/null || true"
 ---
 
 <role>
@@ -197,17 +206,17 @@ Track coverage as you go.
 - New milestone: Start at 1
 - Continuing milestone: Check existing phases, start at last + 1
 
-## Depth Calibration
+## Granularity Calibration
 
-read depth from config.json. Depth controls compression tolerance.
+read granularity from config.json. Granularity controls compression tolerance.
 
-| Depth | Typical Phases | What It Means |
-|-------|----------------|---------------|
-| Quick | 3-5 | Combine aggressively, critical path only |
+| Granularity | Typical Phases | What It Means |
+|-------------|----------------|---------------|
+| Coarse | 3-5 | Combine aggressively, critical path only |
 | Standard | 5-8 | Balanced grouping |
-| Comprehensive | 8-12 | Let natural boundaries stand |
+| Fine | 8-12 | Let natural boundaries stand |
 
-**Key:** Derive phases from work, then apply depth as compression guidance. Don't pad small projects or compress complex ones.
+**Key:** Derive phases from work, then apply granularity as compression guidance. Don't pad small projects or compress complex ones.
 
 ## Good Phase Patterns
 
@@ -333,11 +342,11 @@ After roadmap creation, REQUIREMENTS.md gets updated with phase mappings:
 | 2. Name | 0/2 | Not started | - |
 ```
 
-Reference full template: `~/.config/opencode/get-shit-done/templates/roadmap.md`
+Reference full template: `$HOME/.config/opencode/get-shit-done/templates/roadmap.md`
 
 ## STATE.md Structure
 
-Use template from `~/.config/opencode/get-shit-done/templates/state.md`.
+Use template from `$HOME/.config/opencode/get-shit-done/templates/state.md`.
 
 Key sections:
 - Project Reference (core value, current focus)
@@ -354,7 +363,7 @@ When presenting to user for approval:
 ## ROADMAP DRAFT
 
 **Phases:** [N]
-**Depth:** [from config]
+**Granularity:** [from config]
 **Coverage:** [X]/[Y] requirements mapped
 
 ### Phase Structure
@@ -398,7 +407,7 @@ Orchestrator provides:
 - PROJECT.md content (core value, constraints)
 - REQUIREMENTS.md content (v1 requirements with REQ-IDs)
 - research/SUMMARY.md content (if exists - phase suggestions)
-- config.json (depth setting)
+- config.json (granularity setting)
 
 Parse and confirm understanding before proceeding.
 
@@ -434,7 +443,7 @@ Apply phase identification methodology:
 1. Group requirements by natural delivery boundaries
 2. Identify dependencies between groups
 3. Create phases that complete coherent capabilities
-4. Check depth setting for compression guidance
+4. Check granularity setting for compression guidance
 
 ## Step 5: Derive Success Criteria
 
@@ -454,7 +463,9 @@ If gaps found, include in draft for user decision.
 
 ## Step 7: write Files Immediately
 
-**write files first, then return.** This ensures artifacts persist even if context is lost.
+**ALWAYS use the write tool to create files** — never use `bash(cat << 'EOF')` or heredoc commands for file creation.
+
+write files first, then return. This ensures artifacts persist even if context is lost.
 
 1. **write ROADMAP.md** using output format
 
@@ -497,7 +508,7 @@ When files are written and returning to orchestrator:
 ### Summary
 
 **Phases:** {N}
-**Depth:** {from config}
+**Granularity:** {from config}
 **Coverage:** {X}/{X} requirements mapped ✓
 
 | Phase | Goal | Requirements |
@@ -623,7 +634,7 @@ Roadmap is complete when:
 - [ ] All v1 requirements extracted with IDs
 - [ ] Research context loaded (if exists)
 - [ ] Phases derived from requirements (not imposed)
-- [ ] Depth calibration applied
+- [ ] Granularity calibration applied
 - [ ] Dependencies between phases identified
 - [ ] Success criteria derived for each phase (2-5 observable behaviors)
 - [ ] Success criteria cross-checked against requirements (gaps resolved)

package/agents/gsd-verifier.md

@@ -1,6 +1,7 @@
 ---
 name: gsd-verifier
 description: Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.
+mode: subagent
 tools:
   read: true
   write: true
@@ -8,6 +9,14 @@ tools:
   grep: true
   glob: true
 color: "#008000"
+skills:
+  - gsd-verifier-workflow
+# hooks:
+#   PostToolUse:
+#     - matcher: "write|edit"
+#       hooks:
+#         - type: command
+#           command: "npx eslint --fix $FILE 2>/dev/null || true"
 ---
 
 <role>
@@ -21,6 +30,21 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `read` tool t
 **Critical mindset:** Do NOT trust SUMMARY.md claims. SUMMARYs document what OpenCode SAID it did. You verify what ACTUALLY exists in the code. These often differ.
 </role>
 
+<project_context>
+Before verifying, discover project context:
+
+**Project instructions:** read `./AGENTS.md` if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
+
+**Project skills:** Check `.OpenCode/skills/` or `.agents/skills/` directory if either exists:
+1. List available skills (subdirectories)
+2. read `SKILL.md` for each skill (lightweight index ~130 lines)
+3. Load specific `rules/*.md` files as needed during verification
+4. Do NOT load full `AGENTS.md` files (100KB+ context cost)
+5. Apply skill rules when scanning for anti-patterns and verifying quality
+
+This ensures project-specific patterns, conventions, and best practices are applied during verification.
+</project_context>
+
 <core_principle>
 **task completion ≠ Goal achievement**
 
@@ -62,7 +86,7 @@ Set `is_re_verification = false`, proceed with Step 1.
 ```bash
 ls "$PHASE_DIR"/*-PLAN.md 2>/dev/null
 ls "$PHASE_DIR"/*-SUMMARY.md 2>/dev/null
-node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs roadmap get-phase "$PHASE_NUM"
+node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" roadmap get-phase "$PHASE_NUM"
 grep -E "^| $PHASE_NUM" .planning/REQUIREMENTS.md 2>/dev/null
 ```
 
@@ -99,7 +123,7 @@ must_haves:
 If no must_haves in frontmatter, check for Success Criteria:
 
 ```bash
-PHASE_DATA=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs roadmap get-phase "$PHASE_NUM" --raw)
+PHASE_DATA=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" roadmap get-phase "$PHASE_NUM" --raw)
 ```
 
 Parse the `success_criteria` array from the JSON output. If non-empty:
@@ -142,7 +166,7 @@ For each truth:
 Use gsd-tools for artifact verification against must_haves in PLAN frontmatter:
 
 ```bash
-ARTIFACT_RESULT=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs verify artifacts "$PLAN_PATH")
+ARTIFACT_RESULT=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" verify artifacts "$PLAN_PATH")
 ```
 
 Parse JSON result: `{ all_passed, passed, total, artifacts: [{path, exists, issues, passed}] }`
@@ -191,7 +215,7 @@ Key links are critical connections. If broken, the goal fails even with all arti
 Use gsd-tools for key link verification against must_haves in PLAN frontmatter:
 
 ```bash
-LINKS_RESULT=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs verify key-links "$PLAN_PATH")
+LINKS_RESULT=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" verify key-links "$PLAN_PATH")
 ```
 
 Parse JSON result: `{ all_verified, verified, total, links: [{from, to, via, verified, detail}] }`
@@ -273,12 +297,12 @@ Identify files modified in this phase from SUMMARY.md key-files section, or extr
 
 ```bash
 # Option 1: Extract from SUMMARY frontmatter
-SUMMARY_FILES=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs summary-extract "$PHASE_DIR"/*-SUMMARY.md --fields key-files)
+SUMMARY_FILES=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" summary-extract "$PHASE_DIR"/*-SUMMARY.md --fields key-files)
 
 # Option 2: Verify commits exist (if commit hashes documented)
 COMMIT_HASHES=$(grep -oE "[a-f0-9]{7,40}" "$PHASE_DIR"/*-SUMMARY.md | head -10)
 if [ -n "$COMMIT_HASHES" ]; then
-  COMMITS_VALID=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs verify commits $COMMIT_HASHES)
+  COMMITS_VALID=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" verify commits $COMMIT_HASHES)
 fi
 
 # Fallback: grep for files

package/bin/dm/lib/constants.js

@@ -58,7 +58,12 @@ export const PATH_PATTERNS = {
    * These appear in workflow files that call gsd-tools.cjs directly.
    * Must be replaced for both global and local installs to ensure correct paths.
    */
-  tildeConfigReference: /~\/\.config\/opencode\//g
+  tildeConfigReference: /~\/\.config\/opencode\//g,
+  /**
+   * Pattern to match literal $HOME/.config/opencode/ references in markdown files.
+   * These are shell-style absolute references that need to be replaced for local installs.
+   */
+  homeConfigReference: /\$HOME\/\.config\/opencode\//g
 };
 
 /**

package/bin/dm/src/services/file-ops.js

@@ -485,8 +485,12 @@ export class FileOperations {
       if (PATH_PATTERNS.tildeConfigReference) {
         PATH_PATTERNS.tildeConfigReference.lastIndex = 0; // Reset regex
       }
+      const hasHomeRef = PATH_PATTERNS.homeConfigReference && PATH_PATTERNS.homeConfigReference.test(content);
+      if (PATH_PATTERNS.homeConfigReference) {
+        PATH_PATTERNS.homeConfigReference.lastIndex = 0; // Reset regex
+      }
 
-      if (!hasGsdRef && !hasAbsRef && !hasTildeRef) {
+      if (!hasGsdRef && !hasAbsRef && !hasTildeRef && !hasHomeRef) {
         await fs.copyFile(sourcePath, targetPath, fsConstants.COPYFILE_FICLONE);
         return;
       }
@@ -520,6 +524,15 @@ export class FileOperations {
         );
       }
 
+      // For local installs, replace literal $HOME/.config/opencode/ with local path
+      // This handles shell-style references like: node $HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs
+      if (this.scopeManager.scope === 'local' && PATH_PATTERNS.homeConfigReference) {
+        content = content.replace(
+          PATH_PATTERNS.homeConfigReference,
+          () => targetDir + '/'
+        );
+      }
+
       await fs.writeFile(targetPath, content, 'utf-8');
     } else {
       // Copy binary or other files directly

package/commands/gsd/gsd-add-phase.md

@@ -2,10 +2,10 @@
 name: gsd-add-phase
 description: Add phase to end of current milestone in roadmap
 argument-hint: <description>
-allowed-tools:
-  - read
-  - write
-  - bash
+permissions:
+   read: true
+   write: true
+   bash: true
 ---
 
 <objective>
@@ -19,7 +19,7 @@ Routes to the add-phase workflow which handles:
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/add-phase.md
+@$HOME/.config/opencode/get-shit-done/workflows/add-phase.md
 </execution_context>
 
 <context>
@@ -29,7 +29,7 @@ Roadmap and state are resolved in-workflow via `init phase-op` and targeted tool
 </context>
 
 <process>
-**Follow the add-phase workflow** from `@~/.config/opencode/get-shit-done/workflows/add-phase.md`.
+**Follow the add-phase workflow** from `@$HOME/.config/opencode/get-shit-done/workflows/add-phase.md`.
 
 The workflow handles all logic including:
 1. Argument parsing and validation

package/commands/gsd/gsd-add-tests.md

@@ -0,0 +1,41 @@
+---
+name: gsd-add-tests
+description: Generate tests for a completed phase based on UAT criteria and implementation
+argument-hint: "<phase> [additional instructions]"
+permissions:
+   read: true
+   write: true
+   edit: true
+   bash: true
+   glob: true
+   grep: true
+   task: true
+   question: true
+argument-instructions: |
+  Parse the argument as a phase number (integer, decimal, or letter-suffix), plus optional free-text instructions.
+  Example: /gsd-add-tests 12
+  Example: /gsd-add-tests 12 focus on edge cases in the pricing module
+---
+<objective>
+Generate unit and E2E tests for a completed phase, using its SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications.
+
+Analyzes implementation files, classifies them into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
+
+Output: Test files committed with message `test(phase-{N}): add unit and E2E tests from add-tests command`
+</objective>
+
+<execution_context>
+@$HOME/.config/opencode/get-shit-done/workflows/add-tests.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS
+
+@.planning/STATE.md
+@.planning/ROADMAP.md
+</context>
+
+<process>
+Execute the add-tests workflow from @$HOME/.config/opencode/get-shit-done/workflows/add-tests.md end-to-end.
+Preserve all workflow gates (classification approval, test plan approval, RED-GREEN verification, gap reporting).
+</process>

package/commands/gsd/gsd-add-todo.md

@@ -2,11 +2,11 @@
 name: gsd-add-todo
 description: Capture idea or task as todo from current conversation context
 argument-hint: [optional description]
-allowed-tools:
-  - read
-  - write
-  - bash
-  - question
+permissions:
+   read: true
+   write: true
+   bash: true
+   question: true
 ---
 
 <objective>
@@ -23,7 +23,7 @@ Routes to the add-todo workflow which handles:
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/add-todo.md
+@$HOME/.config/opencode/get-shit-done/workflows/add-todo.md
 </execution_context>
 
 <context>
@@ -33,7 +33,7 @@ State is resolved in-workflow via `init todos` and targeted reads.
 </context>
 
 <process>
-**Follow the add-todo workflow** from `@~/.config/opencode/get-shit-done/workflows/add-todo.md`.
+**Follow the add-todo workflow** from `@$HOME/.config/opencode/get-shit-done/workflows/add-todo.md`.
 
 The workflow handles all logic including:
 1. Directory ensuring

package/commands/gsd/gsd-audit-milestone.md

@@ -2,13 +2,13 @@
 name: gsd-audit-milestone
 description: Audit milestone completion against original intent before archiving
 argument-hint: "[version]"
-allowed-tools:
-  - read
-  - glob
-  - grep
-  - bash
-  - task
-  - write
+permissions:
+   read: true
+   glob: true
+   grep: true
+   bash: true
+   task: true
+   write: true
 ---
 <objective>
 Verify milestone achieved its definition of done. Check requirements coverage, cross-phase integration, and end-to-end flows.
@@ -17,7 +17,7 @@ Verify milestone achieved its definition of done. Check requirements coverage, c
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/audit-milestone.md
+@$HOME/.config/opencode/get-shit-done/workflows/audit-milestone.md
 </execution_context>
 
 <context>
@@ -31,6 +31,6 @@ glob: .planning/phases/*/*-VERIFICATION.md
 </context>
 
 <process>
-Execute the audit-milestone workflow from @~/.config/opencode/get-shit-done/workflows/audit-milestone.md end-to-end.
+Execute the audit-milestone workflow from @$HOME/.config/opencode/get-shit-done/workflows/audit-milestone.md end-to-end.
 Preserve all workflow gates (scope determination, verification reading, integration check, requirements coverage, routing).
 </process>

package/commands/gsd/gsd-check-profile.md

@@ -1,9 +1,9 @@
 ---
 name: gsd-check-profile
 description: Validate gsd-opencode profile configuration
-allowed-tools:
-  - read
-  - bash
+permissions:
+  read: true
+  bash: true
 ---
 <objective>
 Validate gsd-opencode profile configuration across both `opencode.json` and `.planning/oc_config.json`, then report results.

package/commands/gsd/gsd-check-todos.md

@@ -2,11 +2,11 @@
 name: gsd-check-todos
 description: List pending todos and select one to work on
 argument-hint: [area filter]
-allowed-tools:
-  - read
-  - write
-  - bash
-  - question
+permissions:
+   read: true
+   write: true
+   bash: true
+   question: true
 ---
 
 <objective>
@@ -21,7 +21,7 @@ Routes to the check-todos workflow which handles:
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/check-todos.md
+@$HOME/.config/opencode/get-shit-done/workflows/check-todos.md
 </execution_context>
 
 <context>
@@ -31,7 +31,7 @@ Todo state and roadmap correlation are loaded in-workflow using `init todos` and
 </context>
 
 <process>
-**Follow the check-todos workflow** from `@~/.config/opencode/get-shit-done/workflows/check-todos.md`.
+**Follow the check-todos workflow** from `@$HOME/.config/opencode/get-shit-done/workflows/check-todos.md`.
 
 The workflow handles all logic including:
 1. Todo existence checking

package/commands/gsd/gsd-cleanup.md

@@ -9,10 +9,10 @@ Use when `.planning/phases/` has accumulated directories from past milestones.
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/cleanup.md
+@$HOME/.config/opencode/get-shit-done/workflows/cleanup.md
 </execution_context>
 
 <process>
-Follow the cleanup workflow at @~/.config/opencode/get-shit-done/workflows/cleanup.md.
+Follow the cleanup workflow at @$HOME/.config/opencode/get-shit-done/workflows/cleanup.md.
 Identify completed milestones, show a dry-run summary, and archive on confirmation.
 </process>

package/commands/gsd/gsd-complete-milestone.md

@@ -3,10 +3,10 @@ type: prompt
 name: gsd-complete-milestone
 description: Archive completed milestone and prepare for next version
 argument-hint: <version>
-allowed-tools:
-  - read
-  - write
-  - bash
+permissions:
+   read: true
+   write: true
+   bash: true
 ---
 
 <objective>
@@ -19,8 +19,8 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 <execution_context>
 **Load these files NOW (before proceeding):**
 
-- @~/.config/opencode/get-shit-done/workflows/complete-milestone.md (main workflow)
-- @~/.config/opencode/get-shit-done/templates/milestone-archive.md (archive template)
+- @$HOME/.config/opencode/get-shit-done/workflows/complete-milestone.md (main workflow)
+- @$HOME/.config/opencode/get-shit-done/templates/milestone-archive.md (archive template)
   </execution_context>
 
 <context>

package/commands/gsd/gsd-debug.md

@@ -2,11 +2,11 @@
 name: gsd-debug
 description: Systematic debugging with persistent state across context resets
 argument-hint: [issue description]
-allowed-tools:
-  - read
-  - bash
-  - task
-  - question
+permissions:
+   read: true
+   bash: true
+   task: true
+   question: true
 ---
 
 <objective>
@@ -31,12 +31,13 @@ ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5
 ## 0. Initialize Context
 
 ```bash
-INIT=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs state load)
+INIT=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" state load)
+if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
 ```
 
 Extract `commit_docs` from init JSON. Resolve debugger model:
 ```bash
-DEBUGGER_MODEL=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs resolve-model gsd-debugger --raw)
+debugger_model=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" resolve-model gsd-debugger --raw)
 ```
 
 ## 1. Check Active Sessions
@@ -110,6 +111,9 @@ task(
 **If `## CHECKPOINT REACHED`:**
 - Present checkpoint details to user
 - Get user response
+- If checkpoint type is `human-verify`:
+  - If user confirms fixed: continue so agent can finalize/resolve/archive
+  - If user reports issues: continue so agent returns to investigation/fixing
 - Spawn continuation agent (see step 5)
 
 **If `## INVESTIGATION INCONCLUSIVE`:**

package/commands/gsd/gsd-discuss-phase.md

@@ -2,31 +2,35 @@
 name: gsd-discuss-phase
 description: Gather phase context through adaptive questioning before planning
 argument-hint: "<phase> [--auto]"
-allowed-tools:
-  - read
-  - write
-  - bash
-  - glob
-  - grep
-  - question
-  - task
+permissions:
+   read: true
+   write: true
+   bash: true
+   glob: true
+   grep: true
+   question: true
+   task: true
+   mcp__context7__resolve-library-id: true
+   mcp__context7__query-docs: true
 ---
 
 <objective>
 Extract implementation decisions that downstream agents need — researcher and planner will use CONTEXT.md to know what to investigate and what choices are locked.
 
 **How it works:**
-1. Analyze the phase to identify gray areas (UI, UX, behavior, etc.)
-2. Present gray areas — user selects which to discuss
-3. Deep-dive each selected area until satisfied
-4. Create CONTEXT.md with decisions that guide research and planning
+1. Load prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files)
+2. Scout codebase for reusable assets and patterns
+3. Analyze phase — skip gray areas already decided in prior phases
+4. Present remaining gray areas — user selects which to discuss
+5. Deep-dive each selected area until satisfied
+6. Create CONTEXT.md with decisions that guide research and planning
 
 **Output:** `{phase_num}-CONTEXT.md` — decisions clear enough that downstream agents can act without asking the user again
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/discuss-phase.md
-@~/.config/opencode/get-shit-done/templates/context.md
+@$HOME/.config/opencode/get-shit-done/workflows/discuss-phase.md
+@$HOME/.config/opencode/get-shit-done/templates/context.md
 </execution_context>
 
 <context>
@@ -38,11 +42,13 @@ Context files are resolved in-workflow using `init phase-op` and roadmap/state t
 <process>
 1. Validate phase number (error if missing or not in roadmap)
 2. Check if CONTEXT.md exists (offer update/view/skip if yes)
-3. **Analyze phase** — Identify domain and generate phase-specific gray areas
-4. **Present gray areas** — Multi-select: which to discuss? (NO skip option)
-5. **Deep-dive each area** — 4 questions per area, then offer more/next
-6. **write CONTEXT.md** — Sections match areas discussed
-7. Offer next steps (research or plan)
+3. **Load prior context** — read PROJECT.md, REQUIREMENTS.md, STATE.md, and all prior CONTEXT.md files
+4. **Scout codebase** — Find reusable assets, patterns, and integration points
+5. **Analyze phase** — Check prior decisions, skip already-decided areas, generate remaining gray areas
+6. **Present gray areas** — Multi-select: which to discuss? Annotate with prior decisions + code context
+7. **Deep-dive each area** — 4 questions per area, code-informed options, Context7 for library choices
+8. **write CONTEXT.md** — Sections match areas discussed + code_context section
+9. Offer next steps (research or plan)
 
 **CRITICAL: Scope guardrail**
 - Phase boundary from ROADMAP.md is FIXED
@@ -74,6 +80,7 @@ Generate 3-4 **phase-specific** gray areas, not generic categories.
 </process>
 
 <success_criteria>
+- Prior context loaded and applied (no re-asking decided questions)
 - Gray areas identified through intelligent analysis
 - User chose which areas to discuss
 - Each selected area explored until satisfied

package/commands/gsd/gsd-execute-phase.md

@@ -2,16 +2,16 @@
 name: gsd-execute-phase
 description: Execute all plans in a phase with wave-based parallelization
 argument-hint: "<phase-number> [--gaps-only]"
-allowed-tools:
-  - read
-  - write
-  - edit
-  - glob
-  - grep
-  - bash
-  - task
-  - todowrite
-  - question
+permissions:
+   read: true
+   write: true
+   edit: true
+   glob: true
+   grep: true
+   bash: true
+   task: true
+   todowrite: true
+   question: true
 ---
 <objective>
 Execute all plans in a phase using wave-based parallel execution.
@@ -22,8 +22,8 @@ Context budget: ~15% orchestrator, 100% fresh per subagent.
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/execute-phase.md
-@~/.config/opencode/get-shit-done/references/ui-brand.md
+@$HOME/.config/opencode/get-shit-done/workflows/execute-phase.md
+@$HOME/.config/opencode/get-shit-done/references/ui-brand.md
 </execution_context>
 
 <context>
@@ -36,6 +36,6 @@ Context files are resolved inside the workflow via `gsd-tools init execute-phase
 </context>
 
 <process>
-Execute the execute-phase workflow from @~/.config/opencode/get-shit-done/workflows/execute-phase.md end-to-end.
+Execute the execute-phase workflow from @$HOME/.config/opencode/get-shit-done/workflows/execute-phase.md end-to-end.
 Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).
 </process>