opencode-goopspec 0.1.4 → 0.1.6

package/commands/goop-plan.md

@@ -18,374 +18,39 @@ alternatives:
 
 **Create Specification and Blueprint.** Transform discovery interview into executable plans.
 
-## Usage
+## Immediate Action
 
-```bash
-/goop-plan
+**STOP. Execute this tool call NOW before reading anything else:**
 ```
-
-## Gate Requirement
-
-```
-+================================================================+
-|  DISCOVERY GATE: Interview must be complete before planning.    |
-|  This ensures we build the RIGHT thing.                         |
-+================================================================+
+goop_reference({ name: "plan-process" })
 ```
 
-**Required before this command:**
-- `interviewComplete: true` (check via `goop_state({ action: "get" })`)
-- `.goopspec/REQUIREMENTS.md` exists
+**Then execute the gate checks from that reference.** Do not process user messages until gates are checked.
 
-**If not satisfied:** Refuse and redirect to `/goop-discuss`
+## Quick Summary
 
-**CRITICAL: Never read or edit .goopspec/state.json directly. Always use `goop_state` tool.**
-
-## Orchestrator Role
+**Gate:** `interviewComplete: true` required. Check via `goop_state({ action: "get" })`.
 
 **You check the gate, then spawn the planner.** The planner creates SPEC.md and BLUEPRINT.md.
 
-## Tools Used
+### Tools Used
 
-| Tool | Purpose in This Command |
-|------|------------------------|
+| Tool | Purpose |
+|------|---------|
 | `goop_status` | Check current phase and gate requirements |
+| `goop_state` | Check/update workflow state (NEVER edit state.json directly) |
 | `goop_spec` | Validate interview complete, load existing specs |
 | `memory_search` | Find prior architecture decisions |
-| `memory_decision` | Record new planning decisions |
-| `goop_reference` | Load spec/blueprint templates |
-
-**Hook Support:** `tool.execute.after` may auto-transition to specify phase.
-
----
-
-## Process
-
-### Phase 1: Gate Check
-
-**Execute BEFORE anything else:**
-
-```
-goop_status()
-goop_state({ action: "get" })          # NEVER read state.json directly
-Read(".goopspec/REQUIREMENTS.md")
-```
-
-**1.1 Check interviewComplete:**
-
-```
-IF state.interviewComplete != true:
-  REFUSE with:
-  
-  ## 🔮 GoopSpec · Gate Blocked
-  
-  ✗ Discovery interview required before planning.
-  
-  → Run: `/goop-discuss`
-  
-  ---
-  
-  EXIT command.
-```
-
-**1.2 Check REQUIREMENTS.md exists:**
-
-```
-IF .goopspec/REQUIREMENTS.md does not exist:
-  REFUSE with:
-  
-  ## 🔮 GoopSpec · Gate Blocked
-  
-  ✗ No discovery output found.
-  
-  → Run: `/goop-discuss`
-  
-  ---
-  
-  EXIT command.
-```
-
-**1.3 Gate passed:**
-
-```
-## 🔮 GoopSpec · Planning
-
-✓ Discovery gate passed
-
-⏳ Creating specification and blueprint...
-
----
-```
-
-### Phase 2: Check for Existing Documents
-
-**2.1 Check for existing SPEC.md/BLUEPRINT.md:**
-
-```
-Read(".goopspec/SPEC.md")
-Read(".goopspec/BLUEPRINT.md")
-```
-
-**2.2 If documents exist:**
-
-Use `question` tool:
-- header: "Existing Project"
-- question: "I found existing project documents. How would you like to proceed?"
-- options:
-  - "Archive and start fresh (Recommended)" — Move current docs to archive, create new
-  - "Continue existing project" — Resume work (exit, run /goop-status)
-  - "Overwrite without archiving" — Replace documents (loses history)
-
-**On "Archive":** Spawn writer to archive, then continue.
-**On "Continue":** Exit, suggest `/goop-status`.
-**On "Overwrite":** Warn, then continue.
-
-### Phase 3: Load Context
-
-**3.1 Load discovery interview:**
-
-```
-Read(".goopspec/REQUIREMENTS.md")
-```
-
-Extract:
-- Vision
-- Must-haves (with acceptance criteria)
-- Constraints
-- Out of scope
-- Assumptions
-- Risks
-
-**3.2 Search memory:**
-
-```
-memory_search({ query: "[feature] architecture decisions patterns", limit: 5 })
-```
-
-**3.3 Load project knowledge:**
-
-```
-Read(".goopspec/PROJECT_KNOWLEDGE_BASE.md")  # If exists
-```
-
-### Phase 4: Spawn Planner
-
-**Display banner:**
-```
-## 🔮 GoopSpec · Creating Documents
-
-⏳ Spawning planner to create SPEC.md and BLUEPRINT.md...
-
----
-```
-
-**Spawn goop-planner with full context:**
-
-```
-task({
-  subagent_type: "goop-planner",
-  description: "Create SPEC and BLUEPRINT",
-  prompt: `
-## TASK
-Create specification and blueprint from discovery interview.
-
-## PROJECT CONTEXT
-[From PROJECT_KNOWLEDGE_BASE.md if exists]
-- Stack: [technologies]
-- Conventions: [naming, patterns]
-
-## DISCOVERY INTERVIEW OUTPUT
-[Full content of REQUIREMENTS.md]
-
-### Vision
-[Vision section]
-
-### Must-Haves
-[Must-haves with acceptance criteria]
-
-### Constraints
-[Technical and practical constraints]
-
-### Out of Scope
-[Explicit exclusions]
-
-### Assumptions
-[Baseline assumptions]
-
-### Risks
-[Identified risks with mitigations]
-
-## INSTRUCTIONS
-
-1. **Verify discovery completeness:**
-   - Vision defined? 
-   - Must-haves listed with acceptance criteria?
-   - Out of scope defined?
-   - Risks identified?
-   
-   If missing critical info, return BLOCKED.
-
-2. **Create .goopspec/SPEC.md:**
-   - Transform must-haves into formal requirements (MH1, MH2, etc.)
-   - Include acceptance criteria for each
-   - Add traceability section (will be filled after blueprint)
-   - Mark status as "Draft"
+| `goop_reference` | Load detailed process |
 
