gsd-opencode 1.22.0 → 1.30.0

package/get-shit-done/templates/user-profile.md

@@ -0,0 +1,146 @@
+# Developer Profile
+
+> This profile was generated from session analysis. It contains behavioral directives
+> for OpenCode to follow when working with this developer. HIGH confidence dimensions
+> should be acted on directly. LOW confidence dimensions should be approached with
+> hedging ("Based on your profile, I'll try X -- let me know if that's off").
+
+**Generated:** {{generated_at}}
+**Source:** {{data_source}}
+**Projects Analyzed:** {{projects_list}}
+**Messages Analyzed:** {{message_count}}
+
+---
+
+## Quick Reference
+
+{{summary_instructions}}
+
+---
+
+## Communication Style
+
+**Rating:** {{communication_style.rating}} | **Confidence:** {{communication_style.confidence}}
+
+**Directive:** {{communication_style.claude_instruction}}
+
+{{communication_style.summary}}
+
+**Evidence:**
+
+{{communication_style.evidence}}
+
+---
+
+## Decision Speed
+
+**Rating:** {{decision_speed.rating}} | **Confidence:** {{decision_speed.confidence}}
+
+**Directive:** {{decision_speed.claude_instruction}}
+
+{{decision_speed.summary}}
+
+**Evidence:**
+
+{{decision_speed.evidence}}
+
+---
+
+## Explanation Depth
+
+**Rating:** {{explanation_depth.rating}} | **Confidence:** {{explanation_depth.confidence}}
+
+**Directive:** {{explanation_depth.claude_instruction}}
+
+{{explanation_depth.summary}}
+
+**Evidence:**
+
+{{explanation_depth.evidence}}
+
+---
+
+## Debugging Approach
+
+**Rating:** {{debugging_approach.rating}} | **Confidence:** {{debugging_approach.confidence}}
+
+**Directive:** {{debugging_approach.claude_instruction}}
+
+{{debugging_approach.summary}}
+
+**Evidence:**
+
+{{debugging_approach.evidence}}
+
+---
+
+## UX Philosophy
+
+**Rating:** {{ux_philosophy.rating}} | **Confidence:** {{ux_philosophy.confidence}}
+
+**Directive:** {{ux_philosophy.claude_instruction}}
+
+{{ux_philosophy.summary}}
+
+**Evidence:**
+
+{{ux_philosophy.evidence}}
+
+---
+
+## Vendor Philosophy
+
+**Rating:** {{vendor_philosophy.rating}} | **Confidence:** {{vendor_philosophy.confidence}}
+
+**Directive:** {{vendor_philosophy.claude_instruction}}
+
+{{vendor_philosophy.summary}}
+
+**Evidence:**
+
+{{vendor_philosophy.evidence}}
+
+---
+
+## Frustration Triggers
+
+**Rating:** {{frustration_triggers.rating}} | **Confidence:** {{frustration_triggers.confidence}}
+
+**Directive:** {{frustration_triggers.claude_instruction}}
+
+{{frustration_triggers.summary}}
+
+**Evidence:**
+
+{{frustration_triggers.evidence}}
+
+---
+
+## Learning Style
+
+**Rating:** {{learning_style.rating}} | **Confidence:** {{learning_style.confidence}}
+
+**Directive:** {{learning_style.claude_instruction}}
+
+{{learning_style.summary}}
+
+**Evidence:**
+
+{{learning_style.evidence}}
+
+---
+
+## Profile Metadata
+
+| Field | Value |
+|-------|-------|
+| Profile Version | {{profile_version}} |
+| Generated | {{generated_at}} |
+| Source | {{data_source}} |
+| Projects | {{projects_count}} |
+| Messages | {{message_count}} |
+| Dimensions Scored | {{dimensions_scored}}/8 |
+| High Confidence | {{high_confidence_count}} |
+| Medium Confidence | {{medium_confidence_count}} |
+| Low Confidence | {{low_confidence_count}} |
+| Sensitive Content Excluded | {{sensitive_excluded_summary}} |

package/get-shit-done/workflows/add-phase.md

