gsd-opencode 1.3.32 → 1.4.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Lex Christopherson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/command/gsd/add-phase.md

@@ -3,9 +3,9 @@ name: gsd:add-phase
 description: Add phase to end of current milestone in roadmap
 argument-hint: <description>
 allowed-tools:
-  - Read
-  - Write
-  - Bash
+  - read
+  - write
+  - bash
 ---
 
 <objective>
@@ -25,7 +25,7 @@ Purpose: Add planned work discovered during execution that belongs at the end of
 
 <step name="parse_arguments">
 Parse the command arguments:
-- All arguments become the phase description
+- All arguments ($ARGUMENTS) become the phase description
 - Example: `/gsd:add-phase Add authentication` → description = "Add authentication"
 - Example: `/gsd:add-phase Fix critical performance issues` → description = "Fix critical performance issues"
 

package/command/gsd/add-todo.md

@@ -0,0 +1,182 @@
+---
+name: gsd:add-todo
+description: Capture idea or task as todo from current conversation context
+argument-hint: [optional description]
+allowed-tools:
+  - read
+  - write
+  - bash
+  - glob
+---
+
+<objective>
+Capture an idea, task, or issue that surfaces during a GSD session as a structured todo for later work.
+
+Enables "thought → capture → continue" flow without losing context or derailing current work.
+</objective>
+
+<context>
+@.planning/STATE.md
+</context>
+
+<process>
+
+<step name="ensure_directory">
+```bash
+mkdir -p .planning/todos/pending .planning/todos/done
+```
+</step>
+
+<step name="check_existing_areas">
+```bash
+ls .planning/todos/pending/*.md 2>/dev/null | xargs -I {} grep "^area:" {} 2>/dev/null | cut -d' ' -f2 | sort -u
+```
+
+Note existing areas for consistency in infer_area step.
+</step>
+
+<step name="extract_content">
+**With arguments:** Use ($ARGUMENTS) as the title/focus.
+- `/gsd:add-todo Add auth token refresh` → title = "Add auth token refresh"
+
+**Without arguments:** Analyze recent conversation to extract:
+- The specific problem, idea, or task discussed
+- Relevant file paths mentioned
+- Technical details (error messages, line numbers, constraints)
+
+Formulate:
+- `title`: 3-10 word descriptive title (action verb preferred)
+- `problem`: What's wrong or why this is needed
+- `solution`: Approach hints or "TBD" if just an idea
+- `files`: Relevant paths with line numbers from conversation
+</step>
+
+<step name="infer_area">
+Infer area from file paths:
+
+| Path pattern | Area |
+|--------------|------|
+| `src/api/*`, `api/*` | `api` |
+| `src/components/*`, `src/ui/*` | `ui` |
+| `src/auth/*`, `auth/*` | `auth` |
+| `src/db/*`, `database/*` | `database` |
+| `tests/*`, `__tests__/*` | `testing` |
+| `docs/*` | `docs` |
+| `.planning/*` | `planning` |
+| `scripts/*`, `bin/*` | `tooling` |
+| No files or unclear | `general` |
+
+Use existing area from step 2 if similar match exists.
+</step>
+
+<step name="check_duplicates">
+```bash
+grep -l -i "[key words from title]" .planning/todos/pending/*.md 2>/dev/null
+```
+
+If potential duplicate found:
+1. Read the existing todo
+2. Compare scope
+
+If overlapping, use question:
+- header: "Duplicate?"
+- question: "Similar todo exists: [title]. What would you like to do?"
+- options:
+  - "Skip" — keep existing todo
+  - "Replace" — update existing with new context
+  - "Add anyway" — create as separate todo
+</step>
+
+<step name="create_file">
+```bash
+timestamp=$(date "+%Y-%m-%dT%H:%M")
+date_prefix=$(date "+%Y-%m-%d")
+```
+
+Generate slug from title (lowercase, hyphens, no special chars).
+
+Write to `.planning/todos/pending/${date_prefix}-${slug}.md`:
+
+```markdown
+---
+created: [timestamp]
+title: [title]
+area: [area]
+files:
+  - [file:lines]
+---
+
+## Problem
+
+[problem description - enough context for future Claude to understand weeks later]
+
+## Solution
+
+[approach hints or "TBD"]
+```
+</step>
+
+<step name="update_state">
+If `.planning/STATE.md` exists:
+
+1. Count todos: `ls .planning/todos/pending/*.md 2>/dev/null | wc -l`
+2. Update "### Pending Todos" under "## Accumulated Context"
+</step>
+
+<step name="git_commit">
+Commit the todo and any updated state:
+
+```bash
+git add .planning/todos/pending/[filename]
+[ -f .planning/STATE.md ] && git add .planning/STATE.md
+git commit -m "$(cat <<'EOF'
+docs: capture todo - [title]
+
+Area: [area]
+EOF
+)"
+```
+
+Confirm: "Committed: docs: capture todo - [title]"
+</step>
+
+<step name="confirm">
+```
+Todo saved: .planning/todos/pending/[filename]
+
+  [title]
+  Area: [area]
+  Files: [count] referenced
+
+---
+
+Would you like to:
+
+1. Continue with current work
+2. Add another todo
+3. View all todos (/gsd:check-todos)
+```
+</step>
+
+</process>
+
+<output>
+- `.planning/todos/pending/[date]-[slug].md`
+- Updated `.planning/STATE.md` (if exists)
+</output>
+
+<anti_patterns>
+- Don't create todos for work in current plan (that's deviation rule territory)
+- Don't create elaborate solution sections — captures ideas, not plans
+- Don't block on missing information — "TBD" is fine
+</anti_patterns>
+
+<success_criteria>
+- [ ] Directory structure exists
+- [ ] Todo file created with valid frontmatter
+- [ ] Problem section has enough context for future Claude
+- [ ] No duplicates (checked and resolved)
+- [ ] Area consistent with existing todos
+- [ ] STATE.md updated if exists
+- [ ] Todo and state committed to git
+</success_criteria>