-3. **Create .goopspec/BLUEPRINT.md:**
-   - Design wave architecture
-   - Create tasks that cover ALL must-haves
-   - Add spec coverage to each task
-   - Build traceability matrix
+### Process Overview
 
-4. **Update .goopspec/SPEC.md:**
-   - Fill traceability matrix (must-have → tasks)
-   - Verify 100% coverage
-
-5. **Initialize .goopspec/CHRONICLE.md:**
-   - Phase: plan → ready for specify
-   - Documents created with timestamps
-
-6. **Save to memory:**
-   - Key architectural decisions
-   - Technology choices with rationale
-
-7. **Return XML response envelope** with:
-   - BLUEPRINT COMPLETE status
-   - Wave summary
-   - Traceability summary
-   - Handoff instructions
-
-## VERIFICATION
-Before returning COMPLETE:
-- [ ] Every must-have has mapped tasks
-- [ ] Every task has spec coverage
-- [ ] Traceability matrix shows 100%
-- [ ] SPEC.md has all sections filled
-- [ ] BLUEPRINT.md has verification commands
-  `
-})
-```
-
-### Phase 5: Handle Response
-
-**Parse XML response from planner.**
-
-**On `COMPLETE` status:**
-
-Read created documents:
-```
-Read(".goopspec/SPEC.md")
-Read(".goopspec/BLUEPRINT.md")
-```
-
-Display completion:
-```
-## 🔮 GoopSpec · Planning Complete
-
-✨ Blueprint created successfully
-
-**Feature:** [Name from SPEC.md]
-
-| Document | Status | Location |
-|----------|--------|----------|
-| Spec | ✓ Created | .goopspec/SPEC.md |
-| Blueprint | ✓ Created | .goopspec/BLUEPRINT.md |
-| Chronicle | ✓ Created | .goopspec/CHRONICLE.md |
-
-**[N] must-haves** | **[M] waves** | **[P] tasks**
-
-### Traceability
-| Must-Have | Covered By |
-|-----------|------------|
-| MH1 | Wave X, Tasks Y |
-| MH2 | Wave X, Tasks Y |
-
-✓ Coverage: 100%
-
-### Next Step
-
-**Lock the specification** — Confirm requirements before execution
-
-→ `/goop-specify`
-
----
-
-Start a **new session** for fresh context, then run the command.
-
-**Also available:**
-- `cat .goopspec/SPEC.md` — Review specification
-- `cat .goopspec/BLUEPRINT.md` — Review execution plan
-- `/goop-research [topic]` — Investigate unknowns first
-```
-
-**Generate HANDOFF.md:**
-
-```
-Write(".goopspec/HANDOFF.md", `
-# Session Handoff
-
-**Generated:** [timestamp]
-**Phase:** plan
-
-## Accomplished
-- [x] Discovery interview completed
-- [x] SPEC.md created with [N] must-haves
-- [x] BLUEPRINT.md created with [M] waves, [P] tasks
-- [x] 100% traceability achieved
-
-## Current State
-- Phase: plan
-- Interview: complete
-- Spec: draft (not locked)
-
-## Next Session
-Run: /goop-specify
-
-## Files to Read
-1. .goopspec/SPEC.md — Requirements
-2. .goopspec/BLUEPRINT.md — Execution plan
-
-## Context Summary
-Planning complete for [feature]. [N] must-haves mapped to [P] tasks
-across [M] waves. Ready to lock specification.
-`)
-```
-
-**On `BLOCKED` status:**
-
-```
-## 🔮 GoopSpec · Planning Blocked
-
-✗ Cannot proceed
-
-**Blocker:** [From planner response]
-
-**Options:**
-1. Provide more context → `/goop-discuss`
-2. Research the unknown → `/goop-research [topic]`
-
----
-```
-
-Use `question` tool to get user choice.
-
-**On `PARTIAL` status:**
-
-Present what was created, explain gaps, offer to continue or restart.
-
-### Phase 6: Memory Persistence
-
-After successful planning:
-
-```
-memory_save({
-  type: "note",
-  title: "Plan: [Feature Name]",
-  content: "Created [N]-wave blueprint. Key decisions: [list]. Must-haves: [summary].",
-  concepts: ["planning", "blueprint", "[domain]"],
-  importance: 0.7
-})
-```
+1. **Gate Check** — Verify `interviewComplete` and REQUIREMENTS.md exist
+2. **Handle Existing** — Archive or continue if docs already exist
+3. **Load Context** — Read REQUIREMENTS.md, search memory
+4. **Create PROJECT_KNOWLEDGE_BASE.md** — If missing, generate from constraints
+5. **Spawn goop-planner** — With full discovery context
+6. **Generate HANDOFF.md** — For session continuity
 
 ## Output
 
