opencode-goopspec 0.1.2 → 0.1.3

package/commands/goop-specify.md

@@ -1,145 +1,69 @@
 ---
 name: goop-specify
-description: Lock the specification - the CONTRACT between user and agent
+description: Lock the specification contract
+phase: specify
+next-step: "Once the spec is locked and confirmed, begin implementation"
+next-command: /goop-execute
+alternatives:
+  - command: /goop-amend
+    when: "If you need to modify the locked specification"
+  - command: /goop-pause
+    when: "To save progress and continue later"
 ---
 
-# GoopSpec Specify
+# /goop-specify
 
-Lock the specification - the binding contract that defines exactly what will be delivered.
+**Lock the specification.** Create a binding contract between user and agent.
 
 ## Usage
 
-```
-/goop-specify
-```
-
-## Workflow Position
-
-```
-┌─────────────┐     ┌─────────────┐     ┌─────────────┐
-│    PLAN     │ ──▶ │  RESEARCH   │ ──▶ │   SPECIFY   │
-│  (Intent)   │     │  (Explore)  │     │ (Contract)  │
-└─────────────┘     └─────────────┘     └─────────────┘
-                                              ↑
-                                        (You are here)
-
-       ╔══════════════════════════════════════════════╗
-       ║          CONTRACT GATE                        ║
-       ║   User MUST confirm before execution begins   ║
-       ╚══════════════════════════════════════════════╝
-```
-
-The Specify phase answers: **What exactly will we deliver?**
-
-## What Happens
-
-1. **Synthesize Plan + Research** - Combine intent with technical approach
-2. **Define Must-Haves** - Observable, achievable, specific deliverables (3-7 items)
-3. **Set Boundaries** - Explicitly state what's out of scope
-4. **Create SPEC.md** - The locked specification document
-5. **Create BLUEPRINT.md** - Wave-based execution plan
-6. **Present Contract** - Show must-haves, nice-to-haves, out-of-scope
-7. **Wait for Confirmation** - User MUST type "confirm" to proceed
-
-## The Contract Concept
-
-Once locked, the specification becomes a binding agreement:
-- **Agent commits** to delivering must-haves
-- **User commits** to accepting if must-haves are met
-- **Changes require** explicit amendment via `/goop-amend`
-
-### Why Contracts Matter
-
-**Without a locked spec:**
-- Scope creeps silently
-- "Almost done" never ends
-- Success criteria shift
-- Both parties frustrated
-
-**With a locked spec:**
-- Clear deliverables
-- Measurable completion
-- Explicit change process
-- Satisfied expectations
-
-## Artifacts Created
-
-- `SPEC.md` - Locked specification with:
-  - Intent summary
-  - Must-haves (guaranteed)
-  - Nice-to-haves (best effort)
-  - Out-of-scope (explicitly excluded)
-  - Technical approach
-  - Target files
-  - Acceptance criteria
-
-- `BLUEPRINT.md` - Wave-based execution plan with:
-  - Wave 1: Foundation tasks
-  - Wave 2: Core tasks
-  - Wave 3: Integration tasks
-  - Wave 4: Polish tasks
-
-## Confirmation Prompt
-
-```
-╭─ ⬢ GoopSpec ───────────────────────────────────────╮
-│                                                    │
-│  🔒 CONTRACT GATE                                  │
-│                                                    │
-│  I'm ready to lock the specification.              │
-│                                                    │
-│  MUST HAVES (I commit to delivering):              │
-│  • User can log in with email/password             │
-│  • Session persists across refresh                 │
-│  • Error messages displayed                        │
-│                                                    │
-│  NICE TO HAVES (Best effort):                      │
-│  • Remember me option                              │
-│                                                    │
-│  OUT OF SCOPE:                                     │
-│  • OAuth providers (future enhancement)            │
-│  • Password reset (separate feature)               │
-│                                                    │
-│  ACCEPTANCE CRITERIA:                              │
-│  1. User can successfully log in                   │
-│  2. Tests pass for auth flow                       │
-│  3. Session management works                       │
-│                                                    │
-│  ─────────────────────────────────────────────     │
-│  Type "confirm" to lock and proceed.               │
-│  Type "amend" to request changes.                  │
-│                                                    │
-╰────────────────────────────────────────────────────╯
-```
-
-## Example
-
-After research on authentication:
-
-```
+```bash
 /goop-specify
 ```
 
-Agent creates SPEC.md and BLUEPRINT.md, then presents contract for confirmation.
-
-## Next Steps
-
-After confirmation:
-- `/goop-execute` - Start wave-based implementation
-
-If changes needed:
-- Type "amend" to modify specification before locking
-
-After locking:
-- `/goop-amend [change]` - Propose changes to locked spec
-
-## Quick Mode Shortcut
-
-For Quick tasks, Specify phase is **SKIPPED**:
-- Intent from Plan phase serves as implicit spec
-- No formal SPEC.md
-- Jumps directly to Execute
-
----
-
-**GoopSpec**: Lock the contract, deliver with confidence.
+## How It Works
+
+This command marks the transition from planning to commitment. It generates the `SPEC.md` and `BLUEPRINT.md` files and presents them for user confirmation.
+
+### 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).
+
+### 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.
+
+### 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.
+
+## 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.

package/commands/goop-status.md

@@ -1,153 +1,51 @@
 ---
 name: goop-status
-description: Show GoopSpec status and progress
+description: Show current GoopSpec status
 ---
 
-# GoopSpec Status
+# /goop-status
 
-Display the current status of your GoopSpec project and workflow progress.
+**Show project status.** View progress, active phase, and pending tasks.
 
 ## Usage
 
+```bash
+/goop-status [--verbose]
 ```
-/goop-status
-```
-
-## Information Shown
-
-### Project State
-- Initialized: Yes/No
-- Active: Yes/No
-- Current milestone (if any)
-- Task mode: Quick | Standard | Comprehensive | Milestone
-
-### Current Workflow
-- Phase: Plan | Research | Specify | Execute | Accept
-- Spec locked: Yes/No
-- Acceptance confirmed: Yes/No
-- Last activity timestamp
 
