gsd-opencode 1.10.2 → 1.20.1

package/commands/gsd/set-model.md

@@ -1,77 +0,0 @@
----
-name: gsd-set-model
-description: Configure models for a specific profile's stages (planning/execution/verification)
-arguments:
-  - name: profile
-    description: "Profile name: quality, balanced, or budget (optional - will prompt if not provided)"
-    required: false
-agent: gsd-set-model
-tools:
-  - read
-  - write
-  - bash
-  - question
----
-
-<objective>
-Configure the models assigned to each stage (planning, execution, verification) for a specific profile.
-
-Unlike `/gsd-set-profile` which switches between profiles, this command lets you define *what models* a profile uses. Implementation lives in the `gsd-set-model` agent.
-</objective>
-
-<process>
-
-Run the model configuration flow using the `gsd-set-model` agent.
-
-</process>
-
-<examples>
-
-**Configure the balanced profile:**
-
-```text
-/gsd-set-model balanced
-
-Configuring models for: balanced
-
-Select model for Planning stage:
-> anthropic/claude-sonnet-4-20250514
-
-Select model for Execution stage:
-> anthropic/claude-sonnet-4-20250514
-
-Select model for Verification stage:
-> openai/gpt-4o-mini
-
-✓ Updated balanced profile:
-| Stage | Model |
-|-------|-------|
-| planning | anthropic/claude-sonnet-4-20250514 |
-| execution | anthropic/claude-sonnet-4-20250514 |
-| verification | openai/gpt-4o-mini |
-```
-
-**Interactive mode (no argument):**
-
-```text
-/gsd-set-model
-
-Which profile do you want to configure?
-> Balanced
-
-Configuring models for: balanced
-...
-```
-
-</examples>
-
-<success_criteria>
-
-- [ ] `.planning/config.json` exists (or clear error shown)
-- [ ] User selects a profile (or provides via argument)
-- [ ] User selects models for all three stages from available models
-- [ ] Profile preset is updated in `.planning/config.json`
-- [ ] `opencode.json` is regenerated if the modified profile is active
-- [ ] Clear confirmation shown with updated model assignments
-
-</success_criteria>

package/commands/gsd/set-profile.md

@@ -1,46 +0,0 @@
----
-name: gsd-set-profile
-description: Switch model profile for GSD agents (quality/balanced/budget)
-arguments:
-  - name: profile
-    description: "Profile name: quality, balanced, or budget"
-    required: true
-agent: gsd-set-profile
-tools:
-  - read
-  - write
-  - bash
-  - question
----
-
-<objective>
-Switch the project’s active model profile (quality/balanced/budget).
-
-Implementation lives in the `gsd-set-profile` agent so we don’t duplicate the full switching/migration logic in multiple places.
-</objective>
-
-<process>
-
-Run the profile switch using the `gsd-set-profile` agent.
-
-</process>
-
-<examples>
-
-**Switch to budget profile:**
-
-```text
-/gsd-set-profile budget
-
-✓ Active profile set to: budget
-```
-
-**Switch to quality profile:**
-
-```text
-/gsd-set-profile quality
-
-✓ Active profile set to: quality
-```
-
-</examples>

package/commands/gsd/settings.md

@@ -1,33 +0,0 @@
----
-name: gsd-settings
-description: Configure GSD model profiles and workflow settings
-agent: gsd-settings
-tools:
-  - read
-  - write
-  - bash
-  - question
----
-
-<objective>
-Open an interactive settings menu.
-
-This delegates the implementation to the `gsd-settings` agent, which manages `.planning/config.json` and regenerates `opencode.json` when needed.
-</objective>
-
-<process>
-
-Run the interactive settings flow using the `gsd-settings` agent.
-
-</process>
-
-<success_criteria>
-
-- [ ] `.planning/` is validated as an existing GSD project (or a clear error is shown)
-- [ ] Current settings are displayed (active profile, effective models, workflow toggles)
-- [ ] User can update profile and workflow toggles via interactive UI
-- [ ] Updates are persisted to `.planning/config.json`
-- [ ] `opencode.json` is regenerated/updated to reflect effective models
-- [ ] A clear confirmation is shown ("GSD ► SETTINGS UPDATED")
-
-</success_criteria>

package/commands/gsd/verify-work.md

