opencode-goopspec 0.1.4 → 0.1.6

package/commands/goop-setup.md

@@ -3,307 +3,64 @@ name: goop-setup
 description: GoopSpec setup wizard - first-time init, configuration, and verification
 ---
 
-# GoopSpec Setup Wizard
+# /goop-setup
 
-You are helping the user set up or modify their GoopSpec configuration. This wizard handles first-time setup, modifications, and verification.
+**GoopSpec setup wizard.** First-time init, configuration, and verification.
 
-## Available Actions
-
-| Action | Purpose | When to Use |
-|--------|---------|-------------|
-| `init` | Full first-time initialization | New projects, creates all directories and files |
-| `detect` | Show current environment | Understand what's already configured |
-| `plan` | Preview changes | Before applying, see what will change |
-| `apply` | Write configuration | Apply configuration changes |
-| `verify` | Check setup health | Ensure everything is working |
-| `reset` | Reset to defaults | Start over or fix broken config |
-| `models` | Show model suggestions | Help choosing agent models |
-| `status` | Show current config | Quick overview of current state |
-
-## Tools Used
-
-| Tool | Purpose in This Command |
-|------|------------------------|
-| `goop_setup` | Primary tool - all setup actions |
-
-**Hook Support:** None specific - configuration tool.
-
----
-
-## First-Time Setup Flow
-
-For users who haven't set up GoopSpec yet, use the `init` action.
-
-### Step 1: Detect Current State
+## Immediate Action
 
+**STOP. Execute this tool call NOW before reading anything else:**
 ```
-goop_setup(action: "detect")
+goop_setup({ action: "detect" })
 ```
 
-Review what's already configured. If nothing exists, proceed to full init.
-
-### Step 2: Ask for Project Name
-
-Ask the user: "What's your project name?"
-
-This will be stored in the configuration for context.
-
-### Step 3: Configuration Scope
-
-Ask: "Where should GoopSpec be configured?"
-
-Use the question tool:
-- **both** (Recommended) - Both global and project-specific settings
-- **global** - Only system-wide settings
-- **project** - Only this project
-
-### Step 4: MCP Preset
-
-Ask: "Which MCPs should be installed?"
-
-- **recommended** - Context7 + Exa + Playwright (full workflow support)
-- **core** - Context7 + Exa only (minimal)
-- **none** - Skip MCP installation
-
-### Step 5: Memory System
-
-Ask: "Would you like to enable the memory system?"
-
-The memory system allows GoopSpec to remember decisions, patterns, and context across sessions.
-
-If yes, ask about embedding provider:
-- **local** (Recommended) - Uses local embeddings, no API needed
-- **openai** - Uses OpenAI embeddings (requires API key)
-- **ollama** - Uses local Ollama server
+**Then follow the workflow below based on the result.** Do not process user messages until you have run detection.
 
-### Step 6: Model Configuration
-
-Ask: "Would you like to configure models for each agent?"
-
-- **Quick setup** - Use recommended defaults
-- **Custom setup** - Choose models individually
+---
 
-For custom setup, walk through each agent or accept shortcuts like "use Claude Sonnet for everything".
+## Workflow
 
-### Step 7: Apply Init
+### If .goopspec directory NOT found → First-Time Setup
 
-Execute the initialization:
+1. **Ask project name** using `question` tool (allow custom input)
+2. **Ask scope** → "Both (Recommended)", "Project only", or "Global only"
+3. **Ask MCP preset** → "Recommended", "Core", or "None"
+4. **Ask memory** → "Yes, local embeddings (Recommended)", "Yes, OpenAI", "Yes, Ollama", or "No"
+5. **Ask models** → "Use defaults (Recommended)" or "Custom configuration"
 
+Then apply:
 ```
 goop_setup(
   action: "init",
-  scope: "<scope>",
-  projectName: "<name>",
-  mcpPreset: "<preset>",
-  memoryEnabled: true,
-  memoryProvider: "local",
-  agentModels: { ... }
+  scope: "<from step 2: both/project/global>",
+  projectName: "<from step 1>",
+  mcpPreset: "<from step 3: recommended/core/none>",
+  memoryEnabled: <from step 4: true/false>,
+  memoryProvider: "<from step 4: local/openai/ollama>"
 )
 ```
 
