gsd-opencode 1.22.1 → 1.33.0

package/commands/gsd/gsd-review.md

@@ -0,0 +1,38 @@
+---
+name: gsd-review
+description: Request cross-AI peer review of phase plans from external AI CLIs
+argument-hint: "--phase N [--gemini] [--OpenCode] [--codex] [--opencode] [--all]"
+permissions:
+   read: true
+   write: true
+   bash: true
+   glob: true
+   grep: true
+---
+
+<objective>
+Invoke external AI CLIs (Gemini, OpenCode, Codex, OpenCode) to independently review phase plans.
+Produces a structured REVIEWS.md with per-reviewer feedback that can be fed back into
+planning via /gsd-plan-phase --reviews.
+
+**Flow:** Detect CLIs → Build review prompt → Invoke each CLI → Collect responses → write REVIEWS.md
+</objective>
+
+<execution_context>
+@$HOME/.config/opencode/get-shit-done/workflows/review.md
+</execution_context>
+
+<context>
+Phase number: extracted from $ARGUMENTS (required)
+
+**Flags:**
+- `--gemini` — Include Gemini CLI review
+- `--OpenCode` — Include OpenCode CLI review (uses separate session)
+- `--codex` — Include Codex CLI review
+- `--opencode` — Include OpenCode review (uses model from user's OpenCode config)
+- `--all` — Include all available CLIs
+</context>
+
+<process>
+Execute the review workflow from @$HOME/.config/opencode/get-shit-done/workflows/review.md end-to-end.
+</process>

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

@@ -0,0 +1,35 @@
+---
+name: gsd-secure-phase
+description: Retroactively verify threat mitigations for a completed phase
+argument-hint: "[phase number]"
+permissions:
+   read: true
+   write: true
+   edit: true
+   bash: true
+   glob: true
+   grep: true
+   task: true
+   question: true
+---
+<objective>
+Verify threat mitigations for a completed phase. Three states:
+- (A) SECURITY.md exists — audit and verify mitigations
+- (B) No SECURITY.md, PLAN.md with threat model exists — run from artifacts
+- (C) Phase not executed — exit with guidance
+
+Output: updated SECURITY.md.
+</objective>
+
+<execution_context>
+@$HOME/.config/opencode/get-shit-done/workflows/secure-phase.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS — optional, defaults to last completed phase.
+</context>
+
+<process>
+Execute @$HOME/.config/opencode/get-shit-done/workflows/secure-phase.md.
+Preserve all workflow gates.
+</process>

package/commands/gsd/gsd-session-report.md

@@ -0,0 +1,19 @@
+---
+name: gsd-session-report
+description: Generate a session report with token usage estimates, work summary, and outcomes
+permissions:
+   read: true
+   bash: true
+   write: true
+---
+<objective>
+Generate a structured SESSION_REPORT.md document capturing session outcomes, work performed, and estimated resource usage. Provides a shareable artifact for post-session review.
+</objective>
+
+<execution_context>
+@$HOME/.config/opencode/get-shit-done/workflows/session-report.md
+</execution_context>
+
+<process>
+Execute the session-report workflow from @$HOME/.config/opencode/get-shit-done/workflows/session-report.md end-to-end.
+</process>

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

@@ -1,34 +1,35 @@
 ---
 name: gsd-set-profile
-description: Switch model profile for GSD agents (simple/smart/genius)
-argument-hint: <profile>
+description: Switch model profile for GSD agents (simple/smart/genius/inherit)
+argument-hint: <profile (simple|smart|genius|inherit)>
+model: haiku
 permissions:
-   read: true
-   write: true
    bash: true
 ---
 
+
+
 <objective>
-Switch the model profile used by GSD agents. Controls which OpenCode model each agent uses, balancing quality vs token spend.
+      Switch the model profile used by GSD agents. Controls which OpenCode model each agent uses, balancing quality vs token spend.
 
-Routes to the set-profile workflow which handles:
-- Argument validation (simple/smart/genius)
-- Config file creation if missing
-- Profile update in config.json
-- Confirmation with model table display
-</objective>
+      Routes to the set-profile workflow which handles:
+      - Argument validation (simple/smart/genius)
+      - Config file creation if missing
+      - Profile update in config.json
+      - Confirmation with model table display
+      </objective>
 
-<execution_context>
-@$HOME/.config/opencode/get-shit-done/workflows/oc-set-profile.md
-</execution_context>
+      <execution_context>
+      @$HOME/.config/opencode/get-shit-done/workflows/oc-set-profile.md
+      </execution_context>
 
-<process>
-**Follow the set-profile workflow** from `@$HOME/.config/opencode/get-shit-done/workflows/oc-set-profile.md`.
+      <process>
+      **Follow the set-profile workflow** from `@$HOME/.config/opencode/get-shit-done/workflows/oc-set-profile.md`.
 
-The workflow handles all logic including:
-1. Profile argument validation
-2. Config file ensuring
-3. Config reading and updating
-4. Model table generation from MODEL_PROFILES
-5. Confirmation display
-</process>
+      The workflow handles all logic including:
+      1. Profile argument validation
+      2. Config file ensuring
+      3. Config reading and updating
+      4. Model table generation from MODEL_PROFILES
+      5. Confirmation display
+      </process> 

package/commands/gsd/gsd-ship.md

@@ -0,0 +1,23 @@
+---
+name: gsd-ship
+description: Create PR, run review, and prepare for merge after verification passes
+argument-hint: "[phase number or milestone, e.g., '4' or 'v1.0']"
+permissions:
+   read: true
+   bash: true
+   grep: true
+   glob: true
+   write: true
+   question: true
+---
+<objective>
+Bridge local completion → merged PR. After /gsd-verify-work passes, ship the work: push branch, create PR with auto-generated body, optionally trigger review, and track the merge.
+
+Closes the plan → execute → verify → ship loop.
+</objective>
+
+<execution_context>
+@$HOME/.config/opencode/get-shit-done/workflows/ship.md
+</execution_context>
+
+Execute the ship workflow from @$HOME/.config/opencode/get-shit-done/workflows/ship.md end-to-end.

package/commands/gsd/gsd-stats.md

@@ -0,0 +1,18 @@
+---
+name: gsd-stats
+description: Display project statistics — phases, plans, requirements, git metrics, and timeline
+permissions:
+   read: true
+   bash: true
+---
+<objective>
+Display comprehensive project statistics including phase progress, plan execution metrics, requirements completion, git history stats, and project timeline.
+</objective>
+
+<execution_context>
+@$HOME/.config/opencode/get-shit-done/workflows/stats.md
+</execution_context>
+
+<process>
+Execute the stats workflow from @$HOME/.config/opencode/get-shit-done/workflows/stats.md end-to-end.
+</process>

package/commands/gsd/gsd-thread.md

@@ -0,0 +1,127 @@
+---
+name: gsd-thread
+description: Manage persistent context threads for cross-session work
+argument-hint: [name | description]
+permissions:
+   read: true
+   write: true
+   bash: true
+---
+
+<objective>
+Create, list, or resume persistent context threads. Threads are lightweight
+cross-session knowledge stores for work that spans multiple sessions but
+doesn't belong to any specific phase.
+</objective>
+
+<process>
+
+**Parse $ARGUMENTS to determine mode:**
+
+<mode_list>
+**If no arguments or $ARGUMENTS is empty:**
+
+List all threads:
+```bash
+ls .planning/threads/*.md 2>/dev/null
+```
+
+For each thread, read the first few lines to show title and status:
+```
+## Active Threads
+
+| Thread | Status | Last Updated |
+|--------|--------|-------------|
+| fix-deploy-key-auth | OPEN | 2026-03-15 |
+| pasta-tcp-timeout | RESOLVED | 2026-03-12 |
+| perf-investigation | IN PROGRESS | 2026-03-17 |
+```
+
+If no threads exist, show:
+```
+No threads found. Create one with: /gsd-thread <description>
+```
+</mode_list>
+
+<mode_resume>
+**If $ARGUMENTS matches an existing thread name (file exists):**
+
+Resume the thread — load its context into the current session:
+```bash
+cat ".planning/threads/${THREAD_NAME}.md"
+```
+
+Display the thread content and ask what the user wants to work on next.
+Update the thread's status to `IN PROGRESS` if it was `OPEN`.
+</mode_resume>
+
+<mode_create>
+**If $ARGUMENTS is a new description (no matching thread file):**
+
+Create a new thread:
+
+1. Generate slug from description:
+   ```bash
+   SLUG=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" generate-slug "$ARGUMENTS" --raw)
+   ```
+
+2. Create the threads directory if needed:
+   ```bash
+   mkdir -p .planning/threads
+   ```
+
+3. write the thread file:
+   ```bash
+   cat > ".planning/threads/${SLUG}.md" << 'EOF'
+   # Thread: {description}
+
+   ## Status: OPEN
+
+   ## Goal
+
+   {description}
+
+   ## Context
+
+   *Created from conversation on {today's date}.*
+
+   ## References
+
+   - *(add links, file paths, or issue numbers)*
+
+   ## Next Steps
+
+   - *(what the next session should do first)*
+   EOF
+   ```
+
+4. If there's relevant context in the current conversation (code snippets,
+   error messages, investigation results), extract and add it to the Context
+   section.
+
+5. Commit:
+   ```bash
+   node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" commit "docs: create thread — ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"
+   ```
+
+6. Report:
+   ```
+   ## 🧵 Thread Created
+
+   Thread: {slug}
+   File: .planning/threads/{slug}.md
+
+   Resume anytime with: /gsd-thread {slug}
+   ```
+</mode_create>
+
+</process>
+
+<notes>
+- Threads are NOT phase-scoped — they exist independently of the roadmap
+- Lighter weight than /gsd-pause-work — no phase state, no plan context
+- The value is in Context and Next Steps — a cold-start session can pick up immediately
+- Threads can be promoted to phases or backlog items when they mature:
+  /gsd-add-phase or /gsd-add-backlog with context from the thread
+- Thread files live in .planning/threads/ — no collision with phases or other GSD structures
+</notes>

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