package/command/gsd/check-todos.md

@@ -0,0 +1,217 @@
+---
+name: gsd:check-todos
+description: List pending todos and select one to work on
+argument-hint: [area filter]
+allowed-tools:
+  - read
+  - write
+  - bash
+  - glob
+  - question
+---
+
+<objective>
+List all pending todos, allow selection, load full context for the selected todo, and route to appropriate action.
+
+Enables reviewing captured ideas and deciding what to work on next.
+</objective>
+
+<context>
+@.planning/STATE.md
+@.planning/ROADMAP.md
+</context>
+
+<process>
+
+<step name="check_exist">
+```bash
+TODO_COUNT=$(ls .planning/todos/pending/*.md 2>/dev/null | wc -l | tr -d ' ')
+echo "Pending todos: $TODO_COUNT"
+```
+
+If count is 0:
+```
+No pending todos.
+
+Todos are captured during work sessions with /gsd:add-todo.
+
+---
+
+Would you like to:
+
+1. Continue with current phase (/gsd:progress)
+2. Add a todo now (/gsd:add-todo)
+```
+
+Exit.
+</step>
+
+<step name="parse_filter">
+Check for area filter in arguments:
+- `/gsd:check-todos` → show all
+- `/gsd:check-todos api` → filter to area:api only
+</step>
+
+<step name="list_todos">
+```bash
+for file in .planning/todos/pending/*.md; do
+  created=$(grep "^created:" "$file" | cut -d' ' -f2)
+  title=$(grep "^title:" "$file" | cut -d':' -f2- | xargs)
+  area=$(grep "^area:" "$file" | cut -d' ' -f2)
+  echo "$created|$title|$area|$file"
+done | sort
+```
+
+Apply area filter if specified. Display as numbered list:
+
+```
+Pending Todos:
+
+1. Add auth token refresh (api, 2d ago)
+2. Fix modal z-index issue (ui, 1d ago)
+3. Refactor database connection pool (database, 5h ago)
+
+---
+
+Reply with a number to view details, or:
+- `/gsd:check-todos [area]` to filter by area
+- `q` to exit
+```
+
+Format age as relative time.
+</step>
+
+<step name="handle_selection">
+Wait for user to reply with a number.
+
+If valid: load selected todo, proceed.
+If invalid: "Invalid selection. Reply with a number (1-[N]) or `q` to exit."
+</step>
+
+<step name="load_context">
+Read the todo file completely. Display:
+
+```
+## [title]
+
+**Area:** [area]
+**Created:** [date] ([relative time] ago)
+**Files:** [list or "None"]
+
+### Problem
+[problem section content]
+
+### Solution
+[solution section content]
+```
+
+If `files` field has entries, read and briefly summarize each.
+</step>
+
+<step name="check_roadmap">
+```bash
+ls .planning/ROADMAP.md 2>/dev/null && echo "Roadmap exists"
+```
+
+If roadmap exists:
+1. Check if todo's area matches an upcoming phase
+2. Check if todo's files overlap with a phase's scope
+3. Note any match for action options
+</step>
+
+<step name="offer_actions">
+**If todo maps to a roadmap phase:**
+
+Use question:
+- header: "Action"
+- question: "This todo relates to Phase [N]: [name]. What would you like to do?"
+- options:
+  - "Work on it now" — move to done, start working
+  - "Add to phase plan" — include when planning Phase [N]
+  - "Brainstorm approach" — think through before deciding
+  - "Put it back" — return to list
+
+**If no roadmap match:**
+
+Use question:
+- header: "Action"
+- question: "What would you like to do with this todo?"
+- options:
+  - "Work on it now" — move to done, start working
+  - "Create a phase" — /gsd:add-phase with this scope
+  - "Brainstorm approach" — think through before deciding
+  - "Put it back" — return to list
+</step>
+
+<step name="execute_action">
+**Work on it now:**
+```bash
+mv ".planning/todos/pending/[filename]" ".planning/todos/done/"
+```
+Update STATE.md todo count. Present problem/solution context. Begin work or ask how to proceed.
+
+**Add to phase plan:**
+Note todo reference in phase planning notes. Keep in pending. Return to list or exit.
+
+**Create a phase:**
+Display: `/gsd:add-phase [description from todo]`
+Keep in pending. User runs command in fresh context.
+
+**Brainstorm approach:**
+Keep in pending. Start discussion about problem and approaches.
+
+**Put it back:**
+Return to list_todos step.
+</step>
+
+<step name="update_state">
+After any action that changes todo count:
+
+```bash
+ls .planning/todos/pending/*.md 2>/dev/null | wc -l
+```
+
+Update STATE.md "### Pending Todos" section if exists.
+</step>
+
+<step name="git_commit">
+If todo was moved to done/, commit the change:
+
+```bash
+git add .planning/todos/done/[filename]
+git rm --cached .planning/todos/pending/[filename] 2>/dev/null || true
+[ -f .planning/STATE.md ] && git add .planning/STATE.md
+git commit -m "$(cat <<'EOF'
+docs: start work on todo - [title]
+
+Moved to done/, beginning implementation.
+EOF
+)"
+```
+
+Confirm: "Committed: docs: start work on todo - [title]"
+</step>
+
+</process>
+
+<output>
+- Moved todo to `.planning/todos/done/` (if "Work on it now")
+- Updated `.planning/STATE.md` (if todo count changed)
+</output>
+
+<anti_patterns>
+- Don't delete todos — move to done/ when work begins
+- Don't start work without moving to done/ first
+- Don't create plans from this command — route to /gsd:plan-phase or /gsd:add-phase
+</anti_patterns>
+
+<success_criteria>
+- [ ] All pending todos listed with title, area, age
+- [ ] Area filter applied if specified
+- [ ] Selected todo's full context loaded
+- [ ] Roadmap context checked for phase match
+- [ ] Appropriate actions offered
+- [ ] Selected action executed
+- [ ] STATE.md updated if todo count changed
+- [ ] Changes committed to git (if todo moved to done/)
+</success_criteria>