-### Step 8: Verify Setup
-
-After init completes, verify everything is working:
-
-```
-goop_setup(action: "verify")
-```
-
-Report any issues and suggest fixes.
-
-## Modifying Existing Setup
-
-For users who already have GoopSpec configured:
-
-### Check Current Status
-
-```
-goop_setup(action: "status")
-```
-
-Shows what's currently configured.
-
-### Update Configuration
-
-```
-goop_setup(
-  action: "apply",
-  scope: "project",
-  // Only include what you want to change
-  memoryEnabled: true,
-  agentModels: {
-    "goop-executor": "anthropic/claude-sonnet-4-5"
-  }
-)
-```
+Finally verify: `goop_setup(action: "verify")`
 
-### Reset Configuration
+### If .goopspec directory FOUND → Ask what to do
 
-If something is broken:
+Use `question` tool:
+- **Header:** "Existing Setup"
+- **Question:** "GoopSpec is already configured. What would you like to do?"
+- **Options:**
+  - "Verify setup" → Run `goop_setup(action: "verify")`
+  - "Modify configuration" → Ask what to change, then `goop_setup(action: "apply", ...)`
+  - "Reset and start fresh" → `goop_setup(action: "reset", scope: "project", preserveData: true, confirmed: true)` then do First-Time Setup
+  - "View current status" → Run `goop_setup(action: "status")`
 
-```
-goop_setup(
-  action: "reset",
-  scope: "project",
-  preserveData: true,  // Keep memories, history, checkpoints
-  confirmed: true
-)
-```
-
-## Agent Model Options
-
-### goop-debugger
-*Systematic debugging with hypothesis testing*
-1. openai/gpt-5.2-codex
-2. anthropic/claude-opus-4-5
-3. kimi-for-coding/k2p5
-
-### goop-designer
-*Visual design planning and UI/UX reasoning*
-1. anthropic/claude-opus-4-5
-2. kimi-for-coding/k2p5
-3. google/antigravity-gemini-3-pro-high
-
-### goop-executor
-*Task execution with checkpoints and verification*
-1. openai/gpt-5.2-codex
-2. anthropic/claude-opus-4-5
-3. anthropic/claude-sonnet-4-5
-4. kimi-for-coding/k2p5
-5. google/antigravity-gemini-3-pro-high
-6. opencode/glm-4.7-free
-
-### goop-explorer
-*Fast codebase exploration and pattern extraction*
-1. google/antigravity-gemini-3-flash
-2. anthropic/claude-haiku-4-5
-3. opencode/minimax-m2.1-free
-
-### goop-librarian
-*Codebase search and documentation retrieval*
-1. openai/gpt-5.2
-2. google/antigravity-gemini-3-flash
-3. anthropic/claude-sonnet-4-5
-
-### goop-orchestrator
-*Primary orchestrator - spec clarity and wave execution*
-1. anthropic/claude-opus-4-5
-2. openai/gpt-5.2-codex
-3. kimi-for-coding/k2p5
-4. anthropic/claude-sonnet-4-5
-
-### goop-planner
-*Detailed execution plans with architectural precision*
-1. anthropic/claude-opus-4-5
-2. openai/gpt-5.2-codex
-3. kimi-for-coding/k2p5
-4. anthropic/claude-sonnet-4-5
-
-### goop-researcher
-*Comprehensive ecosystem research*
-1. openai/gpt-5.2
-2. anthropic/claude-sonnet-4-5
-3. kimi-for-coding/k2p5
-4. opencode/glm-4.7-free
-
-### goop-tester
-*Web frontend testing with Playwright*
-1. kimi-for-coding/k2p5
-2. anthropic/claude-sonnet-4-5
-3. google/antigravity-gemini-3-flash
-
-### goop-verifier
-*Post-execution verification with security focus*
-1. openai/gpt-5.2-codex
-2. anthropic/claude-opus-4-5
-
-### goop-writer
-*Comprehensive documentation generation*
-1. google/antigravity-gemini-3-pro-high
-2. kimi-for-coding/k2p5
-3. anthropic/claude-sonnet-4-5
-
-## Memory System Configuration
-
-The memory system allows GoopSpec to:
-- Remember decisions and their reasoning
-- Recall patterns from past work
-- Build context across sessions
-
-### Configuration Options
-
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `memoryEnabled` | boolean | true | Enable/disable memory |
-| `memoryProvider` | string | "local" | Embedding provider |
-| `memoryWorkerPort` | number | 37777 | Worker process port |
-
-### Embedding Providers
-
-- **local** - Uses `Xenova/all-MiniLM-L6-v2`, runs locally, free
-- **openai** - Uses OpenAI's embedding API, requires API key
-- **ollama** - Uses local Ollama server
-
-## Troubleshooting
-
-### "Memory worker not responding"
-
-1. Check if port 37777 is in use: `lsof -i :37777`
-2. Try a different port: `memoryWorkerPort: 37778`
-3. Check memory directory exists: `.goopspec/memory/`
-
-### "Configuration not loading"
-
-1. Run `goop_setup(action: "verify")` to diagnose
-2. Check for JSON syntax errors in config files
-3. Try `goop_setup(action: "reset", scope: "project", confirmed: true)`
-
-### "MCPs not installing"
-
-MCPs require OpenCode configuration. Check:
-1. OpenCode is installed and configured
-2. You have write permissions to ~/.config/opencode/
-
-## Tips
-
-1. **Start with detect** - Always check what's already configured
-2. **Use verify after changes** - Ensures everything works
-3. **Preserve data on reset** - Don't lose memories unless needed
-4. **Quick setup is fine** - Model defaults work well for most users
-5. **Local memory is best** - No API costs, runs offline
-
-## Complete Example
-
-First-time setup:
+---
 
