opencode-goopspec 0.1.3 → 0.1.4

package/commands/goop-quick.md

@@ -13,6 +13,18 @@ description: Fast-track a small task
 /goop-quick [task description]
 ```
 
+## Tools Used
+
+| Tool | Purpose in This Command |
+|------|------------------------|
+| `goop_status` | Check current state, skip heavy workflow |
+| `memory_search` | Find relevant prior context |
+| `memory_save` | Persist any discoveries |
+
+**Hook Support:** Minimal - quick mode bypasses most phase enforcement.
+
+---
+
 ## How It Works
 
 Quick mode bypasses the formal Plan/Research/Specify phases while maintaining safety guarantees. Ideal for bug fixes, small refactors, or docs.

package/commands/goop-recall.md

@@ -16,6 +16,17 @@ Search the persistent memory system for relevant context. Use this to:
 `/goop-recall recent` - Show recent memories
 `/goop-recall decisions` - Show recent architectural decisions
 
+## Tools Used
+
+| Tool | Purpose in This Command |
+|------|------------------------|
+| `memory_search` | Search persistent memories |
+| `session_search` | Search session history |
+
+**Hook Support:** None specific - read-only query.
+
+---
+
 ## Instructions
 
 When this command is invoked:

package/commands/goop-remember.md

@@ -17,6 +17,18 @@ Save important information to the persistent memory system for future sessions.
 `/goop-remember note: [content]` - Quick note
 `/goop-remember todo: [content]` - Create a durable task
 
+## Tools Used
+
+| Tool | Purpose in This Command |
+|------|------------------------|
+| `memory_save` | Store structured memories |
+| `memory_decision` | Record decisions with reasoning |
+| `memory_note` | Quick note capture |
+
+**Hook Support:** `system.transform` uses saved memories in future sessions.
+
+---
+
 ## Instructions
 
 When this command is invoked:

package/commands/goop-research.md

@@ -23,6 +23,19 @@ alternatives:
 /goop-research [topic or question]
 ```
 
+## Tools Used
+
+| Tool | Purpose in This Command |
+|------|------------------------|
+| `goop_status` | Check current phase allows research |
+| `memory_search` | Find prior research on same topic |
+| `memory_save` | Persist research findings |
+| `goop_skill` | Load specialized research skills |
+
+**Hook Support:** `system.transform` injects prior research context.
+
+---
+
 ## How It Works
 
 Research is an **opt-in** phase used when the path forward isn't clear. It prevents "coding in the dark."

package/commands/goop-resume.md

@@ -13,6 +13,18 @@ description: Resume from a saved checkpoint
 /goop-resume [checkpoint-id]
 ```
 
+## Tools Used
+
+| Tool | Purpose in This Command |
+|------|------------------------|
+| `goop_checkpoint` | Load saved execution state |
+| `goop_status` | Verify current state matches checkpoint |
+| `memory_search` | Find context from when checkpoint was saved |
+
+**Hook Support:** `system.transform` injects checkpoint context automatically.
+
+---
+
 ## How It Works
 
 Loads a saved state, restores the workflow context, and prepares the agent to continue exactly where it left off.

package/commands/goop-setup.md

@@ -20,6 +20,16 @@ You are helping the user set up or modify their GoopSpec configuration. This wiz
 | `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.
