opencode-goopspec 0.1.4 → 0.1.5

package/README.md

@@ -6,8 +6,7 @@
 
 **Stop the AI chaos. Ship what you actually want.**
 
-[![Version](https://img.shields.io/badge/version-0.1.4-blue?style=for-the-badge)](https://github.com/hffmnnj/opencode-goopspec)
-[![OpenCode](https://img.shields.io/badge/OpenCode-plugin-0891b2?style=for-the-badge)](https://opencode.ai)
+[![Version](https://img.shields.io/badge/version-0.1.5-blue?style=for-the-badge)](https://github.com/hffmnnj/opencode-goopspec)
 [![Bun](https://img.shields.io/badge/Bun-1.0+-f97316?style=for-the-badge&logo=bun&logoColor=white)](https://bun.sh)
 [![TypeScript](https://img.shields.io/badge/TypeScript-5.8-3178c6?style=for-the-badge&logo=typescript&logoColor=white)](https://www.typescriptlang.org/)
 [![Tests](https://img.shields.io/badge/tests-1056%20passing-22c55e?style=for-the-badge)](./TEST-SUMMARY.md)

package/agents/goop-debugger.md

@@ -453,4 +453,4 @@ Restart if:
 
 **Remember: You are a scientist, not a guesser. Hypothesize. Test. Prove. And ALWAYS tell the orchestrator the status and next steps.**
 
-*GoopSpec Debugger v0.1.4*
+*GoopSpec Debugger v0.1.5*

package/agents/goop-designer.md

@@ -506,4 +506,4 @@ List screens and states to verify visually.
 
 **Remember: You design experiences. Every pixel serves the user. And ALWAYS tell the orchestrator how to implement your designs.**
 
-*GoopSpec Designer v0.1.4*
+*GoopSpec Designer v0.1.5*

package/agents/goop-executor.md

@@ -321,7 +321,7 @@ If verification is skipped, mark as Fail and explain why in Evidence.
 Every response must end with the XML envelope below. You may provide a short human-readable Markdown summary before the XML, but the XML is required and must be the final block.
 
 ```xml
-<goop_report version="0.1.4">
+<goop_report version="0.1.5">
   <status>COMPLETE|PARTIAL|BLOCKED|CHECKPOINT</status>
   <agent>goop-executor</agent>
   <task_id>W[wave].T[task]</task_id>
@@ -434,4 +434,4 @@ Every response must end with the XML envelope below. You may provide a short hum
 
 **Remember: Your code should look like it was written by the best developer on the team. Quality is non-negotiable. And your responses should tell the orchestrator EXACTLY what to do next.**
 
-*GoopSpec Executor v0.1.4*
+*GoopSpec Executor v0.1.5*

package/agents/goop-explorer.md

@@ -302,7 +302,7 @@ Exploration complete. Codebase mapped.
 [Most important thing to know about this codebase]
 
 ```xml
-<goop_report version="0.1.4">
+<goop_report version="0.1.5">
   <status>COMPLETE</status>
   <agent>goop-explorer</agent>
   <task_name>Codebase exploration</task_name>
@@ -408,4 +408,4 @@ Provide focus area for deeper exploration.
 
 **Remember: You're the scout. Map fast. Report clear. Move on. And ALWAYS tell the orchestrator what they need to know.**
 
-*GoopSpec Explorer v0.1.4*
+*GoopSpec Explorer v0.1.5*

package/agents/goop-librarian.md

@@ -403,4 +403,4 @@ Responses MUST use an XML envelope. Include required sections: <query_log>, <rel
 
 **Remember: You are the gateway to knowledge. Be fast. Be accurate. Be helpful. And ALWAYS tell the orchestrator what to do with your findings.**
 
-*GoopSpec Librarian v0.1.4*
+*GoopSpec Librarian v0.1.5*

package/agents/goop-orchestrator.md

@@ -603,4 +603,4 @@ All subagents return XML response envelopes. Parse them:
 
 **Remember: You are the Conductor. You don't play instruments. You make the orchestra play beautifully together. Enforce the gates. Generate handoffs. Keep context clean.**
 
-*GoopSpec Orchestrator v0.1.4*
+*GoopSpec Orchestrator v0.1.5*

package/agents/goop-planner.md

@@ -421,7 +421,7 @@ V "Task 2.1: Implement JWT auth service"
 **EVERY response MUST end with this XML envelope:**
 
 ```xml
-<goop_report version="0.1.4">
+<goop_report version="0.1.5">
   <status>COMPLETE|PARTIAL|BLOCKED</status>
   <agent>goop-planner</agent>
   <task_name>Create execution blueprint</task_name>
@@ -540,4 +540,4 @@ Run `/goop-discuss` to complete discovery interview.
 
 **Remember: Plans are contracts. Every must-have traces to tasks. Every task is verifiable. Spec-nail before you build.**
 
-*GoopSpec Planner v0.1.4*
+*GoopSpec Planner v0.1.5*

package/agents/goop-researcher.md

@@ -350,7 +350,7 @@ Research complete. Ready to inform [planning/specification/decision].
 [What decision can now be made with this research]
 
 ```xml
-<goop_report version="0.1.4">
+<goop_report version="0.1.5">
   <status>COMPLETE</status>
   <agent>goop-researcher</agent>
   <task_name>Research [topic]</task_name>
@@ -465,4 +465,4 @@ Additional research needed.
 
 **Remember: Research enables decisions. Make it count. And ALWAYS tell the orchestrator what to do with your findings.**
 
-*GoopSpec Researcher v0.1.4*
+*GoopSpec Researcher v0.1.5*

package/agents/goop-tester.md

@@ -504,4 +504,4 @@ export class LoginPage {
 
 **Remember: You are the last line of defense. Find bugs before users do. ALWAYS report test status, coverage targets, and flakiness risks.**
 
-*GoopSpec Tester v0.1.4*
+*GoopSpec Tester v0.1.5*

package/agents/goop-verifier.md

@@ -433,4 +433,4 @@ STOP all other work. Address security first.
 
 **Remember: You are the last line of defense. Trust nothing. Verify everything. And ALWAYS tell the orchestrator exactly what to do next.**
 
-*GoopSpec Verifier v0.1.4*
+*GoopSpec Verifier v0.1.5*

package/agents/goop-writer.md

@@ -572,4 +572,4 @@ Returns a list of users.
 
 **Remember: Good documentation prevents questions. Great documentation enables success. And ALWAYS tell the orchestrator what to do with your documentation.**
 
-*GoopSpec Writer v0.1.4*
+*GoopSpec Writer v0.1.5*

package/agents/memory-distiller.md

@@ -75,7 +75,7 @@ session_search (raw events) → distill → memory_save (structured) + PROJECT_K
 - Enable future search
 - Build a durable project memory
 
-## Responsibilities (v0.1.4)
+## Responsibilities (v0.1.5)
 
 - Update `PROJECT_KNOWLEDGE_BASE.md` after major decisions
 - Generate HANDOFF.md content for session continuity
@@ -335,4 +335,4 @@ GoopSpec session context:
 
 **Remember: You build the system's long-term memory. Quality now enables intelligence later.**
 
-*GoopSpec Memory Distiller v0.1.4*
+*GoopSpec Memory Distiller v0.1.5*

package/commands/goop-accept.md

@@ -453,5 +453,5 @@ Orchestrator: Run `/goop-execute` to continue.
 
 ---
 
-*Acceptance Protocol v0.1.4*
+*Acceptance Protocol v0.1.5*
 *"Verify everything. Accept explicitly."*

package/commands/goop-discuss.md

@@ -430,5 +430,5 @@ planning. Want to do that first?"
 
 ---
 
-*Discovery Interview Protocol v0.1.4*
+*Discovery Interview Protocol v0.1.5*
 *"Nail the spec before you write the code."*

package/commands/goop-execute.md

@@ -416,5 +416,5 @@ Orchestrator: Resuming with Option A...
 
 ---
 
-*Execution Protocol v0.1.4*
+*Execution Protocol v0.1.5*
 *"Execute in waves. Checkpoint often. Handoff clean."*

package/commands/goop-plan.md

@@ -162,12 +162,76 @@ Extract:
 memory_search({ query: "[feature] architecture decisions patterns", limit: 5 })
 ```
 
-**3.3 Load project knowledge:**
+**3.3 Create or load project knowledge:**
 
 ```
-Read(".goopspec/PROJECT_KNOWLEDGE_BASE.md")  # If exists
+Read(".goopspec/PROJECT_KNOWLEDGE_BASE.md")
 ```
 
+**If PROJECT_KNOWLEDGE_BASE.md does not exist, CREATE IT:**
+
+This file is required by subagents throughout the workflow. Extract stack/convention info from REQUIREMENTS.md constraints section and create a minimal knowledge base:
+
+```markdown
+# Project Knowledge Base
+
+**Last Updated:** [timestamp]
+**Updated By:** orchestrator (auto-generated from discovery)
+
+---
+
+## Project Identity
+
+**Name:** [From REQUIREMENTS.md vision]
+**Type:** [Inferred from constraints]
+**Stage:** Active
+
+---
+
+## Stack (Non-Negotiable)
+
+[Extract from REQUIREMENTS.md Constraints section]
+
+### Runtime & Language
+- **Runtime:** [e.g., Node.js / Bun / Browser]
+- **Language:** [e.g., TypeScript]
+
+### Frameworks & Libraries
+- **Framework:** [From constraints]
+- **Testing:** [From constraints or infer from package.json]
+
+---
+
+## Conventions
+
+[Extract from REQUIREMENTS.md or infer from codebase]
+
+### File Naming
+- **Files:** [kebab-case / camelCase]
+- **Tests:** [*.test.ts / *.spec.ts]
+
+### Code Style
+- **Exports:** [Named / Default]
+
+---
+
+## Architecture Decisions
+
+*To be populated during planning and execution.*
+
+---
+
+## Known Gotchas
+
+*To be populated as issues are discovered.*
+
+---
+
+*Auto-generated from discovery interview. Update as project evolves.*
+```
+
+Write to `.goopspec/PROJECT_KNOWLEDGE_BASE.md` before proceeding.
+
 ### Phase 4: Spawn Planner
 
 **Display banner:**
@@ -395,6 +459,7 @@ memory_save({
 | `.goopspec/BLUEPRINT.md` | Wave-based execution plan |
 | `.goopspec/CHRONICLE.md` | Progress tracking |
 | `.goopspec/HANDOFF.md` | Session handoff |
+| `.goopspec/PROJECT_KNOWLEDGE_BASE.md` | Stack and conventions (created if missing) |
 | State (via goop_state) | Workflow state (phase transitions) |
 
 ## Transitions
@@ -460,6 +525,7 @@ Orchestrator:
 - [ ] Gate check performed (interview_complete + REQUIREMENTS.md)
 - [ ] If gate fails, refused with clear redirect to /goop-discuss
 - [ ] Existing documents handled (archive/continue/overwrite)
+- [ ] PROJECT_KNOWLEDGE_BASE.md created if missing (from REQUIREMENTS.md constraints)
 - [ ] goop-planner spawned with full discovery context
 - [ ] SPEC.md created with traceability
 - [ ] BLUEPRINT.md created with spec coverage
@@ -486,5 +552,5 @@ Orchestrator:
 
 ---
 
-*Planning Protocol v0.1.4*
+*Planning Protocol v0.1.5*
 *"Every must-have traces to tasks."*

package/commands/goop-setup.md

@@ -3,307 +3,61 @@ name: goop-setup
 description: GoopSpec setup wizard - first-time init, configuration, and verification
 ---
 
-# GoopSpec Setup Wizard
+# EXECUTE NOW
 
-You are helping the user set up or modify their GoopSpec configuration. This wizard handles first-time setup, modifications, 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
+**Step 1: Run detection immediately:**
 
 ```
 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.
+Then follow the workflow below based on the result.
 
-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
-
-### 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

@@ -341,5 +341,5 @@ Orchestrator:
 
 ---
 
-*Specification Lock Protocol v0.1.4*
+*Specification Lock Protocol v0.1.5*
 *"The spec is a contract. Lock it before you build."*

package/commands/goop-status.md

@@ -295,5 +295,5 @@ User: /goop-status
 
 ---
 
-*Status Protocol v0.1.4*
+*Status Protocol v0.1.5*
 *"Know where you are. Know where to go."*