@@ -395,96 +60,21 @@ memory_save({
 | `.goopspec/BLUEPRINT.md` | Wave-based execution plan |
 | `.goopspec/CHRONICLE.md` | Progress tracking |
 | `.goopspec/HANDOFF.md` | Session handoff |
-| State (via goop_state) | Workflow state (phase transitions) |
-
-## Transitions
-
-| Outcome | Next Step |
-|---------|-----------|
-| Planning complete | `/goop-specify` to lock |
-| Missing discovery | `/goop-discuss` to interview |
-| Unknowns remain | `/goop-research` to investigate |
-| Need to pause | `/goop-pause` to checkpoint |
-
-## Examples
-
-**Gate Passed:**
-```
-User: /goop-plan
-
-Orchestrator: 
-+--------------------------------------------------------+
-|  GOOPSPEC > PLANNING                                    |
-+--------------------------------------------------------+
-|  Discovery gate: PASSED                                  |
-|  Creating specification and blueprint...                 |
-+--------------------------------------------------------+
-
-[Spawns goop-planner]
-
-...
-
-+--------------------------------------------------------+
-|  GOOPSPEC > PLANNING COMPLETE                           |
-+--------------------------------------------------------+
-
-**Feature:** Dark Mode Toggle
-
-| Document   | Status  |
-|------------|---------|
-| Spec       | Created |
-| Blueprint  | Created |
-
-**3 must-haves** | **2 waves** | **5 tasks**
-
-## > Next Step
-`/goop-specify`
-```
-
-**Gate Blocked:**
-```
-User: /goop-plan
-
-Orchestrator:
-+--------------------------------------------------------+
-|  GOOPSPEC > GATE BLOCKED                                |
-+--------------------------------------------------------+
-|  Discovery interview required before planning.          |
-|                                                         |
-|  Run: /goop-discuss                                     |
-+--------------------------------------------------------+
-```
+| `.goopspec/PROJECT_KNOWLEDGE_BASE.md` | Stack and conventions |
 
 ## Success Criteria
 
 - [ ] 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
 - [ ] goop-planner spawned with full discovery context
-- [ ] SPEC.md created with traceability
-- [ ] BLUEPRINT.md created with spec coverage
 - [ ] 100% must-have coverage achieved
-- [ ] HANDOFF.md generated
 - [ ] User knows next step is `/goop-specify`
-- [ ] Suggested to start new session for fresh context
 
 ## Anti-Patterns
 
-**DON'T:**
-- Skip the discovery gate check
-- Conduct interview in /goop-plan (that's /goop-discuss)
-- Create documents without traceability
-- Leave user without next steps
-- Skip handoff generation
-
-**DO:**
-- Enforce the gate strictly
-- Spawn planner with complete context
-- Verify 100% traceability
-- Generate HANDOFF.md
-- Suggest new session for clean context
+**DON'T:** Skip gate check, conduct interview here, create docs without traceability
+**DO:** Enforce gate strictly, spawn planner with complete context, verify 100% traceability
 
 ---
 
-*Planning Protocol v0.1.4*
-*"Every must-have traces to tasks."*
+*Load `goop_reference({ name: "plan-process" })` for full process details.*

package/commands/goop-quick.md

@@ -1,6 +1,14 @@
 ---
 name: goop-quick
 description: Fast-track a small task
+phase: quick
+next-step: "After verification, confirm completion with the user"
+next-command: null
+alternatives:
+  - command: /goop-discuss
+    when: "If the task is complex or requires multiple waves"
+  - command: /goop-debug
+    when: "If the task is debugging a specific issue"
 ---
 
 # /goop-quick
@@ -13,49 +21,68 @@ description: Fast-track a small task
 /goop-quick [task description]
 ```
 
-## Tools Used
+## Immediate Action
 
-| Tool | Purpose in This Command |
-|------|------------------------|
-| `goop_status` | Check current state, skip heavy workflow |
+**STOP. Execute this tool call NOW before reading anything else:**
+```
+goop_reference({ name: "quick-process" })
+```
+
+**Then follow the process from that reference.** Do not process user messages until you have loaded and understood the protocol.
+
+## Quick Summary
+
+**Bypass formal planning for small, well-defined tasks.** Still maintains safety guarantees.
+
+### Tools Used
+
+| Tool | Purpose |
+|------|---------|
+| `goop_status` | Check current state |
+| `goop_state` | Set quick mode (NEVER edit state.json directly) |
 | `memory_search` | Find relevant prior context |
 | `memory_save` | Persist any discoveries |
+| `goop_adl` | Log the quick fix decision |
+| `goop_reference` | Load detailed process |
 
-**Hook Support:** Minimal - quick mode bypasses most phase enforcement.
+### Process Overview
 
----
+1. **Qualify** — Verify task is truly "quick" (single concern, known location)
+2. **Capture** — One-line plan, one success criterion
+3. **Execute** — Implement with atomic commit
+4. **Verify** — Confirm fix works, ask user to accept
 
-## How It Works
+### Quick Criteria
 
-Quick mode bypasses the formal Plan/Research/Specify phases while maintaining safety guarantees. Ideal for bug fixes, small refactors, or docs.
+A task qualifies for quick mode if ALL of these are true:
+- [ ] Single file OR tightly coupled files (max 3)
+- [ ] Clear, unambiguous intent
+- [ ] No architectural decisions required
+- [ ] Estimated < 15 minutes of work
+- [ ] No new dependencies needed
 
-### 1. Implicit Planning
-- Captures intent in 1 sentence.
-- Defines 1 clear success criterion.
-- Skips formal `SPEC.md`.
+## Output
 
-### 2. Rapid Execution
-- Creates a simplified 1-Wave Blueprint.
-- Executes immediately.
-- Still performs atomic commits.
+| File | Purpose |
+|------|---------|
+| Source files | Implementation |
+| Commit | Atomic change |
+| `.goopspec/ADL.md` | Quick fix logged |
 
-### 3. Quick Acceptance
-- Verifies the fix.
-- Asks for confirmation.
+## Success Criteria
 
-## When to Use
-- **Good:** "Fix the typo in the navbar", "Update dependency X", "Add a unit test".
-- **Bad:** "Add user auth", "Refactor entire API". (Use `/goop-plan` for these).
+- [ ] Quick criteria validated (5 checkboxes)
+- [ ] Intent captured in one sentence
+- [ ] Success criterion defined before execution
+- [ ] Atomic commit created
+- [ ] Fix verified working
+- [ ] User confirmed acceptance
 
-## Output
+## Anti-Patterns
 
-- Atomic commits.
-- `.goopspec/quick/` logs (for history).
+**DON'T:** Use for multi-wave work, skip verification, force complex tasks into quick mode
+**DO:** Escalate to `/goop-discuss` if scope grows, verify before declaring done, document in ADL
 
-## Example
+---
 
-> **User:** `/goop-quick Fix the z-index on the modal`
-> **Agent:** "Plan: Adjust z-index in `Modal.css`. Success: Modal appears above overlay.
-> Executing...
-> Done (commit: x9y8z7). Modal z-index set to 1000.
-> Verified. Type 'accept' to close."
+*Load `goop_reference({ name: "quick-process" })` for full process details.*