@@ -0,0 +1,34 @@
+---
+name: gsd-ui-phase
+description: Generate UI design contract (UI-SPEC.md) for frontend phases
+argument-hint: "[phase]"
+permissions:
+   read: true
+   write: true
+   bash: true
+   glob: true
+   grep: true
+   task: true
+   webfetch: true
+   question: true
+   mcp__context7__*: true
+---
+<objective>
+Create a UI design contract (UI-SPEC.md) for a frontend phase.
+Orchestrates gsd-ui-researcher and gsd-ui-checker.
+Flow: Validate → Research UI → Verify UI-SPEC → Done
+</objective>
+
+<execution_context>
+@$HOME/.config/opencode/get-shit-done/workflows/ui-phase.md
+@$HOME/.config/opencode/get-shit-done/references/ui-brand.md
+</execution_context>
+
+<context>
+Phase number: $ARGUMENTS — optional, auto-detects next unplanned phase if omitted.
+</context>
+
+<process>
+Execute @$HOME/.config/opencode/get-shit-done/workflows/ui-phase.md end-to-end.
+Preserve all workflow gates.
+</process>

package/commands/gsd/gsd-ui-review.md

@@ -0,0 +1,32 @@
+---
+name: gsd-ui-review
+description: Retroactive 6-pillar visual audit of implemented frontend code
+argument-hint: "[phase]"
+permissions:
+   read: true
+   write: true
+   bash: true
+   glob: true
+   grep: true
+   task: true
+   question: true
+---
+<objective>
+Conduct a retroactive 6-pillar visual audit. Produces UI-REVIEW.md with
+graded assessment (1-4 per pillar). Works on any project.
+Output: {phase_num}-UI-REVIEW.md
+</objective>
+
+<execution_context>
+@$HOME/.config/opencode/get-shit-done/workflows/ui-review.md
+@$HOME/.config/opencode/get-shit-done/references/ui-brand.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS — optional, defaults to last completed phase.
+</context>
+
+<process>
+Execute @$HOME/.config/opencode/get-shit-done/workflows/ui-review.md end-to-end.
+Preserve all workflow gates.
+</process>

