opencode-goopspec 0.1.2 → 0.1.4

package/commands/goop-amend.md

@@ -3,173 +3,57 @@ name: goop-amend
 description: Propose changes to a locked specification
 ---
 
-# GoopSpec Amend
+# /goop-amend
 
-Propose changes to a locked specification after the CONTRACT GATE.
+**Modify a locked specification.** Manage scope creep responsibly.
 
 ## Usage
 
+```bash
+/goop-amend [description of change]
 ```
-/goop-amend [change description]
-```
-
-## When to Use
-
-Use `/goop-amend` when:
-- Specification is already locked
-- Requirements have changed
-- New constraints discovered
-- Scope needs adjustment
-- User realizes something was missed
-
-**Before locking:** Just type "amend" at the CONTRACT GATE prompt.
-
-**After locking:** Use this command to propose changes.
 
-## What Happens
+## Tools Used
 
-1. **Stop Current Execution** - Pause any in-progress work
-2. **Document Change Request** - Record what needs to change and why
-3. **Assess Impact** - Analyze effect on:
-   - Completed work
-   - In-progress tasks
-   - Remaining tasks
-   - Timeline and effort
-4. **Present Options** - Show impact and alternatives
-5. **User Confirms Amendment** - Must explicitly approve
-6. **Update SPEC.md** - Modify locked specification
-7. **Update BLUEPRINT.md** - Adjust wave/task plan
-8. **Resume or Restart** - Continue execution with new spec
-
-## Amendment Types
-
-### Additive Amendment
-Adding new requirements without removing existing ones.
-
-**Example:**
-```
-/goop-amend Add OAuth login support alongside email/password
-```
+| Tool | Purpose in This Command |
+|------|------------------------|
+| `goop_status` | Check spec is locked |
+| `goop_spec` | Load current spec for amendment |
+| `goop_adl` | Log amendment decision |
+| `memory_decision` | Record amendment rationale |
 
-**Impact:** Extends scope, adds tasks, increases timeline.
+**Hook Support:** `tool.execute.after` updates spec lock state.
 
-### Subtractive Amendment
-Removing requirements to reduce scope.
+---
 
-**Example:**
-```
-/goop-amend Remove remember me feature, focus on core login
-```
+## How It Works
 
-**Impact:** Reduces scope, removes tasks, decreases timeline.
+Once a spec is locked via `/goop-specify`, it cannot be silently changed. `/goop-amend` provides a formal process to alter the contract.
 
-### Replacement Amendment
-Changing approach or swapping requirements.
+### 1. Change Request
+User proposes a change (e.g., "Add password reset button").
 
-**Example:**
-```
-/goop-amend Use session-based auth instead of JWT
-```
+### 2. Impact Analysis
+The agent analyzes the impact:
+- **Scope:** Does this add new tasks?
+- **Risk:** Does it break existing work?
+- **Timeline:** How much longer will it take?
 
-**Impact:** May require rework, affects architecture.
-
-## Amendment Process
-
-```
-User: /goop-amend Add password reset functionality
-
-Agent:
-╭─ ⬢ GoopSpec ───────────────────────────────────────╮
-│                                                    │
-│  📝 AMENDMENT REQUEST                              │
-│                                                    │
-│  PROPOSED CHANGE:                                  │
-│  Add password reset functionality                  │
-│                                                    │
-│  IMPACT ASSESSMENT:                                │
-│  • Current progress: Wave 2 of 4 (50% complete)    │
-│  • Completed work: Not affected                    │
-│  • New work required:                              │
-│    - Add password reset endpoint                   │
-│    - Email service integration                     │
-│    - Reset token management                        │
-│    - UI for reset flow                             │
-│  • Estimated additional effort: +4 hours           │
-│  • New must-have: User can reset password          │
-│                                                    │
-│  OPTIONS:                                          │
-│  1. Add to current spec (extends timeline)         │
-│  2. Defer to next phase (separate feature)         │
-│  3. Cancel amendment (keep current spec)           │
-│                                                    │
-│  ─────────────────────────────────────────────     │
-│  Type "confirm" to update spec and continue.       │
-│  Type "defer" to handle in next phase.             │
-│  Type "cancel" to keep current spec.               │
-│                                                    │
-╰────────────────────────────────────────────────────╯
-```
+### 3. Decision
+The agent presents the impact and asks for confirmation.
+- **Confirm:** Update SPEC.md and BLUEPRINT.md.
+- **Defer:** Add to a future milestone/task.
+- **Cancel:** Abort change.
 
 ## Artifacts Updated
-
-- `SPEC.md` - Updated with amendment:
-  ```markdown
-  ## Amendment History
-  
-  ### Amendment 1 - [Date]
-  **Change:** Added password reset functionality
-  **Reason:** User requirement discovered during execution
-  **Impact:** +4 hours, +1 must-have
-  ```
-
-- `BLUEPRINT.md` - Updated with new/modified tasks
-- `CHRONICLE.md` - Amendment logged with impact
-
-## Best Practices
-
-### When to Amend
-
-**GOOD reasons:**
-- Critical requirement missed
-- User needs changed
-- Technical constraint discovered
-- Security issue requires different approach
-
-**BAD reasons:**
-- "Nice to have" feature idea
-- Scope creep without justification
-- Avoiding difficult implementation
-- Perfectionism
-
-### Minimizing Amendments
-
-To reduce need for amendments:
-- Thorough planning phase
-- Clear success criteria
-- Explicit out-of-scope items
-- User confirmation at CONTRACT GATE
+- `SPEC.md`: Adds an "Amendment" entry.
+- `BLUEPRINT.md`: Adds/Removes tasks.
+- `CHRONICLE.md`: Logs the scope change.
 
 ## Example
 
-During authentication implementation, user realizes password reset is critical:
-
-```
-/goop-amend Add password reset - users need recovery option
-```
-
-Agent assesses impact, presents options, user confirms.
-SPEC.md updated, new tasks added to BLUEPRINT.md.
-
-## Next Steps
-
-After amendment confirmed:
-- `/goop-execute` - Resume execution with updated spec
-- `/goop-status` - Check updated progress
-
-If amendment deferred:
-- Continue current work
-- Plan amendment as next phase
-
----
-
-**GoopSpec**: Adapt when needed, maintain the contract.
+> **User:** `/goop-amend We need a 'Forgot Password' link`
+> **Agent:** "Impact: Adds ~2 hours. Requires new API endpoint.
+> Confirm amendment?"
+> **User:** `confirm`
+> **Agent:** "Spec updated. New tasks added to Wave 2."

package/commands/goop-complete.md

@@ -1,206 +1,62 @@
 ---
 name: goop-complete
-description: Complete and archive a milestone
+description: Complete and archive the current milestone
 ---
 
-# GoopSpec Complete
+# /goop-complete
 
-Complete and archive a milestone, extracting learnings and preparing for the next phase.
+**Complete a milestone.** Archive artifacts and extract learnings.
 
 ## Usage
 
-```
+```bash
 /goop-complete
 ```
 