package/command/gsd/complete-milestone.md

@@ -1,11 +1,12 @@
 ---
+type: prompt
 name: gsd:complete-milestone
 description: Archive completed milestone and prepare for next version
 argument-hint: <version>
 allowed-tools:
-  - Read
-  - Write
-  - Bash
+  - read
+  - write
+  - bash
 ---
 
 <objective>
@@ -18,8 +19,8 @@ Output: Milestone archived, roadmap reorganized, git tagged.
 <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)
+- @~/.config/opencode/gsd-opencode/workflows/complete-milestone.md (main workflow)
+- @~/.config/opencode/gsd-opencode/templates/milestone-archive.md (archive template)
   </execution_context>
 
 <context>

package/command/gsd/consider-issues.md

@@ -2,11 +2,11 @@
 name: gsd:consider-issues
 description: Review deferred issues with codebase context, close resolved ones, identify urgent ones
 allowed-tools:
-  - Read
-  - Bash
-  - Grep
-  - Glob
-  - Edit
+  - read
+  - bash
+  - grep
+  - glob
+  - edit
   - question
 ---
 

package/command/gsd/create-roadmap.md

@@ -2,11 +2,11 @@
 name: gsd:create-roadmap
 description: Create roadmap with phases for the project
 allowed-tools:
-  - Read
-  - Write
-  - Bash
+  - read
+  - write
+  - bash
   - question
-  - Glob
+  - glob
 ---
 
 <objective>
