gsd-opencode 1.5.2 → 1.6.0

package/command/gsd/help.md

@@ -21,42 +21,55 @@ Output ONLY the reference content below. Do NOT add:
 
 ## Quick Start
 
-1. `/gsd-new-project` - Initialize project with brief
-2. `/gsd-create-roadmap` - Create roadmap and phases
-3. `/gsd-plan-phase <number>` - Create detailed plan for first phase
-4. `/gsd-execute-plan <path>` - Execute the plan
+1. `/gsd-new-project` - Initialize project (includes research, requirements, roadmap)
+2. `/gsd-plan-phase 1` - Create detailed plan for first phase
+3. `/gsd-execute-phase 1` - Execute the phase
 
-## Core Workflow
+## Staying Updated
+
+GSD evolves fast. Check for updates periodically:
 
 ```
-Initialization → Planning → Execution → Milestone Completion
+/gsd-whats-new
 ```
 
-### Project Initialization
+Shows what changed since your installed version. Update with:
 
-**`/gsd-new-project`**
-Initialize new project with brief and configuration.
+```bash
+npx gsd-opencode@latest
+```
 
-- Creates `.planning/PROJECT.md` (vision and requirements)
-- Creates `.planning/config.json` (workflow mode)
-- Asks for workflow mode (interactive/yolo) upfront
-- Commits initialization files to git
+## Core Workflow
 
-Usage: `/gsd-new-project`
+```
+/gsd-new-project → /gsd-plan-phase → /gsd-execute-phase → repeat
+```
 
-**`/gsd-create-roadmap`**
-Create roadmap and state tracking for initialized project.
+### Project Initialization
 
-- Creates `.planning/ROADMAP.md` (phase breakdown)
-- Creates `.planning/STATE.md` (project memory)
-- Creates `.planning/phases/` directories
+**`/gsd-new-project`**
+Initialize new project through unified flow.
+
+One command takes you from idea to ready-for-planning:
+- Deep questioning to understand what you're building
+- Optional domain research (spawns 4 parallel researcher agents)
+- Requirements definition with v1/v2/out-of-scope scoping
+- Roadmap creation with phase breakdown and success criteria
+
+Creates all `.planning/` artifacts:
+- `PROJECT.md` — vision and requirements
+- `config.json` — workflow mode (interactive/yolo)
+- `research/` — domain research (if selected)
+- `REQUIREMENTS.md` — scoped requirements with REQ-IDs
+- `ROADMAP.md` — phases mapped to requirements
+- `STATE.md` — project memory
 
-Usage: `/gsd-create-roadmap`
+Usage: `/gsd-new-project`
 
 **`/gsd-map-codebase`**
 Map an existing codebase for brownfield projects.
 
-- Analyzes codebase with parallel explore agents
+- Analyzes codebase with parallel Explore agents
 - Creates `.planning/codebase/` with 7 focused documents
 - Covers stack, architecture, structure, conventions, testing, integrations, concerns
 - Use before `/gsd-new-project` on existing codebases
@@ -106,30 +119,16 @@ Result: Creates `.planning/phases/01-foundation/01-01-PLAN.md`
 
 ### Execution
 
-**`/gsd-execute-plan <path>`**
-Execute a single PLAN.md file.
-
-- Runs plan tasks sequentially
-- Creates SUMMARY.md after completion
-- Updates STATE.md with accumulated context
-- Use for interactive execution with checkpoints
-
-Usage: `/gsd-execute-plan .planning/phases/01-foundation/01-01-PLAN.md`
-
 **`/gsd-execute-phase <phase-number>`**
-Execute all unexecuted plans in a phase with parallel agents.
+Execute all plans in a phase.
 
-- Analyzes plan dependencies and spawns independent plans concurrently
-- Use when phase has 2+ plans and you want "walk away" execution
-- Respects max_concurrent_agents from config.json
+- Groups plans by wave (from frontmatter), executes waves sequentially
+- Plans within each wave run in parallel via Task tool
+- Verifies phase goal after all plans complete
+- Updates REQUIREMENTS.md, ROADMAP.md, STATE.md
 
 Usage: `/gsd-execute-phase 5`
 
-Options (via `.planning/config.json` parallelization section):
-- `max_concurrent_agents`: Limit parallel agents (default: 3)
-- `skip_checkpoints`: Skip human checkpoints in background (default: true)
-- `min_plans_for_parallel`: Minimum plans to trigger parallelization (default: 2)
-
 ### Roadmap Management
 
 **`/gsd-add-phase <description>`**
@@ -164,21 +163,15 @@ Result: Phase 17 deleted, phases 18-20 become 17-19
 
 ### Milestone Management
 
