gsd-opencode 1.5.2 → 1.6.1

package/bin/install.js

@@ -20,7 +20,7 @@ const pkg = require("../package.json");
 const banner = `
 ${cyan}   ██████╗ ███████╗██████╗
   ██╔════╝ ██╔════╝██╔══██╗
-  ██║  ███╗█████╗  ██║  ██║
+  ██║  ███╗███████╗██║  ██║
   ██║   ██║╚════██║██║  ██║
   ╚██████╔╝███████║██████╔╝
    ╚═════╝ ╚══════╝╚═════╝${reset}
@@ -176,12 +176,22 @@ function install(isGlobal) {
   copyWithPathReplacement(gsdSrc, gsdDest, pathPrefix);
   console.log(`  ${green}✓${reset} Installed command/gsd`);
 
+  // Copy agents  with path replacement
+  const agentsSrc = path.join(src, "agents");
+  const agentsDest = path.join(opencodeDir, "agents");
+  copyWithPathReplacement(agentsSrc, agentsDest, pathPrefix);
+  console.log(`  ${green}✓${reset} Installed agents`);
+
   // Copy get-shit-done skill with path replacement
   const skillSrc = path.join(src, "get-shit-done");
   const skillDest = path.join(opencodeDir, "get-shit-done");
   copyWithPathReplacement(skillSrc, skillDest, pathPrefix);
   console.log(`  ${green}✓${reset} Installed get-shit-done`);
 
+  // Create VERSION file
+  fs.writeFileSync(path.join(skillDest, "VERSION"), `v${pkg.version}`);
+  console.log(`  ${green}✓${reset} Created VERSION file`);
+
   console.log(`
   ${green}Done!${reset} Run ${cyan}/gsd-help${reset} to get started.
   `);

package/command/gsd/add-phase.md

@@ -2,7 +2,7 @@
 name: gsd-add-phase
 description: Add phase to end of current milestone in roadmap
 argument-hint: <description>
-allowed-tools:
+tools:
   - read
   - write
   - bash
@@ -19,15 +19,13 @@ Purpose: Add planned work discovered during execution that belongs at the end of
 <execution_context>
 @.planning/ROADMAP.md
 @.planning/STATE.md
-
-Phase description: $ARGUMENTS
 </execution_context>
 
 <process>
 
 <step name="parse_arguments">
 Parse the command arguments:
-- All arguments `$ARGUMENTS` become the phase description
+- $ARGUMENTS 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"
 
@@ -54,7 +52,7 @@ else
 fi
 ```
 
-Read roadmap content for parsing.
+read roadmap content for parsing.
 </step>
 
 <step name="find_current_milestone">
@@ -136,7 +134,7 @@ Add the new phase entry to the roadmap:
    [To be added during planning]
    ```
 
-3. Write updated roadmap back to file
+3. write updated roadmap back to file
 
 Preserve all other content exactly (formatting, spacing, other phases).
 </step>
@@ -144,7 +142,7 @@ Preserve all other content exactly (formatting, spacing, other phases).
 <step name="update_project_state">
 Update STATE.md to reflect the new phase:
 
-1. Read `.planning/STATE.md`
+1. read `.planning/STATE.md`
 2. Under "## Current Position" → "**Next Phase:**" add reference to new phase
 3. Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
    ```

package/command/gsd/add-todo.md

@@ -2,7 +2,7 @@
 name: gsd-add-todo
 description: Capture idea or task as todo from current conversation context
 argument-hint: [optional description]
-allowed-tools:
+tools:
   - read
   - write
   - bash
@@ -17,8 +17,6 @@ Enables "thought → capture → continue" flow without losing context or derail
 
 <context>
 @.planning/STATE.md
-
-Todo title: $ARGUMENTS
 </context>
 
 <process>
@@ -38,7 +36,7 @@ Note existing areas for consistency in infer_area step.
 </step>
 
 <step name="extract_content">
-**With arguments:** Use `$ARGUMENTS` as the title/focus.
+**With arguments:** Use as the title/focus.
 - `/gsd-add-todo Add auth token refresh` → title = "Add auth token refresh"
 
 **Without arguments:** Analyze recent conversation to extract:
@@ -77,7 +75,7 @@ grep -l -i "[key words from title]" .planning/todos/pending/*.md 2>/dev/null
 ```
 
 If potential duplicate found:
-1. Read the existing todo
+1. read the existing todo
 2. Compare scope
 
 If overlapping, use question:
@@ -97,7 +95,7 @@ date_prefix=$(date "+%Y-%m-%d")
 
 Generate slug from title (lowercase, hyphens, no special chars).
 
-Write to `.planning/todos/pending/${date_prefix}-${slug}.md`:
+write to `.planning/todos/pending/${date_prefix}-${slug}.md`:
 
 ```markdown
 ---

package/command/gsd/audit-milestone.md

@@ -0,0 +1,257 @@
+---
+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)
+
+**Completed Work:**
+glob: .planning/phases/*/*-SUMMARY.md
+glob: .planning/phases/*/*-VERIFICATION.md
+</context>
+
+<process>
+
+## 1. Determine Milestone Scope
+
+```bash
+# Get phases in milestone
+ls -d .planning/phases/*/ | sort -V
+```
+
+- Parse version from arguments or detect current from ROADMAP.md
+- Identify all phase directories in scope
+- Extract milestone definition of done from ROADMAP.md
+- Extract requirements mapped to this milestone from REQUIREMENTS.md
+
+## 2. read All Phase Verifications
+
+For each phase directory, read the VERIFICATION.md:
+
+```bash
+cat .planning/phases/01-*/*-VERIFICATION.md
+cat .planning/phases/02-*/*-VERIFICATION.md
+# etc.
+```
+
+From each VERIFICATION.md, extract:
+- **Status:** passed | gaps_found
+- **Critical gaps:** (if any — these are blockers)
+- **Non-critical gaps:** tech debt, deferred items, warnings
+- **Anti-patterns found:** TODOs, stubs, placeholders
+- **Requirements coverage:** which requirements satisfied/blocked
+
+If a phase is missing VERIFICATION.md, flag it as "unverified phase" — this is a blocker.
+
+## 3. Spawn Integration Checker
+
+With phase context collected:
+
+```
+Task(
+  prompt="Check cross-phase integration and E2E flows.
+
+Phases: {phase_dirs}
+Phase exports: {from SUMMARYs}
+API routes: {routes created}
+
+Verify cross-phase wiring and E2E user flows.",
+  subagent_type="gsd-integration-checker"
+)
+```
+
+## 4. Collect Results
+
+Combine:
+- Phase-level gaps and tech debt (from step 2)
+- Integration checker's report (wiring gaps, broken flows)
+
+## 5. Check Requirements Coverage
+
+For each requirement in REQUIREMENTS.md mapped to this milestone:
+- Find owning phase
+- Check phase verification status
+- Determine: satisfied | partial | unsatisfied
+
+## 6. Aggregate into v{version}-MILESTONE-AUDIT.md
+
+Create `.planning/v{version}-v{version}-MILESTONE-AUDIT.md` with:
+
+```yaml
+---
+milestone: {version}
+audited: {timestamp}
+status: passed | gaps_found | tech_debt
+scores:
+  requirements: N/M
+  phases: N/M
+  integration: N/M
+  flows: N/M
+gaps:  # Critical blockers
+  requirements: [...]
+  integration: [...]
+  flows: [...]
+tech_debt:  # Non-critical, deferred
+  - phase: 01-auth
+    items:
+      - "TODO: add rate limiting"
+      - "Warning: no password strength validation"
+  - phase: 03-dashboard
+    items:
+      - "Deferred: mobile responsive layout"
+---
+```
+
+Plus full markdown report with tables for requirements, phases, integration, tech debt.
+
+**Status values:**
+- `passed` — all requirements met, no critical gaps, minimal tech debt
+- `gaps_found` — critical blockers exist
+- `tech_debt` — no blockers but accumulated deferred items need review
+
+## 7. Present Results
+
+Route by status (see `<offer_next>`).
+
+</process>
+
+<offer_next>
+Output this markdown directly (not as a code block). Route based on status:
+
+---
+
+**If passed:**
+
+## ✓ Milestone {version} — Audit Passed
+
+**Score:** {N}/{M} requirements satisfied
+**Report:** .planning/v{version}-MILESTONE-AUDIT.md
+
+All requirements covered. Cross-phase integration verified. E2E flows complete.
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Complete milestone** — archive and tag
+
+/gsd-complete-milestone {version}
+
+*/new first → fresh context window*
+
+───────────────────────────────────────────────────────────────
+
+---
+
+**If gaps_found:**
+
+## ⚠ Milestone {version} — Gaps Found
+
+**Score:** {N}/{M} requirements satisfied
+**Report:** .planning/v{version}-MILESTONE-AUDIT.md
+
+### Unsatisfied Requirements
+
+{For each unsatisfied requirement:}
+- **{REQ-ID}: {description}** (Phase {X})
+  - {reason}
+
+### Cross-Phase Issues
+
+{For each integration gap:}
+- **{from} → {to}:** {issue}
+
+### Broken Flows
+
+{For each flow gap:}
+- **{flow name}:** breaks at {step}
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Plan gap closure** — create phases to complete milestone
+
+/gsd-plan-milestone-gaps
+
+*/new first → fresh context window*
+
+───────────────────────────────────────────────────────────────
+
+**Also available:**
+- cat .planning/v{version}-MILESTONE-AUDIT.md — see full report
+- /gsd-complete-milestone {version} — proceed anyway (accept tech debt)
+
+───────────────────────────────────────────────────────────────
+
+---
+
+**If tech_debt (no blockers but accumulated debt):**
+
+## ⚡ Milestone {version} — Tech Debt Review
+
+**Score:** {N}/{M} requirements satisfied
+**Report:** .planning/v{version}-MILESTONE-AUDIT.md
+
+All requirements met. No critical blockers. Accumulated tech debt needs review.
+
+### Tech Debt by Phase
+
+{For each phase with debt:}
+**Phase {X}: {name}**
+- {item 1}
+- {item 2}
+
+### Total: {N} items across {M} phases
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Options
+
+**A. Complete milestone** — accept debt, track in backlog
+
+/gsd-complete-milestone {version}
+
+**B. Plan cleanup phase** — address debt before completing
+
+/gsd-plan-milestone-gaps
+
+*/new first → fresh context window*
+
+───────────────────────────────────────────────────────────────
+</offer_next>
+
+<success_criteria>
+- [ ] Milestone scope identified
+- [ ] All phase VERIFICATION.md files read
+- [ ] Tech debt and deferred gaps aggregated
+- [ ] Integration checker spawned for cross-phase wiring
+- [ ] v{version}-MILESTONE-AUDIT.md created
+- [ ] Results presented with actionable next steps
+</success_criteria>

package/command/gsd/check-todos.md

@@ -2,7 +2,7 @@
 name: gsd-check-todos
 description: List pending todos and select one to work on
 argument-hint: [area filter]
-allowed-tools:
+tools:
   - read
   - write
   - bash
@@ -19,8 +19,6 @@ Enables reviewing captured ideas and deciding what to work on next.
 <context>
 @.planning/STATE.md
 @.planning/ROADMAP.md
-
-Area filter: $ARGUMENTS
 </context>
 
 <process>
@@ -91,7 +89,7 @@ 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:
+read the todo file completely. Display:
 
 ```
 ## [title]