package/commands/gsd/gsd-workstreams.md

@@ -0,0 +1,71 @@
+---
+name: gsd-workstreams
+description: Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
+permissions:
+   read: true
+   bash: true
+---
+
+# /gsd-workstreams
+
+<objective>
+      Manage parallel workstreams for concurrent milestone work.
+</objective>
+
+## Usage
+
+`/gsd-workstreams [subcommand] [args]`
+
+### Subcommands
+
+| Command | Description |
+|---------|-------------|
+| `list` | List all workstreams with status |
+| `create <name>` | Create a new workstream |
+| `status <name>` | Detailed status for one workstream |
+| `switch <name>` | Set active workstream |
+| `progress` | Progress summary across all workstreams |
+| `complete <name>` | Archive a completed workstream |
+| `resume <name>` | Resume work in a workstream |
+
+## Step 1: Parse Subcommand
+
+Parse the user's input to determine which workstream operation to perform.
+If no subcommand given, default to `list`.
+
+## Step 2: Execute Operation
+
+### list
+Run: `node "$GSD_TOOLS" workstream list --raw --cwd "$CWD"`
+Display the workstreams in a table format showing name, status, current phase, and progress.
+
+### create
+Run: `node "$GSD_TOOLS" workstream create <name> --raw --cwd "$CWD"`
+After creation, display the new workstream path and suggest next steps:
+- `/gsd-new-milestone --ws <name>` to set up the milestone
+
+### status
+Run: `node "$GSD_TOOLS" workstream status <name> --raw --cwd "$CWD"`
+Display detailed phase breakdown and state information.
+
+### switch
+Run: `node "$GSD_TOOLS" workstream set <name> --raw --cwd "$CWD"`
+Also set `GSD_WORKSTREAM` for the current session when the runtime supports it.
+If the runtime exposes a session identifier, GSD also stores the active workstream
+session-locally so concurrent sessions do not overwrite each other.
+
+### progress
+Run: `node "$GSD_TOOLS" workstream progress --raw --cwd "$CWD"`
+Display a progress overview across all workstreams.
+
+### complete
+Run: `node "$GSD_TOOLS" workstream complete <name> --raw --cwd "$CWD"`
+Archive the workstream to milestones/.
+
+### resume
+Set the workstream as active and suggest `/gsd-resume-work --ws <name>`.
+
+## Step 3: Display Results
+
+Format the JSON output from gsd-tools into a human-readable display.
+Include the `${GSD_WS}` flag in any routing suggestions.