@@ -1,6 +1,6 @@
-<purpose>
+<objective>
 Add a new integer phase to the end of the current milestone in the roadmap. Automatically calculates next phase number, creates phase directory, and updates roadmap structure.
-</purpose>
+</objective>
 
 <required_reading>
 read all files referenced by the invoking prompt's execution_context before starting.

package/get-shit-done/workflows/add-tests.md

@@ -1,8 +1,8 @@
-<purpose>
+<objective>
 Generate unit and E2E tests for a completed phase based on its SUMMARY.md, CONTEXT.md, and implementation. Classifies each changed file into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
 
 Users currently hand-craft `/gsd-quick` prompts for test generation after each phase. This workflow standardizes the process with proper classification, quality gates, and gap reporting.
-</purpose>
+</objective>
 
 <required_reading>
 read all files referenced by the invoking prompt's execution_context before starting.
@@ -146,7 +146,7 @@ find . -type d -name "*test*" -o -name "*spec*" -o -name "*__tests__*" 2>/dev/nu
 # Find existing test files for convention matching
 find . -type f \( -name "*.test.*" -o -name "*.spec.*" -o -name "*Tests.fs" -o -name "*Test.fs" \) 2>/dev/null | head -20
 # Check for test runners
-ls package.json *.sln 2>/dev/null
+ls package.json *.sln 2>/dev/null || true
 ```
 
 Identify:
@@ -243,7 +243,7 @@ For each approved E2E test:
 
 1. **Check for existing tests** covering the same scenario:
    ```bash
-   grep -r "{scenario keyword}" {e2e test directory} 2>/dev/null
+   grep -r "{scenario keyword}" {e2e test directory} 2>/dev/null || true
    ```
    If found, extend rather than duplicate.
 

package/get-shit-done/workflows/add-todo.md

@@ -1,6 +1,6 @@
-<purpose>
+<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.
-</purpose>
+</objective>
 
 <required_reading>
 read all files referenced by the invoking prompt's execution_context before starting.
@@ -63,7 +63,7 @@ Use existing area from step 2 if similar match exists.
 <step name="check_duplicates">
 ```bash
 # Search for key words from title in existing todos
-grep -l -i "[key words from title]" .planning/todos/pending/*.md 2>/dev/null
+grep -l -i "[key words from title]" .planning/todos/pending/*.md 2>/dev/null || true
 ```
 
 If potential duplicate found:

package/get-shit-done/workflows/audit-milestone.md

@@ -1,11 +1,16 @@
-<purpose>
+<objective>
 Verify milestone achieved its definition of done by aggregating phase verifications, checking cross-phase integration, and assessing requirements coverage. Reads existing VERIFICATION.md files (phases already verified during execute-phase), aggregates tech debt and deferred gaps, then spawns integration checker for cross-phase wiring.
-</purpose>
+</objective>
 
 <required_reading>
 read all files referenced by the invoking prompt's execution_context before starting.
 </required_reading>
 
+<available_agent_types>
+Valid GSD subagent types (use exact names — do not fall back to 'general'):
+- gsd-integration-checker — Checks cross-phase integration
+</available_agent_types>
+
 <process>
 
 ## 0. Initialize Milestone Context
@@ -13,6 +18,7 @@ read all files referenced by the invoking prompt's execution_context before star
 ```bash
 INIT=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" init milestone-op)
 if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
+AGENT_SKILLS_CHECKER=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" agent-skills gsd-integration-checker 2>/dev/null)
 ```
 
 Extract from init JSON: `milestone_version`, `milestone_name`, `phase_count`, `completed_phases`, `commit_docs`.
@@ -73,7 +79,8 @@ Milestone Requirements:
 
 MUST map each integration finding to affected requirement IDs where applicable.
 
-Verify cross-phase wiring and E2E user flows.",
+Verify cross-phase wiring and E2E user flows.
+${AGENT_SKILLS_CHECKER}",
   subagent_type="gsd-integration-checker",
   model="{integration_checker_model}"
 )
@@ -105,7 +112,8 @@ For each phase's VERIFICATION.md, extract the expanded requirements table:
 For each phase's SUMMARY.md, extract `requirements-completed` from YAML frontmatter:
 ```bash
 for summary in .planning/phases/*-*/*-SUMMARY.md; do
