opencode-goopspec 0.1.5 → 0.1.6

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.5*
-*"The spec is a contract. Lock it before you build."*
+*Load `goop_reference({ name: "specify-process" })` for full process details.*

package/commands/goop-status.md

@@ -7,293 +7,58 @@ description: Show current GoopSpec status and next steps
 
 **Show project status.** View progress, active phase, gates, and suggested next command.
 
-## Usage
+## Immediate Action
 
-```bash
-/goop-status [--verbose]
+**STOP. Execute this tool call NOW before reading anything else:**
 ```
-
-## Tools Used
-
-| Tool | Purpose in This Command |
-|------|------------------------|
-| `goop_status` | Primary tool - retrieves full workflow state |
-| `memory_search` | Optionally find recent context |
-
-**Hook Support:** None specific - read-only operation.
-
----
-
-## Process
-
-**Execute these reads:**
-
-```
-Read(".goopspec/state.json")
-Read(".goopspec/REQUIREMENTS.md")
-Read(".goopspec/SPEC.md")
-Read(".goopspec/BLUEPRINT.md")
-Read(".goopspec/CHRONICLE.md")
-Read(".goopspec/HANDOFF.md")
+goop_reference({ name: "status-process" })
 ```
 
-## Status Dashboard
-
-Display a comprehensive status view:
-
-```
-+--------------------------------------------------------+
-|  GOOPSPEC STATUS                                        |
-+--------------------------------------------------------+
-
-## Project State
-
-| Attribute | Value |
-|-----------|-------|
-| Phase | [current phase] |
-| Interview Complete | [Yes/No] |
-| Spec Locked | [Yes/No] |
-| Wave | [N of M] |
-| Task | [X of Y] |
-
-## Gate Status
-
-| Gate | Status | Requirement |
-|------|--------|-------------|
-| Discovery | [PASSED/BLOCKED] | interview_complete |
-| Spec | [PASSED/BLOCKED] | spec_locked |
-| Execution | [PASSED/BLOCKED] | all_tasks_done |
-| Acceptance | [PASSED/BLOCKED] | verification_passed |
-
-## Progress
-
-[Progress bar and completion percentage]
-
-### Completed
-- [x] [Item 1]
-- [x] [Item 2]
-
-### In Progress
-- [ ] [Current item] <- **Current**
+**Then display the status dashboard from that reference.** Do not process user messages until you have loaded and understood the protocol.
 
-### Remaining
-- [ ] [Item 3]
-- [ ] [Item 4]
+## Quick Summary
 
-## Active Blockers
+Read-only operation that shows current workflow state.
 
-[None | List of blockers]
+### Tools Used
 
-## Pending Decisions
-
-[None | List of decisions awaiting user input]
-
-## Recent Activity
-
-| Time | Action | Agent |
-|------|--------|-------|
-| [time] | [action] | [agent] |
-
-+--------------------------------------------------------+
-
-## > Suggested Next Command
-
-Based on current state: `/goop-[command]`
-
-[Brief explanation of why this is suggested]
-
-+--------------------------------------------------------+
-```
+| Tool | Purpose |
+|------|---------|
+| `goop_status` | Primary tool - retrieves full workflow state |
+| `memory_search` | Optionally find recent context |
+| `goop_reference` | Load detailed display templates |
 
-## Information Sources
+### Data Sources
 
 | Source | Information |
 |--------|-------------|
-| `state.json` | Phase, locks, timestamps |
+| `goop_state` | Phase, locks, timestamps |
 | `REQUIREMENTS.md` | Interview status |
 | `SPEC.md` | Must-haves, lock status |
 | `BLUEPRINT.md` | Waves, tasks, traceability |
 | `CHRONICLE.md` | Progress, decisions, blockers |
 | `HANDOFF.md` | Last session context |
 
-## Gate Logic
+### Command Suggestions
 
