gsd-opencode 1.10.2 → 1.20.1

package/get-shit-done/templates/summary-standard.md

@@ -0,0 +1,48 @@
+---
+phase: XX-name
+plan: YY
+subsystem: [primary category]
+tags: [searchable tech]
+provides:
+  - [bullet list of what was built/delivered]
+affects: [list of phase names or keywords]
+tech-stack:
+  added: [libraries/tools]
+  patterns: [architectural/code patterns]
+key-files:
+  created: [important files created]
+  modified: [important files modified]
+key-decisions:
+  - "Decision 1"
+duration: Xmin
+completed: YYYY-MM-DD
+---
+
+# Phase [X]: [Name] Summary
+
+**[Substantive one-liner describing outcome]**
+
+## Performance
+- **Duration:** [time]
+- **Tasks:** [count completed]
+- **Files modified:** [count]
+
+## Accomplishments
+- [Key outcome 1]
+- [Key outcome 2]
+
+## task Commits
+1. **task 1: [task name]** - `hash`
+2. **task 2: [task name]** - `hash`
+3. **task 3: [task name]** - `hash`
+
+## Files Created/Modified
+- `path/to/file.ts` - What it does
+- `path/to/another.ts` - What it does
+
+## Decisions & Deviations
+[Key decisions or "None - followed plan as specified"]
+[Minor deviations if any, or "None"]
+
+## Next Phase Readiness
+[What's ready for next phase]

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

@@ -38,6 +38,8 @@ patterns-established:
   - "Pattern 1: description"
   - "Pattern 2: description"
 
+requirements-completed: []  # REQUIRED — Copy ALL requirement IDs from this plan's `requirements` frontmatter field.
+
 # Metrics
 duration: Xmin
 completed: YYYY-MM-DD
@@ -60,13 +62,13 @@ completed: YYYY-MM-DD
 - [Second key accomplishment]
 - [Third if applicable]
 
-## Task Commits
+## task Commits
 
 Each task was committed atomically:
 
-1. **Task 1: [task name]** - `abc123f` (feat/fix/test/refactor)
-2. **Task 2: [task name]** - `def456g` (feat/fix/test/refactor)
-3. **Task 3: [task name]** - `hij789k` (feat/fix/test/refactor)
+1. **task 1: [task name]** - `abc123f` (feat/fix/test/refactor)
+2. **task 2: [task name]** - `def456g` (feat/fix/test/refactor)
+3. **task 3: [task name]** - `hij789k` (feat/fix/test/refactor)
 
 **Plan metadata:** `lmn012o` (docs: complete plan)
 
@@ -88,7 +90,7 @@ _Note: TDD tasks may have multiple commits (test → feat → refactor)_
 ### Auto-fixed Issues
 
 **1. [Rule X - Category] Brief description**
-- **Found during:** Task [N] ([task name])
+- **Found during:** task [N] ([task name])
 - **Issue:** [What was wrong]
 - **Fix:** [What was done]
 - **Files modified:** [file paths]
@@ -199,20 +201,20 @@ The one-liner should tell someone what actually shipped.
 ### Auto-fixed Issues
 
 **1. [Rule 2 - Missing Critical] Added password hashing with bcrypt**
-- **Found during:** Task 2 (Login endpoint implementation)
+- **Found during:** task 2 (Login endpoint implementation)
 - **Issue:** Plan didn't specify password hashing - storing plaintext would be critical security flaw
 - **Fix:** Added bcrypt hashing on registration, comparison on login with salt rounds 10
 - **Files modified:** src/app/api/auth/login/route.ts, src/lib/auth.ts
 - **Verification:** Password hash test passes, plaintext never stored
-- **Committed in:** abc123f (Task 2 commit)
+- **Committed in:** abc123f (task 2 commit)
 
 **2. [Rule 3 - Blocking] Installed missing jose dependency**
-- **Found during:** Task 4 (JWT token generation)
+- **Found during:** task 4 (JWT token generation)
 - **Issue:** jose package not in package.json, import failing
 - **Fix:** Ran `npm install jose`
 - **Files modified:** package.json, package-lock.json
 - **Verification:** Import succeeds, build passes
-- **Committed in:** def456g (Task 4 commit)
+- **Committed in:** def456g (task 4 commit)
 
 ---
 
@@ -233,37 +235,14 @@ The one-liner should tell someone what actually shipped.
 </example>
 
 <guidelines>
-**When to create:**
-- After completing each phase plan
-- Required output from execute-plan workflow
-- Documents what actually happened vs what was planned
-
-**Frontmatter completion:**
-- MANDATORY: Complete all frontmatter fields during summary creation
-- See <frontmatter_guidance> for field purposes
-- Frontmatter enables automatic context assembly for future planning
-
-**One-liner requirements:**
-- Must be substantive (describe what shipped, not "phase complete")
-- Should tell someone what was accomplished
-- Examples: "JWT auth with refresh rotation using jose library" not "Authentication implemented"
-
-**Performance tracking:**
-- Include duration, start/end timestamps
-- Used for velocity metrics in STATE.md
-
-**Deviations section:**
-- Documents unplanned work handled via deviation rules
-- Separate from "Issues Encountered" (which is planned work problems)
-- Auto-fixed issues: What was wrong, how fixed, verification
+**Frontmatter:** MANDATORY - complete all fields. Enables automatic context assembly for future planning.
+
+**One-liner:** Must be substantive. "JWT auth with refresh rotation using jose library" not "Authentication implemented".
 
 **Decisions section:**
-- Key decisions made during execution
-- Include rationale (why this choice)
+- Key decisions made during execution with rationale
 - Extracted to STATE.md accumulated context
 - Use "None - followed plan as specified" if no deviations
 
-**After creation:**
-- STATE.md updated with position, decisions, issues
-- Next plan can reference decisions made
+**After creation:** STATE.md updated with position, decisions, issues.
 </guidelines>

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

@@ -304,20 +304,8 @@ curl -X POST http://localhost:3000/api/test-email \
 
 ## Guidelines
 
-**Include in USER-SETUP.md:**
-- Environment variable names and where to find values
-- Account creation URLs (if new service)
-- Dashboard configuration steps
-- Verification commands to confirm setup works
-- Local development alternatives (e.g., `stripe listen`)
-
-**Do NOT include:**
-- Actual secret values (never)
-- Steps OpenCode can automate (package installs, code changes, file creation)
-- Generic instructions ("set up your environment")
+**Never include:** Actual secret values. Steps OpenCode can automate (package installs, code changes).
 
 **Naming:** `{phase}-USER-SETUP.md` matches the phase number pattern.
-
 **Status tracking:** User marks checkboxes and updates status line when complete.
-
 **Searchability:** `grep -r "USER-SETUP" .planning/` finds all phases with user requirements.

package/get-shit-done/templates/verification-report.md

@@ -1,6 +1,6 @@
 # Verification Report Template
 
-Template for `.planning/phases/XX-name/{phase}-VERIFICATION.md` — phase goal verification results.
+Template for `.planning/phases/XX-name/{phase_num}-VERIFICATION.md` — phase goal verification results.
 
 ---
 
@@ -124,8 +124,8 @@ None — all verifiable items checked programmatically.
 **Objective:** {What this fixes}
 
 **Tasks:**
-1. {Task to fix gap 1}
-2. {Task to fix gap 2}
+1. {task to fix gap 1}
+2. {task to fix gap 2}
 3. {Verification task}
 
 **Estimated scope:** {Small / Medium}
@@ -137,8 +137,8 @@ None — all verifiable items checked programmatically.
 **Objective:** {What this fixes}
 
 **Tasks:**
-1. {Task}
-2. {Task}
+1. {task}
+2. {task}
 
 **Estimated scope:** {Small / Medium}
 

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

@@ -0,0 +1,111 @@
+<purpose>
+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>
+
+<required_reading>
+read all files referenced by the invoking prompt's execution_context before starting.
+</required_reading>
+
+<process>
+
+<step name="parse_arguments">
+Parse the command 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"
+
+If no arguments provided:
+
+```
+ERROR: Phase description required
+Usage: /gsd-add-phase <description>
+Example: /gsd-add-phase Add authentication system
+```
+
+Exit.
+</step>
+
+<step name="init_context">
+Load phase operation context:
+
+```bash
+INIT=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs init phase-op "0")
+```
+
+Check `roadmap_exists` from init JSON. If false:
+```
+ERROR: No roadmap found (.planning/ROADMAP.md)
+Run /gsd-new-project to initialize.
+```
+Exit.
+</step>
+
+<step name="add_phase">
+**Delegate the phase addition to gsd-tools:**
+
+```bash
+RESULT=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs phase add "${description}")
+```
+
+The CLI handles:
+- Finding the highest existing integer phase number
+- Calculating next phase number (max + 1)
+- Generating slug from description
+- Creating the phase directory (`.planning/phases/{NN}-{slug}/`)
+- Inserting the phase entry into ROADMAP.md with Goal, Depends on, and Plans sections
+
+Extract from result: `phase_number`, `padded`, `name`, `slug`, `directory`.
+</step>
+
+<step name="update_project_state">
+Update STATE.md to reflect the new phase:
+
+1. read `.planning/STATE.md`
+2. Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
+   ```
+   - Phase {N} added: {description}
+   ```
+
+If "Roadmap Evolution" section doesn't exist, create it.
+</step>
+
+<step name="completion">
+Present completion summary:
+
+```
+Phase {N} added to current milestone:
+- Description: {description}
+- Directory: .planning/phases/{phase-num}-{slug}/
+- Status: Not planned yet
+
+Roadmap updated: .planning/ROADMAP.md
+
+---
+
+## ▶ Next Up
+
+**Phase {N}: {description}**
+
+`/gsd-plan-phase {N}`
+
+*`/new` first → fresh context window*
+
+---
+
+**Also available:**
+- `/gsd-add-phase <description>` — add another phase
+- Review roadmap
+
+---
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] `gsd-tools phase add` executed successfully
+- [ ] Phase directory created
+- [ ] Roadmap updated with new phase entry
+- [ ] STATE.md updated with roadmap evolution note
+- [ ] User informed of next steps
+</success_criteria>

package/{commands/gsd → get-shit-done/workflows}/add-todo.md

@@ -1,38 +1,28 @@
----
-name: gsd-add-todo
-description: Capture idea or task as todo from current conversation context
-argument-hint: [optional description]
-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.
+<purpose>
+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>
 
-Enables "thought → capture → continue" flow without losing context or derailing current work.
-</objective>
-
-<context>
-@.planning/STATE.md
-</context>
+<required_reading>
+read all files referenced by the invoking prompt's execution_context before starting.
+</required_reading>
 
 <process>
 
-<step name="ensure_directory">
+<step name="init_context">
+Load todo context:
+
 ```bash
-mkdir -p .planning/todos/pending .planning/todos/done
+INIT=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs init todos)
 ```
-</step>
 
-<step name="check_existing_areas">
+Extract from init JSON: `commit_docs`, `date`, `timestamp`, `todo_count`, `todos`, `pending_dir`, `todos_dir_exists`.
+
+Ensure directories exist:
 ```bash