-## When to Use
-
-Use `/goop-complete` when:
-- A major milestone is finished
-- Multiple features are complete
-- Ready to close a development cycle
-- Want to extract learnings before next phase
-
-**Note:** For individual features, `/goop-accept` is sufficient. Use `/goop-complete` for larger milestones.
-
-## What Happens
-
-1. **Verify Completion** - Confirm all milestone features accepted
-2. **Generate RETROSPECTIVE.md** - Reflect on what worked/didn't
-3. **Extract LEARNINGS.md** - Document patterns, decisions, insights
-4. **Archive Files** - Move to `archive/milestone-N/`:
-   - SPEC.md
-   - BLUEPRINT.md
-   - CHRONICLE.md
-   - RESEARCH.md
-   - RETROSPECTIVE.md
-   - LEARNINGS.md
-5. **Persist to Memory** - Save key learnings for future reference
-6. **Tag Git** - Create version tag (e.g., `v1.0.0`)
-7. **Clean Workspace** - Clear active workflow state
-8. **Celebrate** - Acknowledge completion
-
-## RETROSPECTIVE.md
-
-Generated retrospective includes:
-
-```markdown
-# Retrospective: [Milestone Name]
-
-**Completed:** [Date]
-**Duration:** [Time period]
-**Features Delivered:** [Count]
-
-## What Went Well
-
-- [Success 1]
-- [Success 2]
-
-## What Could Improve
-
-- [Challenge 1]
-- [Challenge 2]
-
-## Key Decisions
-
-- [Decision 1]: [Rationale]
-- [Decision 2]: [Rationale]
-
-## Metrics
-
-- Tasks completed: [N]
-- Commits: [N]
-- Tests added: [N]
-- Files modified: [N]
-- Deviations: [N]
-
-## Team Feedback
-
-[User observations and feedback]
-```
-
-## LEARNINGS.md
-
-Extracted learnings include:
-
-```markdown
-# Learnings: [Milestone Name]
-
-## Technical Patterns
-
-### Pattern 1: [Name]
-**Context:** [When to use]
-**Implementation:** [How it works]
-**Benefits:** [Why it's good]
-**Files:** [Where it's used]
+## Tools Used
 
-## Architectural Decisions
+| Tool | Purpose in This Command |
+|------|------------------------|
+| `goop_status` | Verify milestone is ready for completion |
+| `goop_adl` | Log completion decision |
+| `memory_save` | Persist milestone learnings |
+| `goop_checkpoint` | Archive milestone state |
 
-### Decision 1: [Name]
-**Problem:** [What we needed to solve]
-**Solution:** [What we chose]
-**Alternatives:** [What we didn't choose]
-**Rationale:** [Why this was best]
+**Hook Support:** `tool.execute.after` triggers archive feature.
 
-## Gotchas Discovered
-
-- [Gotcha 1]: [How to avoid]
-- [Gotcha 2]: [How to avoid]
-
-## Reusable Components
-
-- [Component 1]: [Purpose and location]
-- [Component 2]: [Purpose and location]
-
-## Future Recommendations
-
-- [Recommendation 1]
-- [Recommendation 2]
-```
-
-## Archive Structure
-
-```
-archive/
-└── milestone-1-auth-system/
-    ├── SPEC.md
-    ├── BLUEPRINT.md
-    ├── CHRONICLE.md
-    ├── RESEARCH.md
-    ├── RETROSPECTIVE.md
-    └── LEARNINGS.md
-```
+---
 