-**`/gsd-discuss-milestone`**
-Figure out what you want to build in the next milestone.
-
-- Reviews what shipped in previous milestone
-- Helps you identify features to add, improve, or fix
-- Routes to /gsd-new-milestone when ready
-
-Usage: `/gsd-discuss-milestone`
-
 **`/gsd-new-milestone <name>`**
-Create a new milestone with phases for an existing project.
+Start a new milestone through unified flow.
 
-- Adds milestone section to ROADMAP.md
-- Creates phase directories
-- Updates STATE.md for new milestone
+- Deep questioning to understand what you're building next
+- Optional domain research (spawns 4 parallel researcher agents)
+- Requirements definition with scoping
+- Roadmap creation with phase breakdown
+
+Mirrors `/gsd-new-project` flow for brownfield projects (existing PROJECT.md).
 
 Usage: `/gsd-new-milestone "v2.0 Features"`
 
@@ -226,19 +219,6 @@ Create context handoff when pausing work mid-phase.
 
 Usage: `/gsd-pause-work`
 
-### Issue Management
-
-**`/gsd-consider-issues`**
-Review deferred issues with codebase context.
-
-- Analyzes all open issues against current codebase state
-- Identifies resolved issues (can close)
-- Identifies urgent issues (should address now)
-- Identifies natural fits for upcoming phases
-- Offers batch actions (close, insert phase, note for planning)
-
-Usage: `/gsd-consider-issues`
-
 ### Debugging
 
 **`/gsd-debug [issue description]`**
@@ -284,6 +264,16 @@ Usage: `/gsd-check-todos api`
 **`/gsd-help`**
 Show this command reference.
 
+**`/gsd-whats-new`**
+See what's changed since your installed version.
+
+- Shows installed vs latest version comparison
+- Displays changelog entries for versions you've missed
+- Highlights breaking changes
+- Provides update instructions when behind
+
+Usage: `/gsd-whats-new`
+
 ## Files & Structure
 
 ```
@@ -291,7 +281,6 @@ Show this command reference.
 ├── PROJECT.md            # Project vision
 ├── ROADMAP.md            # Current phase breakdown
 ├── STATE.md              # Project memory & context
-├── ISSUES.md             # Deferred enhancements (created when needed)
 ├── config.json           # Workflow mode & gates
 ├── todos/                # Captured ideas and tasks
 │   ├── pending/          # Todos waiting to be worked on
@@ -338,10 +327,11 @@ Change anytime by editing `.planning/config.json`
 **Starting a new project:**
 
 ```
-/gsd-new-project
-/gsd-create-roadmap
-/gsd-plan-phase 1
-/gsd-execute-plan .planning/phases/01-foundation/01-01-PLAN.md
+/gsd-new-project        # Unified flow: questioning → research → requirements → roadmap
+/new
+/gsd-plan-phase 1       # Create plans for first phase
+/new
+/gsd-execute-phase 1    # Execute all plans in phase
 ```
 
 **Resuming work after a break:**
@@ -355,14 +345,15 @@ Change anytime by editing `.planning/config.json`
 ```
 /gsd-insert-phase 5 "Critical security fix"
 /gsd-plan-phase 5.1
-/gsd-execute-plan .planning/phases/05.1-critical-security-fix/05.1-01-PLAN.md
+/gsd-execute-phase 5.1
 ```
 
 **Completing a milestone:**
 
 ```
 /gsd-complete-milestone 1.0.0
-/gsd-new-project  # Start next milestone
+/new
+/gsd-new-milestone  # Start next milestone (questioning → research → requirements → roadmap)
 ```
 
 **Capturing ideas during work:**
@@ -385,8 +376,8 @@ Change anytime by editing `.planning/config.json`
 
 ## Getting Help
 
-- Read `.planning/PROJECT.md` for project vision
-- Read `.planning/STATE.md` for current context
+- read `.planning/PROJECT.md` for project vision
+- read `.planning/STATE.md` for current context
 - Check `.planning/ROADMAP.md` for phase status
 - Run `/gsd-progress` to check where you're up to
   </reference>

package/command/gsd/insert-phase.md

@@ -2,7 +2,7 @@
 name: gsd-insert-phase
 description: Insert urgent work as decimal phase (e.g., 72.1) between existing phases
 argument-hint: <after> <description>
-allowed-tools:
+tools:
   - read
   - write
   - bash
@@ -25,8 +25,8 @@ Purpose: Handle urgent work discovered during execution without renumbering enti
 
 <step name="parse_arguments">
 Parse the command arguments:
-- First argument ($1): integer phase number to insert after 
-- Remaining arguments ($2 $3 $4 $5 $6 $7 $8 $9 $10 $11 $12 ...): phase description
+- First argument: integer phase number to insert after
+- Remaining arguments: phase description
 
 Example: `/gsd-insert-phase 72 Fix critical auth bug`
 → after = 72
@@ -71,7 +71,7 @@ else
 fi
 ```
 