-### Execution Progress (if in Execute phase)
-- Current wave: N of M
-- Tasks completed in current wave
-- Total tasks completed
-- Recent commits
+## How It Works
 
-### Contract Status
-- Specification locked at: [timestamp]
-- Must-haves: N total
-- Must-haves completed: N of M
-- Nice-to-haves completed: N of M
+Displays a dashboard of the current GoopSpec session.
 
-### Checkpoints
-- Total checkpoints saved
-- Latest checkpoint info
-- Resume available: Yes/No
+### Information Shown
+- **Project State:** Initialized? Active Milestone?
+- **Current Phase:** Discuss, Plan, Research, Specify, Execute, or Accept.
+- **Progress:** Wave completion (e.g., "Wave 2 of 4").
+- **Task Status:** Current active task and recent completions.
+- **Gates:** Spec locked? Acceptance pending?
 
-### Memory Stats
-- Decisions logged: N
-- Observations saved: N
-- Patterns documented: N
+### Interactive Actions
+From the status view, the agent often suggests the logical next command (e.g., "Execution complete. Run `/goop-accept` to verify.").
 
 ## Example Output
 
 ```
-⬢ GoopSpec · Status
-──────────────────────────────────────────────────────
-
-Project: Initialized ✓
-Mode: Standard
-Milestone: Authentication System
-
-WORKFLOW:
-Phase: Execute (Wave 2 of 4)
-Spec Locked: Yes (2024-01-15 10:30)
-Acceptance: Pending
-
-PROGRESS:
-Wave 1: Foundation [COMPLETE] ✓
-  ☑ Task 1.1: Setup
-  ☑ Task 1.2: Config
-  ☑ Task 1.3: Base
-
-Wave 2: Core [IN PROGRESS]
-  ☑ Task 2.1: Auth
-  ◉ Task 2.2: Logic
-  ○ Task 2.3: Data
-
-Wave 3: Integration [PENDING]
-Wave 4: Polish [PENDING]
-
-MUST-HAVES: 2 of 3 complete
-☑ User can log in
-☑ Session persists
-○ Error messages displayed
-
-CHECKPOINTS: 2 saved
-Latest: checkpoint-xyz789 (30 mins ago)
-
-MEMORY: 5 decisions, 12 observations
-
-──────────────────────────────────────────────────────
+⬢ GoopSpec Status
+─────────────────
+Phase:    EXECUTE (Wave 2/4)
+Task:     [2.1] Implement Login Handler (In Progress)
+Milestone: Auth System v1
+
+Progress:
+[✓] Wave 1: Foundation
+[→] Wave 2: Core Logic
+    [✓] 2.1 Define types
+    [→] 2.2 Implement handler
+    [ ] 2.3 Add tests
+[ ] Wave 3: Integration
+
+Next: Finish Task 2.2
 ```
 
-## Phase-Specific Information
-
-### Plan Phase
-- Intent captured: Yes/No
-- Requirements categorized: Yes/No
-- Success criteria defined: Yes/No
-- Ready for research: Yes/No
-
-### Research Phase
-- Agents spawned: N
-- Research complete: Yes/No
-- RESEARCH.md created: Yes/No
-- Ready for specify: Yes/No
-
-### Specify Phase
-- SPEC.md created: Yes/No
-- BLUEPRINT.md created: Yes/No
-- Contract presented: Yes/No
-- User confirmed: Yes/No
-
-### Execute Phase
-- Current wave: N of M
-- Tasks complete: N of M
-- Deviations: N logged
-- Blockers: N active
-
-### Accept Phase
-- Verification complete: Yes/No
-- Must-haves verified: N of M
-- Tests passing: Yes/No
-- User accepted: Yes/No
-
-## Quick Actions
-
-From status view, you can:
-- `/goop-plan [intent]` - Start planning
-- `/goop-research` - Begin research
-- `/goop-specify` - Lock specification
-- `/goop-execute` - Continue execution
-- `/goop-accept` - Verify completion
-- `/goop-pause` - Save checkpoint
-- `/goop-resume` - Resume from checkpoint
-
-## Verbose Mode
-
-For detailed status:
-
-```
-/goop-status --verbose
-```
-
-Shows additional information:
-- Full task list with commit hashes
-- All deviations with details
-- Complete checkpoint history
-- Memory entries related to current work
-
----
-
-**GoopSpec**: Know exactly where you stand.
+## Flags
+- `--verbose`: Show full task history, memory stats, and recent deviations.