-## Memory Persistence
+## How It Works
 
-Key information saved to memory:
-- Architectural decisions
-- Reusable patterns discovered
-- Gotchas and how to avoid them
-- Performance insights
-- Security considerations
+Marks the end of a significant body of work (a Milestone). It focuses on cleanup, reflection, and memory persistence.
 
-## Git Tagging
+### 1. Archival
+Moves active artifacts (`SPEC.md`, `BLUEPRINT.md`, etc.) to `.goopspec/archive/<milestone-slug>/`.
 
-Milestone tagged in git:
+### 2. Retrospective
+Generates `RETROSPECTIVE.md` analyzing:
+- What went well?
+- What failed?
+- Metrics (Time, diff size).
 
-```bash
-git tag -a v1.0.0 -m "Milestone 1: Authentication System"
-git push origin v1.0.0
-```
+### 3. Memory Extraction
+Parses the session for reusable knowledge:
+- **Patterns:** "We used Recoil for state."
+- **Decisions:** "Chosen Redis over Memcached."
+- **Gotchas:** "Beware of circular deps in utils."
+These are saved to persistent memory.
 
-## Completion Prompt
+### 4. Tagging
+Optionally creates a git tag for the release.
 
-```
-╭─ ⬢ GoopSpec ───────────────────────────────────────╮
-│                                                    │
-│  🎯 MILESTONE COMPLETE                             │
-│                                                    │
-│  Milestone: Authentication System                  │
-│                                                    │
-│  DELIVERED:                                        │
-│  • User login/logout                               │
-│  • Session management                              │
-│  • Password reset                                  │
-│  • OAuth integration                               │
-│                                                    │
-│  METRICS:                                          │
-│  • Duration: 3 days                                │
-│  • Tasks: 24 completed                             │
-│  • Commits: 24                                     │
-│  • Tests: 87% coverage                             │
-│                                                    │
-│  ARCHIVED:                                         │
-│  • Specifications                                  │
-│  • Research findings                               │
-│  • Learnings extracted                             │
-│  • Git tagged: v1.0.0                              │
-│                                                    │
-╰────────────────────────────────────────────────────╯
-
-What's next?
-• /goop-milestone [name] - Start next milestone
-• /goop-plan [feature] - Plan next feature
-• /goop-status - Check project status
-```
+## Output
+- Archived files.
+- `RETROSPECTIVE.md`.
+- Memory updates.
 
 ## Example
-
-After completing authentication system milestone:
-
-```
-/goop-complete
-```
-
-Agent generates retrospective, extracts learnings, archives files, tags git, and prepares for next milestone.
-
-## Next Steps
-
-After completion:
-- `/goop-milestone [name]` - Start new milestone
-- `/goop-plan [feature]` - Plan next feature
-- Review LEARNINGS.md for insights
-
----
-
-**GoopSpec**: Complete with reflection, start fresh with wisdom.
+> **User:** `/goop-complete`
+> **Agent:** "Milestone 'Auth V1' archived.
+> Retrospective generated.
+> Saved 3 new patterns to memory.
+> Ready for next milestone."