-```
-// 1. Check current state
-goop_setup(action: "detect")
+## Completion
 
-// 2. Initialize everything
-goop_setup(
-  action: "init",
-  scope: "both",
-  projectName: "my-project",
-  mcpPreset: "recommended",
-  memoryEnabled: true,
-  memoryProvider: "local",
-  enableOrchestrator: true
-)
+After setup completes, show:
 
-// 3. Verify
-goop_setup(action: "verify")
 ```
+## GoopSpec Setup Complete
 
-Modify existing:
-
-```
-// Update just the executor model
-goop_setup(
-  action: "apply",
-  scope: "project",
-  agentModels: {
-    "goop-executor": "anthropic/claude-opus-4-5"
-  }
-)
+Next: Run `/goop-discuss` to start your first feature.
 ```

package/commands/goop-specify.md

@@ -16,217 +16,43 @@ alternatives:
 
 **Lock the specification.** Create a binding contract between user and agent.
 
-## Usage
+## Immediate Action
 
-```bash
-/goop-specify
+**STOP. Execute this tool call NOW before reading anything else:**
 ```
-
-## Gate Requirement
-
-```
-+================================================================+
-|  SPEC GATE: Planning must be complete before locking.           |
-|  SPEC.md and BLUEPRINT.md must exist with full traceability.    |
-+================================================================+
+goop_reference({ name: "specify-process" })
 ```
 
-**Required before this command:**
-- `.goopspec/SPEC.md` exists
-- `.goopspec/BLUEPRINT.md` exists
-- Traceability matrix shows 100% coverage
+**Then follow the process from that reference.** Do not process user messages until you have loaded and understood the protocol.
+
+## Quick Summary
 
-**If not satisfied:** Refuse and redirect to `/goop-plan`
+**Gate:** SPEC.md and BLUEPRINT.md must exist with 100% traceability.
 
-## Tools Used
+### Tools Used
 
-| Tool | Purpose in This Command |
-|------|------------------------|
+| Tool | Purpose |
+|------|---------|
 | `goop_status` | Check current phase and readiness |
-| `goop_state` | **Lock the specification** - NEVER edit state.json directly |
+| `goop_state` | **Lock the specification** (NEVER edit state.json directly) |
 | `goop_spec` | Validate spec structure |
 | `memory_search` | Find relevant prior context |
 | `goop_adl` | Log the spec lock decision |