@@ -146,12 +156,12 @@ goop_setup(
 *Systematic debugging with hypothesis testing*
 1. openai/gpt-5.2-codex
 2. anthropic/claude-opus-4-5
-3. opencode/kimi-k2.5-free
+3. kimi-for-coding/k2p5
 
 ### goop-designer
 *Visual design planning and UI/UX reasoning*
 1. anthropic/claude-opus-4-5
-2. opencode/kimi-k2.5-free
+2. kimi-for-coding/k2p5
 3. google/antigravity-gemini-3-pro-high
 
 ### goop-executor
@@ -159,7 +169,7 @@ goop_setup(
 1. openai/gpt-5.2-codex
 2. anthropic/claude-opus-4-5
 3. anthropic/claude-sonnet-4-5
-4. opencode/kimi-k2.5-free
+4. kimi-for-coding/k2p5
 5. google/antigravity-gemini-3-pro-high
 6. opencode/glm-4.7-free
 
@@ -179,26 +189,26 @@ goop_setup(
 *Primary orchestrator - spec clarity and wave execution*
 1. anthropic/claude-opus-4-5
 2. openai/gpt-5.2-codex
-3. opencode/kimi-k2.5-free
+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. opencode/kimi-k2.5-free
+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. opencode/kimi-k2.5-free
+3. kimi-for-coding/k2p5
 4. opencode/glm-4.7-free
 
 ### goop-tester
 *Web frontend testing with Playwright*
-1. opencode/kimi-k2.5-free
+1. kimi-for-coding/k2p5
 2. anthropic/claude-sonnet-4-5
 3. google/antigravity-gemini-3-flash
 
@@ -210,7 +220,7 @@ goop_setup(
 ### goop-writer
 *Comprehensive documentation generation*
 1. google/antigravity-gemini-3-pro-high
-2. opencode/kimi-k2.5-free
+2. kimi-for-coding/k2p5
 3. anthropic/claude-sonnet-4-5
 
 ## Memory System Configuration

package/commands/goop-specify.md

@@ -2,6 +2,7 @@
 name: goop-specify
 description: Lock the specification contract
 phase: specify
+requires: planning_complete
 next-step: "Once the spec is locked and confirmed, begin implementation"
 next-command: /goop-execute
 alternatives:
@@ -21,49 +22,324 @@ alternatives:
 /goop-specify
 ```
 
-## How It Works
+## Gate Requirement
 
-This command marks the transition from planning to commitment. It generates the `SPEC.md` and `BLUEPRINT.md` files and presents them for user confirmation.
+```
++================================================================+
+|  SPEC GATE: Planning must be complete before locking.           |
+|  SPEC.md and BLUEPRINT.md must exist with full traceability.    |
++================================================================+
+```
+
+**Required before this command:**
+- `.goopspec/SPEC.md` exists
+- `.goopspec/BLUEPRINT.md` exists
+- Traceability matrix shows 100% coverage
+
+**If not satisfied:** Refuse and redirect to `/goop-plan`
+
+## Tools Used
+
+| Tool | Purpose in This Command |
+|------|------------------------|
+| `goop_status` | Check current phase and readiness |
+| `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 |
+
+**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]
 
-### 1. Artifact Generation
-Based on the plan (and optional research), the agent generates:
-- **SPEC.md:** The requirements contract.
-- **BLUEPRINT.md:** The execution plan (Waves & Tasks).
+#### Must-Haves (The Contract)
 
-### 2. The Contract Gate
-The agent displays a summary of the contract:
-- **Must Haves:** Guaranteed deliverables.
-- **Nice to Haves:** Best-effort items.
-- **Out of Scope:** Explicit exclusions.
+| ID | Requirement | Covered By |
+|----|-------------|------------|
+| MH1 | [Title] | Wave X, Tasks Y |
+| MH2 | [Title] | Wave X, Tasks Y |
 
-### 3. User Confirmation
-The user **MUST** type "confirm" to lock the spec. 
-- If the user types "amend", the agent enters amendment mode to adjust requirements.
+#### 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.
+```
 
 ## Output
 
-- `.goopspec/SPEC.md` (Locked)
-- `.goopspec/BLUEPRINT.md` (Ready for execution)
-- **State Transition:** `plan` -> `execute`
-
-## Example Interaction
-
-> **User:** `/goop-specify`
-> **Agent:** 
-> ```
-> 🔒 CONTRACT GATE
-> 
-> MUST HAVES:
-> • Email/Password Login
-> • Session Persistence
-> 
-> OUT OF SCOPE:
-> • OAuth (Google/Github)
-> 
-> Type "confirm" to lock, or "amend" to change.
-> ```
-> **User:** `confirm`
-> **Agent:** "Spec locked. Ready to execute."
-
-## Quick Mode
-For `/goop-quick` tasks, this phase is skipped. The intent captured in the plan serves as the implicit spec.
+| File | Change |
+|------|--------|
+| `.goopspec/SPEC.md` | Status updated to "Locked" |
+| 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
+- [ ] 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
+
+---
+
+*Specification Lock Protocol v0.1.4*
+*"The spec is a contract. Lock it before you build."*