@@ -16,9 +16,9 @@ Roadmaps define what work happens in what order. Run after /gsd:new-project.
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/create-roadmap.md
-@~/.config/opencode/get-shit-done/templates/roadmap.md
-@~/.config/opencode/get-shit-done/templates/state.md
+@~/.config/opencode/gsd-opencode/workflows/create-roadmap.md
+@~/.config/opencode/gsd-opencode/templates/roadmap.md
+@~/.config/opencode/gsd-opencode/templates/state.md
 </execution_context>
 
 <context>

package/command/gsd/debug.md

@@ -0,0 +1,58 @@
+---
+name: gsd:debug
+description: Systematic debugging with persistent state across context resets
+argument-hint: [issue description]
+allowed-tools:
+  - read
+  - write
+  - edit
+  - bash
+  - grep
+  - glob
+  - question
+---
+
+<objective>
+Debug issues using scientific method with a persistent debug document that survives `/clear`.
+
+If resuming (no arguments and active session exists): pick up where you left off.
+If starting new: gather symptoms, then investigate autonomously.
+</objective>
+
+<execution_context>
+@~/.config/opencode/gsd-opencode/workflows/debug.md
+@~/.config/opencode/gsd-opencode/templates/DEBUG.md
+</execution_context>
+
+<context>
+User's issue: ($ARGUMENTS)
+
+Check for active debug sessions:
+```bash
+ls .planning/debug/*.md 2>/dev/null | head -5
+```
+</context>
+
+<process>
+Follow the workflow in @~/.config/opencode/gsd-opencode/workflows/debug.md
+
+**Quick reference:**
+
+1. **Check for active sessions** - Offer to resume or start new
+2. **Gather symptoms** - What happened? What should happen? Errors? When?
+3. **Create DEBUG.md** - Document symptoms in `.planning/debug/[slug].md`
+4. **Investigate** - Evidence → Hypothesis → Test → Eliminate or Confirm
+5. **Fix and verify** - Minimal fix, verify against original symptoms
+6. **Archive** - Move to `.planning/debug/resolved/`
+
+**Key principle:** The DEBUG.md is your memory. Update it constantly. It survives `/clear`.
+</process>
+
+<success_criteria>
+- [ ] Active sessions checked before starting new
+- [ ] Symptoms gathered through question (not inline questions)
+- [ ] DEBUG.md tracks all investigation state
+- [ ] Scientific method followed (not random fixes)
+- [ ] Root cause confirmed with evidence before fixing
+- [ ] Fix verified and session archived
+</success_criteria>

package/command/gsd/discuss-milestone.md

@@ -11,7 +11,7 @@ Output: Context gathered, then routes to /gsd:new-milestone
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/discuss-milestone.md
+@~/.config/opencode/gsd-opencode/workflows/discuss-milestone.md
 </execution_context>
 
 <context>

package/command/gsd/discuss-phase.md

@@ -7,18 +7,18 @@ argument-hint: "[phase]"
 <objective>
 Help the user articulate their vision for a phase through collaborative thinking.
 
-Purpose: Understand HOW the user imagines this phase working — what it looks like, what's essential, what's out of scope. You're a thinking partner helping them crystallize their vision, not an interviewer gathering technical requirements.
+Purpose: Understand HOW the user imagines this phase working — what it looks like, what's essential. You're a thinking partner helping them crystallize their vision, not an interviewer gathering technical requirements.
 
 Output: {phase}-CONTEXT.md capturing the user's vision for the phase
 </objective>
 
 <execution_context>
-@~/.config/opencode/get-shit-done/workflows/discuss-phase.md
-@~/.config/opencode/get-shit-done/templates/context.md
+@~/.config/opencode/gsd-opencode/workflows/discuss-phase.md
+@~/.config/opencode/gsd-opencode/templates/context.md
 </execution_context>
 
 <context>
-Phase number: $ARGUMENTS (required)
+Phase number: ($ARGUMENTS) (required)
 
 **Load project state first:**
 @.planning/STATE.md
@@ -36,7 +36,6 @@ Phase number: $ARGUMENTS (required)
    - Use question: "How do you imagine this working?" with interpretation options
    - Use question to follow their thread — probe what excites them
    - Use question to sharpen the core — what's essential for THIS phase
-   - Use question to find boundaries — what's explicitly out of scope
    - Use question for decision gate (ready / ask more / let me add context)
    - Create CONTEXT.md capturing their vision
 5. Offer next steps (research or plan the phase)
@@ -55,6 +54,6 @@ User is the visionary, you are the builder:
 
 - Phase validated against roadmap
 - Vision gathered through collaborative thinking (not interrogation)
-- CONTEXT.md captures: how it works, what's essential, what's out of scope
+- CONTEXT.md captures: how it works, what's essential
 - User knows next steps (research or plan the phase)
 </success_criteria>