package/command/gsd/complete-milestone.md

@@ -3,17 +3,17 @@ type: prompt
 name: gsd-complete-milestone
 description: Archive completed milestone and prepare for next version
 argument-hint: <version>
-allowed-tools:
+tools:
   - read
   - write
   - bash
 ---
 
 <objective>
-Mark milestone $ARGUMENTS complete, archive to milestones/, and update ROADMAP.md.
+Mark milestone {{version}} complete, archive to milestones/, and update ROADMAP.md and REQUIREMENTS.md.
 
-Purpose: Create historical record of shipped version, collapse completed work in roadmap, and prepare for next milestone.
-Output: Milestone archived, roadmap reorganized, git tagged.
+Purpose: Create historical record of shipped version, archive milestone artifacts (roadmap + requirements), and prepare for next milestone.
+Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tagged.
 </objective>
 
 <execution_context>
@@ -26,18 +26,41 @@ Output: Milestone archived, roadmap reorganized, git tagged.
 <context>
 **Project files:**
 - `.planning/ROADMAP.md`
+- `.planning/REQUIREMENTS.md`
 - `.planning/STATE.md`
 - `.planning/PROJECT.md`
 
 **User input:**
 
-- Version: $ARGUMENTS (e.g., "1.0", "1.1", "2.0")
+- Version: {{version}} (e.g., "1.0", "1.1", "2.0")
   </context>
 
 <process>
 
 **Follow complete-milestone.md workflow:**
 
