gsd-opencode 1.5.2 → 1.6.1

package/get-shit-done/templates/UAT.md

@@ -0,0 +1,247 @@
+# UAT Template
+
+Template for `.planning/phases/XX-name/{phase}-UAT.md` — persistent UAT session tracking.
+
+---
+
+## File Template
+
+```markdown
+---
+status: testing | complete | diagnosed
+phase: XX-name
+source: [list of SUMMARY.md files tested]
+started: [ISO timestamp]
+updated: [ISO timestamp]
+---
+
+## Current Test
+<!-- OVERWRITE each test - shows where we are -->
+
+number: [N]
+name: [test name]
+expected: |
+  [what user should observe]
+awaiting: user response
+
+## Tests
+
+### 1. [Test Name]
+expected: [observable behavior - what user should see]
+result: [pending]
+
+### 2. [Test Name]
+expected: [observable behavior]
+result: pass
+
+### 3. [Test Name]
+expected: [observable behavior]
+result: issue
+reported: "[verbatim user response]"
+severity: major
+
+### 4. [Test Name]
+expected: [observable behavior]
+result: skipped
+reason: [why skipped]
+
+...
+
+## Summary
+
+total: [N]
+passed: [N]
+issues: [N]
+pending: [N]
+skipped: [N]
+
+## Gaps
+
+<!-- YAML format for plan-phase --gaps consumption -->
+- truth: "[expected behavior from test]"
+  status: failed
+  reason: "User reported: [verbatim response]"
+  severity: blocker | major | minor | cosmetic
+  test: [N]
+  root_cause: ""     # Filled by diagnosis
+  artifacts: []      # Filled by diagnosis
+  missing: []        # Filled by diagnosis
+  debug_session: ""  # Filled by diagnosis
+```
+
+---
+
+<section_rules>
+
+**Frontmatter:**
+- `status`: OVERWRITE - "testing" or "complete"
+- `phase`: IMMUTABLE - set on creation
+- `source`: IMMUTABLE - SUMMARY files being tested
+- `started`: IMMUTABLE - set on creation
+- `updated`: OVERWRITE - update on every change
+
+**Current Test:**
+- OVERWRITE entirely on each test transition
+- Shows which test is active and what's awaited
+- On completion: "[testing complete]"
+
+**Tests:**
+- Each test: OVERWRITE result field when user responds
+- `result` values: [pending], pass, issue, skipped
+- If issue: add `reported` (verbatim) and `severity` (inferred)
+- If skipped: add `reason` if provided
+
+**Summary:**
+- OVERWRITE counts after each response
+- Tracks: total, passed, issues, pending, skipped
+
+**Gaps:**
+- APPEND only when issue found (YAML format)
+- After diagnosis: fill `root_cause`, `artifacts`, `missing`, `debug_session`
+- This section feeds directly into /gsd-plan-phase --gaps
+
+</section_rules>
+
+<diagnosis_lifecycle>
+
+**After testing complete (status: complete), if gaps exist:**
+
+1. User runs diagnosis (from verify-work offer or manually)
+2. diagnose-issues workflow spawns parallel debug agents
+3. Each agent investigates one gap, returns root cause
+4. UAT.md Gaps section updated with diagnosis:
+   - Each gap gets `root_cause`, `artifacts`, `missing`, `debug_session` filled
+5. status → "diagnosed"
+6. Ready for /gsd-plan-phase --gaps with root causes
+
+**After diagnosis:**
+```yaml
+## Gaps
+
+- truth: "Comment appears immediately after submission"
+  status: failed
+  reason: "User reported: works but doesn't show until I refresh the page"
+  severity: major
+  test: 2
+  root_cause: "useEffect in CommentList.tsx missing commentCount dependency"
+  artifacts:
+    - path: "src/components/CommentList.tsx"
+      issue: "useEffect missing dependency"
+  missing:
+    - "Add commentCount to useEffect dependency array"
+  debug_session: ".planning/debug/comment-not-refreshing.md"
+```
+
+</diagnosis_lifecycle>
+
+<lifecycle>
+
+**Creation:** When /gsd-verify-work starts new session
+- Extract tests from SUMMARY.md files
+- Set status to "testing"
+- Current Test points to test 1
+- All tests have result: [pending]
+
+**During testing:**
+- Present test from Current Test section
+- User responds with pass confirmation or issue description
+- Update test result (pass/issue/skipped)
+- Update Summary counts
+- If issue: append to Gaps section (YAML format), infer severity
+- Move Current Test to next pending test
+
+**On completion:**
+- status → "complete"
+- Current Test → "[testing complete]"
+- Commit file
+- Present summary with next steps
+
+**Resume after /new:**
+1. read frontmatter → know phase and status
+2. read Current Test → know where we are
+3. Find first [pending] result → continue from there
+4. Summary shows progress so far
+
+</lifecycle>
+
+<severity_guide>
+
+Severity is INFERRED from user's natural language, never asked.
+
+| User describes | Infer |
+|----------------|-------|
+| Crash, error, exception, fails completely, unusable | blocker |
+| Doesn't work, nothing happens, wrong behavior, missing | major |
+| Works but..., slow, weird, minor, small issue | minor |
+| Color, font, spacing, alignment, visual, looks off | cosmetic |
+
+Default: **major** (safe default, user can clarify if wrong)
+
+</severity_guide>
+
+<good_example>
+```markdown
+---
+status: diagnosed
+phase: 04-comments
+source: 04-01-SUMMARY.md, 04-02-SUMMARY.md
+started: 2025-01-15T10:30:00Z
+updated: 2025-01-15T10:45:00Z
+---
+
+## Current Test
+
+[testing complete]
+
+## Tests
+
+### 1. View Comments on Post
+expected: Comments section expands, shows count and comment list
+result: pass
+
+### 2. Create Top-Level Comment
+expected: Submit comment via rich text editor, appears in list with author info
+result: issue
+reported: "works but doesn't show until I refresh the page"
+severity: major
+
+### 3. Reply to a Comment
+expected: Click Reply, inline composer appears, submit shows nested reply
+result: pass
+
+### 4. Visual Nesting
+expected: 3+ level thread shows indentation, left borders, caps at reasonable depth
+result: pass
+
+### 5. Delete Own Comment
+expected: Click delete on own comment, removed or shows [deleted] if has replies
+result: pass
+
+### 6. Comment Count
+expected: Post shows accurate count, increments when adding comment
+result: pass
+
+## Summary
+
+total: 6
+passed: 5
+issues: 1
+pending: 0
+skipped: 0
+
+## Gaps
+
+- truth: "Comment appears immediately after submission in list"
+  status: failed
+  reason: "User reported: works but doesn't show until I refresh the page"
+  severity: major
+  test: 2
+  root_cause: "useEffect in CommentList.tsx missing commentCount dependency"
+  artifacts:
+    - path: "src/components/CommentList.tsx"
+      issue: "useEffect missing dependency"
+  missing:
+    - "Add commentCount to useEffect dependency array"
+  debug_session: ".planning/debug/comment-not-refreshing.md"
+```
+</good_example>