-ls .planning/todos/pending/*.md 2>/dev/null | xargs -I {} grep "^area:" {} 2>/dev/null | cut -d' ' -f2 | sort -u
+mkdir -p .planning/todos/pending .planning/todos/done
 ```
 
-Note existing areas for consistency in infer_area step.
+Note existing areas from the todos array for consistency in infer_area step.
 </step>
 
 <step name="extract_content">
@@ -71,6 +61,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
 ```
 
@@ -88,14 +79,14 @@ If overlapping, use question:
 </step>
 
 <step name="create_file">
+Use values from init context: `timestamp` and `date` are already available.
+
+Generate slug for the title:
 ```bash
-timestamp=$(date "+%Y-%m-%dT%H:%M")
-date_prefix=$(date "+%Y-%m-%d")
+slug=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs generate-slug "$title" --raw)
 ```
 
-Generate slug from title (lowercase, hyphens, no special chars).
-
-write to `.planning/todos/pending/${date_prefix}-${slug}.md`:
+write to `.planning/todos/pending/${date}-${slug}.md`:
 
 ```markdown
 ---
@@ -119,34 +110,18 @@ files:
 <step name="update_state">
 If `.planning/STATE.md` exists:
 
-1. Count todos: `ls .planning/todos/pending/*.md 2>/dev/null | wc -l`
+1. Use `todo_count` from init context (or re-run `init todos` if count changed)
 2. Update "### Pending Todos" under "## Accumulated Context"
 </step>
 
 <step name="git_commit">
 Commit the todo and any updated state:
 
-**Check planning config:**
-
 ```bash
-COMMIT_PLANNING_DOCS=$(cat .planning/config.json 2>/dev/null | grep -o '"commit_docs"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
-git check-ignore -q .planning 2>/dev/null && COMMIT_PLANNING_DOCS=false
+node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs commit "docs: capture todo - [title]" --files .planning/todos/pending/[filename] .planning/STATE.md
 ```
 
-**If `COMMIT_PLANNING_DOCS=false`:** Skip git operations, log "Todo saved (not committed - commit_docs: false)"
-
-**If `COMMIT_PLANNING_DOCS=true` (default):**
-
-```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
-)"
-```
+Tool respects `commit_docs` config and gitignore automatically.
 
 Confirm: "Committed: docs: capture todo - [title]"
 </step>
@@ -171,17 +146,6 @@ Would you like to:
 
 </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

package/{commands/gsd → get-shit-done/workflows}/audit-milestone.md

@@ -1,67 +1,31 @@
----
-name: gsd-audit-milestone
-description: Audit milestone completion against original intent before archiving
-argument-hint: "[version]"
-tools:
-  - read
-  - glob
-  - grep
-  - bash
-
-  - write
----
-
-<objective>
-Verify milestone achieved its definition of done. Check requirements coverage, cross-phase integration, and end-to-end flows.
-
-**This command IS the orchestrator.** 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.
-</objective>
-
-<execution_context>
-<!-- Spawns gsd-integration-checker agent which has all audit expertise baked in -->
-</execution_context>
-
-<context>
-Version: `$ARGUMENTS` (optional — defaults to current milestone)
-
-**Original Intent:**
-@.planning/PROJECT.md
-@.planning/REQUIREMENTS.md
-
-**Planned Work:**
-@.planning/ROADMAP.md
-@.planning/config.json (if exists)
+<purpose>
+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>
 
-**Completed Work:**
-glob: .planning/phases/*/*-SUMMARY.md
-glob: .planning/phases/*/*-VERIFICATION.md
-</context>
+<required_reading>
+read all files referenced by the invoking prompt's execution_context before starting.
+</required_reading>
 
 <process>
 
-## 0. Resolve Model Profile
-
-read model profile for agent spawning:
+## 0. Initialize Milestone Context
 
 ```bash
-MODEL_PROFILE=$(cat .planning/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced")
+INIT=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs init milestone-op)
 ```
 
-Default to "balanced" if not set.
-
-**Model lookup table:**
+Extract from init JSON: `milestone_version`, `milestone_name`, `phase_count`, `completed_phases`, `commit_docs`.
 
-| Agent | quality | balanced | budget |
-|-------|---------|----------|--------|
-| gsd-integration-checker | sonnet | sonnet | haiku |
-
-Store resolved model for use in Task call below.
+Resolve integration checker model:
+```bash
+CHECKER_MODEL=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs resolve-model gsd-integration-checker --raw)
+```
 
 ## 1. Determine Milestone Scope
 
 ```bash
-# Get phases in milestone
-ls -d .planning/phases/*/ | sort -V
+# Get phases in milestone (sorted numerically, handles decimals)
+node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs phases list
 ```
 
 - Parse version from arguments or detect current from ROADMAP.md
@@ -74,9 +38,10 @@ ls -d .planning/phases/*/ | sort -V
 For each phase directory, read the VERIFICATION.md:
 
 ```bash