+0. **Check for audit:**
+
+   - Look for `.planning/v{{version}}-MILESTONE-AUDIT.md`
+   - If missing or stale: recommend `/gsd-audit-milestone` first
+   - If audit status is `gaps_found`: recommend `/gsd-plan-milestone-gaps` first
+   - If audit status is `passed`: proceed to step 1
+
+   ```markdown
+   ## Pre-flight Check
+
+   {If no v{{version}}-MILESTONE-AUDIT.md:}
+   ⚠ No milestone audit found. Run `/gsd-audit-milestone` first to verify
+   requirements coverage, cross-phase integration, and E2E flows.
+
+   {If audit has gaps:}
+   ⚠ Milestone audit found gaps. Run `/gsd-plan-milestone-gaps` to create
+   phases that close the gaps, or proceed anyway to accept as tech debt.
+
+   {If audit passed:}
+   ✓ Milestone audit passed. Proceeding with completion.
+   ```
+
 1. **Verify readiness:**
 
    - Check all phases in milestone have completed plans (SUMMARY.md exists)
@@ -53,54 +76,61 @@ Output: Milestone archived, roadmap reorganized, git tagged.
 
 3. **Extract accomplishments:**
 
-   - Read all phase SUMMARY.md files in milestone range
+   - read all phase SUMMARY.md files in milestone range
    - Extract 4-6 key accomplishments
    - Present for approval
 
 4. **Archive milestone:**
 
-   - Create `.planning/milestones/v$ARGUMENTS-ROADMAP.md`
+   - Create `.planning/milestones/v{{version}}-ROADMAP.md`
    - Extract full phase details from ROADMAP.md
    - Fill milestone-archive.md template
    - Update ROADMAP.md to one-line summary with link
-   - Offer to create next milestone
 
-5. **Update PROJECT.md:**
+5. **Archive requirements:**
+
+   - Create `.planning/milestones/v{{version}}-REQUIREMENTS.md`
+   - Mark all v1 requirements as complete (checkboxes checked)
+   - Note requirement outcomes (validated, adjusted, dropped)
+   - Delete `.planning/REQUIREMENTS.md` (fresh one created for next milestone)
+
+6. **Update PROJECT.md:**
 
    - Add "Current State" section with shipped version
    - Add "Next Milestone Goals" section
    - Archive previous content in `<details>` (if v1.1+)
 
-6. **Commit and tag:**
+7. **Commit and tag:**
 
-   - Stage: MILESTONES.md, PROJECT.md, ROADMAP.md, STATE.md, archive file
-   - Commit: `chore: archive v$ARGUMENTS milestone`
-   - Tag: `git tag -a v$ARGUMENTS -m "[milestone summary]"`
+   - Stage: MILESTONES.md, PROJECT.md, ROADMAP.md, STATE.md, archive files
+   - Commit: `chore: archive v{{version}} milestone`
+   - Tag: `git tag -a v{{version}} -m "[milestone summary]"`
    - Ask about pushing tag
 
-7. **Offer next steps:**
-   - Plan next milestone
-   - Archive planning
-   - Done for now
+8. **Offer next steps:**
+   - `/gsd-new-milestone` — start next milestone (questioning → research → requirements → roadmap)
 
 </process>
 
 <success_criteria>
 
-- Milestone archived to `.planning/milestones/v$ARGUMENTS-ROADMAP.md`
+- Milestone archived to `.planning/milestones/v{{version}}-ROADMAP.md`
+- Requirements archived to `.planning/milestones/v{{version}}-REQUIREMENTS.md`
+- `.planning/REQUIREMENTS.md` deleted (fresh for next milestone)
 - ROADMAP.md collapsed to one-line entry
 - PROJECT.md updated with current state
-- Git tag v$ARGUMENTS created
+- Git tag v{{version}} created
 - Commit successful
-- User knows next steps
+- User knows next steps (including need for fresh requirements)
   </success_criteria>
 
 <critical_rules>
 
-- **Load workflow first:** Read complete-milestone.md before executing
+- **Load workflow first:** read complete-milestone.md before executing
 - **Verify completion:** All phases must have SUMMARY.md files
 - **User confirmation:** Wait for approval at verification gates
-- **Archive before collapsing:** Always create archive file before updating ROADMAP.md
+- **Archive before deleting:** Always create archive files before updating/deleting originals
 - **One-line summary:** Collapsed milestone in ROADMAP.md should be single line with link
-- **Context efficiency:** Archive keeps ROADMAP.md constant size
+- **Context efficiency:** Archive keeps ROADMAP.md and REQUIREMENTS.md constant size per milestone
+- **Fresh requirements:** Next milestone starts with `/gsd-new-milestone` which includes requirements definition
   </critical_rules>