@@ -1,219 +0,0 @@
----
-name: gsd-verify-work
-description: Validate built features through conversational UAT
-argument-hint: "[phase number, e.g., '4']"
-tools:
-  - read
-  - bash
-  - glob
-  - grep
-  - edit
-  - write
-
----
-
-<objective>
-Validate built features through conversational testing with persistent state.
-
-Purpose: Confirm what OpenCode built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.
-
-Output: {phase}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for /gsd-execute-phase
-</objective>
-
-<execution_context>
-@~/.config/opencode/get-shit-done/workflows/verify-work.md
-@~/.config/opencode/get-shit-done/templates/UAT.md
-</execution_context>
-
-<context>
-Phase: `$ARGUMENTS` (optional)
-- If provided: Test specific phase (e.g., "4")
-- If not provided: Check for active sessions or prompt for phase
-
-@.planning/STATE.md
-@.planning/ROADMAP.md
-</context>
-
-<process>
-1. Check for active UAT sessions (resume or start new)
-2. Find SUMMARY.md files for the phase
-3. Extract testable deliverables (user-observable outcomes)
-4. Create {phase}-UAT.md with test list
-5. Present tests one at a time:
-   - Show expected behavior
-   - Wait for plain text response
-   - "yes/y/next" = pass, anything else = issue (severity inferred)
-6. Update UAT.md after each response
-7. On completion: commit, present summary
-8. If issues found:
-   - Spawn parallel debug agents to diagnose root causes
-   - Spawn gsd-planner in --gaps mode to create fix plans
-   - Spawn gsd-plan-checker to verify fix plans
-   - Iterate planner ↔ checker until plans pass (max 3)
-   - Present ready status with `/new` then `/gsd-execute-phase`
-</process>
-
-<anti_patterns>
-- Don't use question for test responses — plain text conversation
-- Don't ask severity — infer from description
-- Don't present full checklist upfront — one test at a time
-- Don't run automated tests — this is manual user validation
-- Don't fix issues during testing — log as gaps, diagnose after all tests complete
-</anti_patterns>
-
-<offer_next>
-Output this markdown directly (not as a code block). Route based on UAT results:
-
-| Status | Route |
-|--------|-------|
-| All tests pass + more phases | Route A (next phase) |
-| All tests pass + last phase | Route B (milestone complete) |
-| Issues found + fix plans ready | Route C (execute fixes) |
-| Issues found + planning blocked | Route D (manual intervention) |
-
----
-
-**Route A: All tests pass, more phases remain**
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PHASE {Z} VERIFIED ✓
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-**Phase {Z}: {Name}**
-
-{N}/{N} tests passed
-UAT complete ✓
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
-
-/gsd-discuss-phase {Z+1} — gather context and clarify approach
-
-*/new first → fresh context window*
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- /gsd-plan-phase {Z+1} — skip discussion, plan directly
-- /gsd-execute-phase {Z+1} — skip to execution (if already planned)
-
-───────────────────────────────────────────────────────────────
-
----
-
-**Route B: All tests pass, milestone complete**
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PHASE {Z} VERIFIED ✓
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-**Phase {Z}: {Name}**
-
-{N}/{N} tests passed
-Final phase verified ✓
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Audit milestone** — verify requirements, cross-phase integration, E2E flows
-
-/gsd-audit-milestone
-
-*/new first → fresh context window*
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- /gsd-complete-milestone — skip audit, archive directly
-
-───────────────────────────────────────────────────────────────
-
----
-
-**Route C: Issues found, fix plans ready**
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PHASE {Z} ISSUES FOUND ⚠
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-**Phase {Z}: {Name}**
-
-{N}/{M} tests passed
-{X} issues diagnosed
-Fix plans verified ✓
-
-### Issues Found
-
-{List issues with severity from UAT.md}
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Execute fix plans** — run diagnosed fixes
-
-/gsd-execute-phase {Z} --gaps-only
-
-*/new first → fresh context window*
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- cat .planning/phases/{phase_dir}/*-PLAN.md — review fix plans
-- /gsd-plan-phase {Z} --gaps — regenerate fix plans
-
-───────────────────────────────────────────────────────────────
-
----
-
-**Route D: Issues found, planning blocked**
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PHASE {Z} BLOCKED ✗
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-**Phase {Z}: {Name}**
-
-{N}/{M} tests passed
-Fix planning blocked after {X} iterations
-
-### Unresolved Issues
-
-{List blocking issues from planner/checker output}
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Manual intervention required**
-
-Review the issues above and either:
-1. Provide guidance for fix planning
-2. Manually address blockers
-3. Accept current state and continue
-
-───────────────────────────────────────────────────────────────
-
-**Options:**
-- /gsd-plan-phase {Z} --gaps — retry fix planning with guidance
-- /gsd-discuss-phase {Z} — gather more context before replanning
-
-───────────────────────────────────────────────────────────────
-</offer_next>
-
-<success_criteria>
-- [ ] UAT.md created with tests from SUMMARY.md
-- [ ] Tests presented one at a time with expected behavior
-- [ ] Plain text responses (no structured forms)
-- [ ] Severity inferred, never asked
-- [ ] Batched writes: on issue, every 5 passes, or completion
-- [ ] Committed on completion
-- [ ] If issues: parallel debug agents diagnose root causes
-- [ ] If issues: gsd-planner creates fix plans from diagnosed gaps
-- [ ] If issues: gsd-plan-checker verifies fix plans (max 3 iterations)
-- [ ] Ready for `/gsd-execute-phase` when complete
-</success_criteria>

package/commands/gsd/whats-new.md

@@ -1,124 +0,0 @@
----
-name: gsd-whats-new
-description: See what's new in GSD since your installed version
----
-
-<objective>
-Display changes between installed version and latest available version.
-
-Shows version comparison, changelog entries for missed versions, and update instructions.
-</objective>
-
-<process>
-
-<step name="get_installed_version">
-read installed version from VERSION file:
-
-```bash
-cat ~/.config/opencode/get-shit-done/VERSION 2>/dev/null
-```
-
-**If VERSION file missing:**
-```
-## GSD What's New
-
-**Installed version:** Unknown
-
-Your installation doesn't include version tracking.
-
-**To fix:** `npx gsd-opencode --global`
-
-This will reinstall with version tracking enabled.
-```
-
-STOP here if no VERSION file.
-</step>
-
-<step name="fetch_remote_changelog">
-Fetch latest CHANGELOG.md from GitHub:
-
-Use webfetch tool with:
-- URL: `https://raw.githubusercontent.com/rokicool/gsd-opencode/main/CHANGELOG.md`
-- Prompt: "Extract all version entries with their dates and changes. Return in Keep-a-Changelog format."
-
-**If fetch fails:**
-Fall back to local changelog:
-```bash
-cat ~/.config/opencode/get-shit-done/CHANGELOG.md 2>/dev/null
-```
-
-Note to user: "Couldn't check for updates (offline or GitHub unavailable). Showing local changelog."
-</step>
-
-<step name="parse_versions">
-From the remote (or local) changelog:
-
-1. **Extract latest version** - First `## [X.Y.Z]` line after `## [Unreleased]`
-2. **Compare with installed** - From VERSION file
-3. **Extract entries between** - All version sections from latest down to (but not including) installed
-
-**Version comparison:**
-- If installed == latest: "You're on the latest version"
-- If installed < latest: Show changes since installed version
-- If installed > latest: "You're ahead of latest release (development version?)"
-</step>
-
-<step name="display_output">
-Format output clearly:
-
-**If up to date:**
-```
-## GSD What's New
-
-**Installed:** 1.4.26
-**Latest:** 1.4.26
-
-You're on the latest version.
-
-[View full changelog](https://github.com/rokicool/gsd-opencode/blob/main/CHANGELOG.md)
-```
-
-**If updates available:**
-```
-## GSD What's New
-
-**Installed:** 1.4.23
-**Latest:** 1.4.26
-
----
-
-### Changes since your version:
-
-## [1.4.26] - 2026-01-20
-
-### Added
-- Feature X
-- Feature Y
-
-### Changed
-- **BREAKING:** Changed Z behavior
-
-## [1.4.25] - 2026-01-18
-
-### Fixed
-- Bug in feature A
-
----
-
-[View full changelog](https://github.com/rokicool/gsd-opencode/blob/main/CHANGELOG.md)
-
-**To update:** `npx gsd-opencode --global`
-```
-
-**Breaking changes:** Surface prominently with **BREAKING:** prefix in the output.
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Installed version read from VERSION file
-- [ ] Remote changelog fetched (or graceful fallback to local)
-- [ ] Version comparison displayed clearly
-- [ ] Changes since installed version shown (if any)
-- [ ] Update instructions provided when behind
-</success_criteria>