-cat .planning/phases/01-*/*-VERIFICATION.md
-cat .planning/phases/02-*/*-VERIFICATION.md
-# etc.
+# For each phase, use find-phase to resolve the directory (handles archived phases)
+PHASE_INFO=$(node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs find-phase 01 --raw)
+# Extract directory from JSON, then read VERIFICATION.md from that directory
+# Repeat for each phase number from ROADMAP.md
 ```
 
 From each VERIFICATION.md, extract:
@@ -92,14 +57,21 @@ If a phase is missing VERIFICATION.md, flag it as "unverified phase" — this is
 
 With phase context collected:
 
+Extract `MILESTONE_REQ_IDS` from REQUIREMENTS.md traceability table — all REQ-IDs assigned to phases in this milestone.
+
 ```
-Task(
+task(
   prompt="Check cross-phase integration and E2E flows.
 
 Phases: {phase_dirs}
 Phase exports: {from SUMMARYs}
 API routes: {routes created}
 
+Milestone Requirements:
+{MILESTONE_REQ_IDS — list each REQ-ID with description and assigned phase}
+
+MUST map each integration finding to affected requirement IDs where applicable.
+
 Verify cross-phase wiring and E2E user flows.",
   subagent_type="gsd-integration-checker",
   model="{integration_checker_model}"
@@ -112,12 +84,48 @@ Combine:
 - Phase-level gaps and tech debt (from step 2)
 - Integration checker's report (wiring gaps, broken flows)
 
-## 5. Check Requirements Coverage
+## 5. Check Requirements Coverage (3-Source Cross-Reference)
+
+MUST cross-reference three independent sources for each requirement:
+
+### 5a. Parse REQUIREMENTS.md Traceability Table
+
+Extract all REQ-IDs mapped to milestone phases from the traceability table:
+- Requirement ID, description, assigned phase, current status, checked-off state (`[x]` vs `[ ]`)
+
+### 5b. Parse Phase VERIFICATION.md Requirements Tables
+
+For each phase's VERIFICATION.md, extract the expanded requirements table:
+- Requirement | Source Plan | Description | Status | Evidence
+- Map each entry back to its REQ-ID
+
+### 5c. Extract SUMMARY.md Frontmatter Cross-Check
+
+For each phase's SUMMARY.md, extract `requirements-completed` from YAML frontmatter:
+```bash
+for summary in .planning/phases/*-*/*-SUMMARY.md; do
+  node ~/.config/opencode/get-shit-done/bin/gsd-tools.cjs summary-extract "$summary" --fields requirements_completed | jq -r '.requirements_completed'
+done
+```
+
+### 5d. Status Determination Matrix
+
+For each REQ-ID, determine status using all three sources:
+
+| VERIFICATION.md Status | SUMMARY Frontmatter | REQUIREMENTS.md | → Final Status |
+|------------------------|---------------------|-----------------|----------------|
+| passed                 | listed              | `[x]`           | **satisfied**  |
+| passed                 | listed              | `[ ]`           | **satisfied** (update checkbox) |
+| passed                 | missing             | any             | **partial** (verify manually) |
+| gaps_found             | any                 | any             | **unsatisfied** |
+| missing                | listed              | any             | **partial** (verification gap) |
+| missing                | missing             | any             | **unsatisfied** |
+
+### 5e. FAIL Gate and Orphan Detection
+
+**REQUIRED:** Any `unsatisfied` requirement MUST force `gaps_found` status on the milestone audit.
 
-For each requirement in REQUIREMENTS.md mapped to this milestone:
-- Find owning phase
-- Check phase verification status
-- Determine: satisfied | partial | unsatisfied
+**Orphan detection:** Requirements present in REQUIREMENTS.md traceability table but absent from ALL phase VERIFICATION.md files MUST be flagged as orphaned. Orphaned requirements are treated as `unsatisfied` — they were assigned but never verified by any phase.
 
 ## 6. Aggregate into v{version}-MILESTONE-AUDIT.md
 
@@ -134,7 +142,14 @@ scores:
   integration: N/M
   flows: N/M
 gaps:  # Critical blockers
-  requirements: [...]
+  requirements:
+    - id: "{REQ-ID}"
+      status: "unsatisfied | partial | orphaned"
+      phase: "{assigned phase}"
+      claimed_by_plans: ["{plan files that reference this requirement}"]
+      completed_by_plans: ["{plan files whose SUMMARY marks it complete}"]
+      verification_status: "passed | gaps_found | missing | orphaned"
+      evidence: "{specific evidence or lack thereof}"
   integration: [...]
   flows: [...]
 tech_debt:  # Non-critical, deferred
@@ -270,8 +285,13 @@ All requirements met. No critical blockers. Accumulated tech debt needs review.
 <success_criteria>
 - [ ] Milestone scope identified
 - [ ] All phase VERIFICATION.md files read
+- [ ] SUMMARY.md `requirements-completed` frontmatter extracted for each phase
+- [ ] REQUIREMENTS.md traceability table parsed for all milestone REQ-IDs
+- [ ] 3-source cross-reference completed (VERIFICATION + SUMMARY + traceability)
+- [ ] Orphaned requirements detected (in traceability but absent from all VERIFICATIONs)
 - [ ] Tech debt and deferred gaps aggregated
-- [ ] Integration checker spawned for cross-phase wiring
-- [ ] v{version}-MILESTONE-AUDIT.md created
+- [ ] Integration checker spawned with milestone requirement IDs
+- [ ] v{version}-MILESTONE-AUDIT.md created with structured requirement gap objects
+- [ ] FAIL gate enforced — any unsatisfied requirement forces gaps_found status
 - [ ] Results presented with actionable next steps
 </success_criteria>