+| `goop_reference` | Load detailed process |
 
-**CRITICAL: Never read or edit .goopspec/state.json directly. Always use `goop_state` tool.**
-
----
-
-## Process
-
-### Phase 1: Gate Check
-
-**Execute BEFORE anything else:**
-
-```
-goop_status()
-Read(".goopspec/SPEC.md")
-Read(".goopspec/BLUEPRINT.md")
-```
-
-**1.1 Check documents exist:**
-
-```
-IF .goopspec/SPEC.md does not exist:
-  REFUSE with:
-  
-  ## 🔮 GoopSpec · Gate Blocked
-  
-  ✗ No specification found.
-  
-  → Run: `/goop-plan`
-  
-  ---
-```
-
-**1.2 Check traceability:**
-
-```
-IF traceability matrix shows < 100%:
-  REFUSE with:
-  
-  ## 🔮 GoopSpec · Traceability Incomplete
-  
-  ✗ Not all must-haves have mapped tasks.
-  
-  → Update BLUEPRINT.md or re-run `/goop-plan`
-  
-  ---
-```
-
-### Phase 2: Present Contract
-
-**Display the contract for confirmation:**
-
-```
-## 🔮 GoopSpec · Contract Gate
-
-📜 Review and confirm the specification
-
-### SPECIFICATION: [Name]
+### Process Overview
 
-#### Must-Haves (The Contract)
+1. **Gate Check** — Verify SPEC.md, BLUEPRINT.md, 100% traceability
+2. **Present Contract** — Show must-haves, out-of-scope, execution plan
+3. **Handle Response** — "confirm" locks, "amend" modifies, "cancel" returns
 
-| ID | Requirement | Covered By |
-|----|-------------|------------|
-| MH1 | [Title] | Wave X, Tasks Y |
-| MH2 | [Title] | Wave X, Tasks Y |
+### Confirmation Keywords
 
-#### Out of Scope
-
-- [Item 1]
-- [Item 2]
-
-#### Execution Plan
-
-| Wave | Focus | Tasks |
-|------|-------|-------|
-| 1 | [Name] | [N] |
-| 2 | [Name] | [M] |
-
-✓ Traceability: 100%
-
----
-
-⚠️ **Action Required:**
-- Type **"confirm"** to lock the specification
-- Type **"amend"** to modify requirements
-- Type **"cancel"** to return to planning
-```
-
-### Phase 3: Handle Response
-
-**On "confirm":**
-
-1. Lock the spec using goop_state:
-```
-goop_state({ action: "lock-spec" })
-```
-
-This atomically updates the workflow state. **NEVER edit state.json directly.**
-
-2. Update SPEC.md:
-```markdown
-**Status:** Locked
-**Locked At:** [timestamp]
-```
-
-3. Save to memory:
-```
-memory_decision({
-  decision: "Spec locked for [feature]",
-  reasoning: "User confirmed requirements after review",
-  impact: "high"
-})
-```
-
-4. Generate HANDOFF.md:
-```
-# Session Handoff
-
-**Phase:** specify
-
-## Accomplished
-- Spec locked with [N] must-haves
-- Traceability verified at 100%
-
-## Next Session
-Run: /goop-execute
-
-## Context
-Specification locked. Ready for execution.
-```
-
-5. Display completion:
-```
-## 🔮 GoopSpec · Specification Locked
-
-🔒 The spec is now a binding contract
-
-| Status | Value |
-|--------|-------|
-| Locked | ✓ Yes |
-| Must-Haves | [N] |
-| Waves | [M] |
-| Tasks | [P] |
-
-Changes now require `/goop-amend` with impact analysis.
-
-### Next Step
-
-**Begin execution** — Implement the blueprint
-
-→ `/goop-execute`
-
----
-
-Start a **new session** for fresh context, then run the command.
-```
-
-**On "amend":**
-
-```
-## 🔮 GoopSpec · Amendment Mode
-
-What would you like to change?
-
-1. Add a must-have
-2. Remove a must-have
-3. Modify acceptance criteria
-4. Change out of scope
-5. Cancel
-
----
-```
-
-Use `question` tool to get choice, then process amendment.
-
-**On "cancel":**
-
-```
-Specification not locked. Returning to planning.
-Run `/goop-plan` to modify or `/goop-discuss` to restart discovery.
-```
+| Keyword | Action |
+|---------|--------|
+| `confirm` | Lock specification, proceed to /goop-execute |
+| `amend` | Enter amendment mode |
+| `cancel` | Return to planning |
 
 ## Output
 