package/get-shit-done/templates/codebase/architecture.md

@@ -124,7 +124,7 @@ Template for `.planning/codebase/ARCHITECTURE.md` - captures conceptual code org
 **Command Layer:**
 - Purpose: Parse user input and route to appropriate handler
 - Contains: Command definitions, argument parsing, help text
-- Location: `src/command/*.ts`
+- Location: `src/commands/*.ts`
 - Depends on: Service layer for business logic
 - Used by: CLI entry point (`src/index.ts`)
 
@@ -148,7 +148,7 @@ Template for `.planning/codebase/ARCHITECTURE.md` - captures conceptual code org
 
 1. User runs: `gsd new-project`
 2. Commander parses args and flags
-3. Command handler invoked (`src/command/new-project.ts`)
+3. Command handler invoked (`src/commands/new-project.ts`)
 4. Handler calls service methods (`src/services/project.ts` → `create()`)
 5. Service reads templates, processes files, writes output
 6. Results logged to console
@@ -168,7 +168,7 @@ Template for `.planning/codebase/ARCHITECTURE.md` - captures conceptual code org
 
 **Command:**
 - Purpose: CLI command definition
-- Examples: `src/command/new-project.ts`, `src/command/plan-phase.ts`
+- Examples: `src/commands/new-project.ts`, `src/commands/plan-phase.ts`
 - Pattern: Commander.js command registration
 
 **Template:**
@@ -184,7 +184,7 @@ Template for `.planning/codebase/ARCHITECTURE.md` - captures conceptual code org
 - Responsibilities: Register commands, parse args, display help
 
 **Commands:**
-- Location: `src/command/*.ts`
+- Location: `src/commands/*.ts`
 - Triggers: Matched command from CLI
 - Responsibilities: Validate input, call services, format output
 
@@ -241,7 +241,7 @@ Template for `.planning/codebase/ARCHITECTURE.md` - captures conceptual code org
 Include file paths as concrete examples of abstractions. Use backtick formatting: `src/services/user.ts`. This makes the architecture document actionable for OpenCode when planning.
 
 **When filling this template:**