-Read roadmap content for parsing.
+read roadmap content for parsing.
 </step>
 
 <step name="verify_target_phase">
@@ -149,7 +149,7 @@ Insert the new phase entry into the roadmap:
    [To be added during planning]
    ```
 
-3. Write updated roadmap back to file
+3. write updated roadmap back to file
 
 The "(INSERTED)" marker helps identify decimal phases as urgent insertions.
 
@@ -159,7 +159,7 @@ Preserve all other content exactly (formatting, spacing, other phases).
 <step name="update_project_state">
 Update STATE.md to reflect the inserted phase:
 
-1. Read `.planning/STATE.md`
+1. read `.planning/STATE.md`
 2. Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
    ```
    - Phase {decimal_phase} inserted after Phase {after_phase}: {description} (URGENT)

package/command/gsd/list-phase-assumptions.md

@@ -2,7 +2,7 @@
 name: gsd-list-phase-assumptions
 description: Surface OpenCode's assumptions about a phase approach before planning
 argument-hint: "[phase]"
-allowed-tools:
+tools:
   - read
   - bash
   - grep

package/command/gsd/map-codebase.md

@@ -1,33 +1,26 @@
 ---
 name: gsd-map-codebase
-description: Analyze codebase with parallel explore agents to produce .planning/codebase/ documents
+description: Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
 argument-hint: "[optional: specific area to map, e.g., 'api' or 'auth']"
-allowed-tools:
+tools:
   - read
   - bash
   - glob
   - grep
   - write
-  - task
+
 ---
 
 <objective>
-Analyze existing codebase using parallel explore agents to produce structured codebase documents.
+Analyze existing codebase using parallel gsd-codebase-mapper agents to produce structured codebase documents.
 
-This command spawns multiple explore agents to analyze different aspects of the codebase in parallel, each with fresh context.
+Each mapper agent explores a focus area and **writes documents directly** to `.planning/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.
 
 Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
 </objective>
 
 <execution_context>
 @~/.config/opencode/get-shit-done/workflows/map-codebase.md
-@~/.config/opencode/get-shit-done/templates/codebase/stack.md
-@~/.config/opencode/get-shit-done/templates/codebase/architecture.md
-@~/.config/opencode/get-shit-done/templates/codebase/structure.md
-@~/.config/opencode/get-shit-done/templates/codebase/conventions.md
-@~/.config/opencode/get-shit-done/templates/codebase/testing.md
-@~/.config/opencode/get-shit-done/templates/codebase/integrations.md
-@~/.config/opencode/get-shit-done/templates/codebase/concerns.md
 </execution_context>
 
 <context>
@@ -58,26 +51,20 @@ Check for .planning/STATE.md - loads context if project already initialized
 <process>
 1. Check if .planning/codebase/ already exists (offer to refresh or skip)
 2. Create .planning/codebase/ directory structure
-3. Spawn 4 parallel explore agents to analyze codebase:
-   - Agent 1: Stack + Integrations (technology focus)
-   - Agent 2: Architecture + Structure (organization focus)
-   - Agent 3: Conventions + Testing (quality focus)
-   - Agent 4: Concerns (issues focus)
-4. Wait for all agents to complete, collect findings
-5. Write 7 codebase documents using templates:
-   - STACK.md - Languages, frameworks, key dependencies
-   - ARCHITECTURE.md - System design, patterns, data flow
-   - STRUCTURE.md - Directory layout, module organization
-   - CONVENTIONS.md - Code style, naming, patterns
-   - TESTING.md - Test structure, coverage, practices
-   - INTEGRATIONS.md - APIs, databases, external services
-   - CONCERNS.md - Technical debt, risks, issues
-6. Offer next steps (typically: /gsd-new-project or /gsd-plan-phase)
+3. Spawn 4 parallel gsd-codebase-mapper agents:
+   - Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md
+   - Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md
+   - Agent 3: quality focus → writes CONVENTIONS.md, TESTING.md
+   - Agent 4: concerns focus → writes CONCERNS.md
+4. Wait for agents to complete, collect confirmations (NOT document contents)
+5. Verify all 7 documents exist with line counts
+6. Commit codebase map
+7. Offer next steps (typically: /gsd-new-project or /gsd-plan-phase)
 </process>
 
 <success_criteria>
 - [ ] .planning/codebase/ directory created
-- [ ] All 7 codebase documents written
+- [ ] All 7 codebase documents written by mapper agents
 - [ ] Documents follow template structure
 - [ ] Parallel agents completed without errors
 - [ ] User knows next steps