@@ -236,110 +62,19 @@ Run `/goop-plan` to modify or `/goop-discuss` to restart discovery.
 | State (via goop_state) | `specLocked: true` |
 | `.goopspec/HANDOFF.md` | Session handoff generated |
 
-## Transitions
-
-| Outcome | Next Step |
-|---------|-----------|
-| Spec locked | `/goop-execute` to begin implementation |
-| Amendments requested | Process changes, re-present contract |
-| Cancelled | `/goop-plan` to modify planning |
-
-## Amendment Protocol (After Lock)
-
-Once locked, changes require formal amendment:
-
-1. **Propose change:** User describes modification
-2. **Impact analysis:** Orchestrator assesses affected tasks
-3. **Blueprint update:** Modify BLUEPRINT.md if needed
-4. **Re-confirm:** User confirms amended spec
-5. **Log amendment:** Add to SPEC.md amendment history
-
-```markdown
-## Amendment History
-
-| Version | Date | Change | Impact | Approved |
-|---------|------|--------|--------|----------|
-| 1.1 | [date] | Added MH3 | +1 task | User |
-```
-
-## Examples
-
-**Successful Lock:**
-```
-User: /goop-specify
-
-Orchestrator:
-+--------------------------------------------------------+
-|  GOOPSPEC > CONTRACT GATE                               |
-+--------------------------------------------------------+
-
-## SPECIFICATION: Dark Mode Toggle
-
-### Must-Haves
-| ID | Requirement | Covered By |
-|----|-------------|------------|
-| MH1 | Toggle UI | W1.T1 |
-| MH2 | Theme switch | W1.T2, W2.T1 |
-| MH3 | Persist preference | W2.T2 |
-
-### Out of Scope
-- Multiple themes (beyond light/dark)
-- Per-component theming
-
-### Traceability: 100%
-
-Type "confirm" to lock.
-
-User: confirm
-
-Orchestrator:
-+--------------------------------------------------------+
-|  GOOPSPEC > SPECIFICATION LOCKED                        |
-+--------------------------------------------------------+
-
-## > Next Step
-`/goop-execute`
-```
-
-**Gate Blocked:**
-```
-User: /goop-specify
-
-Orchestrator:
-+--------------------------------------------------------+
-|  GOOPSPEC > GATE BLOCKED                                |
-+--------------------------------------------------------+
-|  No specification found.                                |
-|  Run: /goop-plan                                        |
-+--------------------------------------------------------+
-```
-
 ## Success Criteria
 
 - [ ] Gate check performed (SPEC.md + BLUEPRINT.md exist)
 - [ ] Traceability verified at 100%
-- [ ] Contract presented clearly with must-haves and out-of-scope
+- [ ] Contract presented with must-haves and out-of-scope
 - [ ] User explicitly confirmed with "confirm"
 - [ ] State updated via `goop_state({ action: "lock-spec" })`
-- [ ] SPEC.md updated with Locked status
-- [ ] HANDOFF.md generated
-- [ ] User knows next step is `/goop-execute`
 
 ## Anti-Patterns
 
-**DON'T:**
-- Skip the gate check
-- Lock without user confirmation
-- Proceed with incomplete traceability
-- Skip handoff generation
-
-**DO:**
-- Verify 100% traceability before presenting
-- Require explicit "confirm" keyword
-- Log the lock to memory
-- Generate clear handoff
+**DON'T:** Skip gate check, lock without confirmation, proceed with incomplete traceability
+**DO:** Verify 100% traceability, require explicit "confirm", log to memory
 
 ---
 
-*Specification Lock Protocol v0.1.4*
-*"The spec is a contract. Lock it before you build."*
+*Load `goop_reference({ name: "specify-process" })` for full process details.*