-- Read main entry points (index, server, main)
+- read main entry points (index, server, main)
 - Identify layers by reading imports/dependencies
 - Trace a typical request/command execution
 - Note recurring patterns (services, controllers, repositories)

package/get-shit-done/templates/codebase/concerns.md

@@ -306,5 +306,5 @@ Template for `.planning/codebase/CONCERNS.md` - captures known issues and areas
 - Planning refactoring work
 
 **How this gets populated:**
-explore agents detect these during codebase mapping. Manual additions welcome for human-discovered issues. This is living documentation, not a complaint list.
+Explore agents detect these during codebase mapping. Manual additions welcome for human-discovered issues. This is living documentation, not a complaint list.
 </guidelines>

package/get-shit-done/templates/codebase/conventions.md

@@ -301,7 +301,7 @@ Template for `.planning/codebase/CONVENTIONS.md` - captures coding style and pat
 **Analysis approach:**
 - Scan src/ directory for file naming patterns
 - Check package.json scripts for lint/format commands
-- Read 5-10 files to identify function naming, error handling
+- read 5-10 files to identify function naming, error handling
 - Look for config files (.prettierrc, eslint.config.js)
 - Note patterns in imports, comments, function signatures
 </guidelines>

package/get-shit-done/templates/codebase/structure.md

@@ -125,7 +125,7 @@ Template for `.planning/codebase/STRUCTURE.md` - captures physical file organiza
 ```
 get-shit-done/
 ├── bin/                # Executable entry points
-├── command/           # Slash command definitions
+├── commands/           # Slash command definitions
 │   └── gsd/           # GSD-specific commands
 ├── get-shit-done/     # Skill resources
 │   ├── references/    # Principle documents
@@ -145,7 +145,7 @@ get-shit-done/
 - Key files: install.js - handles npx installation
 - Subdirectories: None
 
-**command/gsd/**
+**commands/gsd/**
 - Purpose: Slash command definitions for OpenCode
 - Contains: *.md files (one per command)
 - Key files: new-project.md, plan-phase.md, execute-plan.md
@@ -197,7 +197,7 @@ get-shit-done/
 
 **Directories:**
 - kebab-case: All directories
-- Plural for collections: templates/, command/, workflows/
+- Plural for collections: templates/, commands/, workflows/
 
 **Special Patterns:**
 - {command-name}.md: Slash command definition
@@ -206,8 +206,8 @@ get-shit-done/
 ## Where to Add New Code
 
 **New Slash Command:**
-- Primary code: `command/gsd/{command-name}.md`
-- Tests: `tests/command/{command-name}.test.js` (if testing implemented)
+- Primary code: `commands/gsd/{command-name}.md`
+- Tests: `tests/commands/{command-name}.test.js` (if testing implemented)
 - Documentation: Update `README.md` with new command
 
 **New Template:**
@@ -220,7 +220,7 @@ get-shit-done/
 
 **New Reference Document:**
 - Implementation: `get-shit-done/references/{name}.md`
-- Usage: Reference from command/workflows as needed
+- Usage: Reference from commands/workflows as needed
 
 **Utilities:**
 - No utilities yet (`install.js` is monolithic)
@@ -233,8 +233,8 @@ get-shit-done/
 - Source: Copied by bin/install.js during installation
 - Committed: Yes (source of truth)
 
-**command/**
-- Purpose: Slash commands installed to ~/.config/opencode/command/
+**commands/**
+- Purpose: Slash commands installed to ~/.config/opencode/commands/
 - Source: Copied by bin/install.js during installation
 - Committed: Yes (source of truth)
 

package/get-shit-done/templates/codebase/testing.md

@@ -457,7 +457,7 @@ it('mocks file system', () => {
 **When filling this template:**
 - Check package.json scripts for test commands
 - Find test config file (jest.config.js, vitest.config.ts)
-- Read 3-5 existing test files to identify patterns
+- read 3-5 existing test files to identify patterns
 - Look for test utilities in tests/ or test-utils/
 - Check for coverage configuration
 - Document actual patterns used, not ideal patterns
@@ -471,7 +471,7 @@ it('mocks file system', () => {
 
 **Analysis approach:**
 - Check package.json for test framework and scripts
-- Read test config file for coverage, setup
+- read test config file for coverage, setup
 - Examine test file organization (collocated vs separate)
 - Review 5 test files for patterns (mocking, structure, assertions)
 - Look for test utilities, fixtures, factories