-  node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" summary-extract "$summary" --fields requirements_completed | jq -r '.requirements_completed'
+  [ -e "$summary" ] || continue
+  node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" summary-extract "$summary" --fields requirements_completed --pick requirements_completed
 done
 ```
 
@@ -133,7 +141,7 @@ For each REQ-ID, determine status using all three sources:
 Skip if `workflow.nyquist_validation` is explicitly `false` (absent = enabled).
 
 ```bash
-NYQUIST_CONFIG=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" config get workflow.nyquist_validation --raw 2>/dev/null)
+NYQUIST_CONFIG=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" config-get workflow.nyquist_validation --raw 2>/dev/null)
 ```
 
 If `false`: skip entirely.

package/get-shit-done/workflows/audit-uat.md

@@ -0,0 +1,109 @@
+<objective>
+Cross-phase audit of all UAT and verification files. Finds every outstanding item (pending, skipped, blocked, human_needed), optionally verifies against the codebase to detect stale docs, and produces a prioritized human test plan.
+</objective>
+
+<process>
+
+<step name="initialize">
+Run the CLI audit:
+
+```bash
+AUDIT=$(node "$HOME/.config/opencode/get-shit-done/bin/gsd-tools.cjs" audit-uat --raw)
+```
+
+Parse JSON for `results` array and `summary` object.
+
+If `summary.total_items` is 0:
+```
+## All Clear
+
+No outstanding UAT or verification items found across all phases.
+All tests are passing, resolved, or diagnosed with fix plans.
+```
+Stop here.
+</step>
+
+<step name="categorize">
+Group items by what's actionable NOW vs. what needs prerequisites:
+
+**Testable Now** (no external dependencies):
+- `pending` — tests never run
+- `human_uat` — human verification items
+- `skipped_unresolved` — skipped without clear blocking reason
+
+**Needs Prerequisites:**
+- `server_blocked` — needs external server running
+- `device_needed` — needs physical device (not simulator)
+- `build_needed` — needs release/preview build
+- `third_party` — needs external service configuration
+
+For each item in "Testable Now", use grep/read to check if the underlying feature still exists in the codebase:
+- If the test references a component/function that no longer exists → mark as `stale`
+- If the test references code that has been significantly rewritten → mark as `needs_update`
+- Otherwise → mark as `active`
+</step>
+
+<step name="present">
+Present the audit report:
+
+```
+## UAT Audit Report
+
+**{total_items} outstanding items across {total_files} files in {phase_count} phases**
+
+### Testable Now ({count})
+
+| # | Phase | Test | Description | Status |
+|---|-------|------|-------------|--------|
+| 1 | {phase} | {test_name} | {expected} | {active/stale/needs_update} |
+...
+
+### Needs Prerequisites ({count})
+
+| # | Phase | Test | Blocked By | Description |
+|---|-------|------|------------|-------------|
+| 1 | {phase} | {test_name} | {category} | {expected} |
+...
+
+### Stale (can be closed) ({count})
+
+| # | Phase | Test | Why Stale |
+|---|-------|------|-----------|
+| 1 | {phase} | {test_name} | {reason} |
+...
+
+---
+
+## Recommended Actions
+
+1. **Close stale items:** `/gsd-verify-work {phase}` — mark stale tests as resolved
+2. **Run active tests:** Human UAT test plan below
+3. **When prerequisites met:** Retest blocked items with `/gsd-verify-work {phase}`
+```
+</step>
+
+<step name="test_plan">
+Generate a human UAT test plan for "Testable Now" + "active" items only:
+
+Group by what can be tested together (same screen, same feature, same prerequisite):
+
+```
+## Human UAT Test Plan
+
+### Group 1: {category — e.g., "Billing Flow"}
+Prerequisites: {what needs to be running/configured}
+
+1. **{Test name}** (Phase {N})
+   - Navigate to: {where}
+   - Do: {action}
+   - Expected: {expected behavior}
+
+2. **{Test name}** (Phase {N})
+   ...
+
+### Group 2: {category}
+...
+```
+</step>
+
+</process>