-### Discovery Gate
-```
-IF REQUIREMENTS.md exists AND interview_complete == true:
-  PASSED
-ELSE:
-  BLOCKED - Run /goop-discuss
-```
-
-### Spec Gate
-```
-IF SPEC.md exists AND spec_locked == true:
-  PASSED
-ELSE:
-  BLOCKED - Run /goop-specify
-```
-
-### Execution Gate
-```
-IF CHRONICLE shows all waves complete:
-  PASSED
-ELSE:
-  BLOCKED - Continue /goop-execute
-```
-
-### Acceptance Gate
-```
-IF verification_passed == true AND user_accepted == true:
-  PASSED
-ELSE:
-  BLOCKED - Run /goop-accept
-```
-
-## Suggested Commands
-
-Based on current state, suggest the appropriate next command:
-
-| State | Suggested Command |
-|-------|-------------------|
-| No project | `/goop-discuss` to start discovery |
-| Interview incomplete | `/goop-discuss` to complete interview |
-| Interview complete, no spec | `/goop-plan` to create blueprint |
-| Spec draft, not locked | `/goop-specify` to lock |
-| Spec locked, not executing | `/goop-execute` to start |
-| Executing, tasks remaining | `/goop-execute` to continue |
-| Executing, all done | `/goop-accept` to verify |
-| Verified, not accepted | `/goop-accept` to accept |
-| Accepted | `/goop-complete` to archive |
-
-## Verbose Mode
-
-With `--verbose`:
-
-```
-## Full Task History
-
-| Wave | Task | Status | Commit | Time |
-|------|------|--------|--------|------|
-| 1 | 1.1 | Complete | abc123 | 10m |
-| 1 | 1.2 | Complete | def456 | 15m |
-| 2 | 2.1 | In Progress | - | - |
-
-## Memory Stats
-
-- Total memories: [N]
-- Decisions: [M]
-- Observations: [P]
-- Recent: [list]
-
-## Recent Deviations
-
-| Rule | Description | Resolution |
-|------|-------------|------------|
-| [N] | [What happened] | [How resolved] |
-
-## Checkpoint History
-
-| ID | Phase | Wave | Created |
-|----|-------|------|---------|
-| [id] | [phase] | [wave] | [time] |
-```
-
-## Examples
-
-**Fresh Project:**
-```
-User: /goop-status
-
-+--------------------------------------------------------+
-|  GOOPSPEC STATUS                                        |
-+--------------------------------------------------------+
-
-## Project State
-
-| Attribute | Value |
-|-----------|-------|
-| Phase | idle |
-| Interview Complete | No |
-| Spec Locked | No |
-
-## Gate Status
-
-| Gate | Status |
-|------|--------|
-| Discovery | BLOCKED |
-| Spec | BLOCKED |
-| Execution | BLOCKED |
-| Acceptance | BLOCKED |
-
-## > Suggested Next Command
-
-`/goop-discuss` - Start discovery interview
-
-No project documents found. Begin with discovery.
-```
-
-**Mid-Execution:**
-```
-User: /goop-status
-
-+--------------------------------------------------------+
-|  GOOPSPEC STATUS                                        |
-+--------------------------------------------------------+
-
-## Project State
-
-| Attribute | Value |
-|-----------|-------|
-| Phase | execute |
-| Interview Complete | Yes |
-| Spec Locked | Yes |
-| Wave | 2 of 3 |
-| Task | 3 of 4 |
-
-## Gate Status
-
-| Gate | Status |
-|------|--------|
-| Discovery | PASSED |
-| Spec | PASSED |
-| Execution | In Progress |
-| Acceptance | Pending |
-
-## Progress
-
-[################____] 75%
-
-### Completed
-- [x] Wave 1: Foundation (4/4 tasks)
-- [x] Wave 2.1: Define types
-- [x] Wave 2.2: Implement handler
-
-### In Progress
-- [ ] Wave 2.3: Add validation <- **Current**
-
-### Remaining
-- [ ] Wave 2.4: Add tests
-- [ ] Wave 3: Integration (3 tasks)
-
-## > Suggested Next Command
-
-`/goop-execute` - Continue Wave 2
-
-2 tasks remaining in Wave 2, then Wave 3.
-```
+| State | Suggested |
+|-------|-----------|
+| No project | `/goop-discuss` |
+| Interview incomplete | `/goop-discuss` |
+| Interview done, no spec | `/goop-plan` |
+| Spec draft | `/goop-specify` |
+| Spec locked | `/goop-execute` |
+| Executing | `/goop-execute` |
+| All tasks done | `/goop-accept` |
+| Accepted | `/goop-complete` |
 
 ## Success Criteria
 
-- [ ] All state files read
 - [ ] Phase correctly identified
 - [ ] Gate status accurately shown
 - [ ] Progress clearly displayed
-- [ ] Blockers highlighted
 - [ ] Next command suggested based on state
-- [ ] Verbose mode shows full history
 
 ---
 
-*Status Protocol v0.1.5*
-*"Know where you are. Know where to go."*
+*Load `goop_reference({ name: "status-process" })` for full display templates.*