opencode-goopspec 0.1.2 → 0.1.3

package/commands/goop-map-codebase.md

@@ -15,7 +15,7 @@ Map an existing codebase for brownfield projects.
 
 Analyzes codebase with parallel Explore agents. Creates `.goopspec/codebase/` with 7 focused documents covering stack, architecture, structure, conventions, testing, integrations, and concerns.
 
-Use before `/goop-new` on existing codebases. Provides the context needed to extend rather than replace.
+Use before `/goop-setup` on existing codebases. Provides the context needed to extend rather than replace.
 
 **Creates:**
 - `.goopspec/codebase/STACK.md` - Technology stack
@@ -429,7 +429,7 @@ OPTIONAL_VAR=[description]
 
 ## Phase 5: Update State
 
-Update STATE.md:
+Update `.goopspec/state.json`:
 - Mark codebase as mapped
 - Add timestamp
 - Link to codebase docs
@@ -467,7 +467,7 @@ Created in .goopspec/codebase/:
 
 **Initialize GoopSpec project** with brownfield context
 
-/goop-new [project-name]
+/goop-setup
 
 <sub>Will use codebase map to understand existing code</sub>
 

package/commands/goop-milestone.md

@@ -3,211 +3,35 @@ name: goop-milestone
 description: Start a new milestone
 ---
 
-# GoopSpec Milestone
+# /goop-milestone
 
-Start a new milestone - a major development cycle with multiple related features.
+**Manage project milestones.** Group features into a larger goal.
 
 ## Usage
 
+```bash
+/goop-milestone [start|status|list] [name]
 ```
-/goop-milestone [milestone name]
-```
-
-## What is a Milestone?
-
-A milestone is a collection of related features that together deliver significant value:
-
-**Examples:**
-- "Authentication System" (login, logout, password reset, OAuth)
-- "Payment Integration" (checkout, subscriptions, invoices)
-- "Admin Dashboard" (user management, analytics, settings)
-- "Mobile App" (iOS/Android apps with core features)
-
-**Not milestones:**
-- Single features (use `/goop-plan` instead)
-- Bug fixes (use `/goop-quick` instead)
-- Small enhancements (use `/goop-plan` instead)
-
-## What Happens
-
-1. **Milestone Planning** - Define scope and features:
-   - Milestone objectives
-   - Feature list
-   - Success criteria
-   - Timeline estimate
-
-2. **Create Milestone Structure**:
-   ```
-   .goopspec/
-   └── milestones/
-       └── milestone-1-auth-system/
-           ├── MILESTONE.md
-           ├── features/
-           │   ├── feature-1-login/
-           │   ├── feature-2-password-reset/
-           │   └── feature-3-oauth/
-           └── shared/
-   ```
-
-3. **Feature Breakdown** - Identify individual features within milestone
-
-4. **Dependency Mapping** - Determine feature order and dependencies
-
-5. **User Confirmation** - Confirm milestone scope before starting
-
-## MILESTONE.md Structure
-
-```markdown
-# Milestone: [Name]
-
-**Status:** Active | Complete
-**Started:** [Date]
-**Target:** [Date]
-**Progress:** [N/M features complete]
-
-## Objectives
 
-[What this milestone achieves]
+## How It Works
 
-## Features
+Milestones are containers for multiple features/tasks. They help track progress towards a larger release.
 
-### Feature 1: [Name]
-**Status:** Planned | In Progress | Complete
-**Dependencies:** None
-**Estimated Effort:** [Size]
+### Commands
+- `/goop-milestone start "v1.0 Release"`: Begin a new milestone.
+- `/goop-milestone status`: Show milestone progress (burndown).
+- `/goop-milestone list`: Show history.
 
-### Feature 2: [Name]
-**Status:** Planned
-**Dependencies:** Feature 1
-**Estimated Effort:** [Size]
+### Workflow
+1. **Start:** Define the milestone goal.
+2. **Execute:** Run multiple `/goop-plan` -> `/goop-execute` cycles within the milestone.
+3. **Track:** Aggregates status across all contained features.
+4. **Complete:** Run `/goop-complete` to finish the milestone.
 
-## Success Criteria
-
-- [ ] Criterion 1
-- [ ] Criterion 2
-
-## Timeline
-
-- Week 1: Features 1-2
-- Week 2: Features 3-4
-- Week 3: Integration and polish
-
-## Notes
-
-[Important context, constraints, decisions]
-```
-
-## Milestone Workflow
-
-```
-/goop-milestone [name]
-    ↓
-Plan milestone scope
-    ↓
-Break into features
-    ↓
-For each feature:
-    /goop-plan → /goop-research → /goop-specify → /goop-execute → /goop-accept
-    ↓
-/goop-complete (archive milestone)
-```
-
-## Task Modes
-
-Milestones use **Comprehensive Mode**:
-- Deeper research per feature
-- More thorough planning
-- Extended verification
-- Formal retrospectives
+## Artifacts
+- `.goopspec/MILESTONE.md`: Tracks overall progress and contained features.
 
 ## Example
-
-Starting authentication system milestone:
-
-```
-/goop-milestone Authentication System
-```
-
-Agent creates:
-- MILESTONE.md with objectives
-- Feature breakdown:
-  - Feature 1: Email/password login
-  - Feature 2: Session management
-  - Feature 3: Password reset
-  - Feature 4: OAuth integration
-- Dependency map
-- Timeline estimate
-
-User confirms scope, then proceeds feature by feature.
-
-## Milestone Tracking
-
-Track progress with:
-
-```
-/goop-status
-```
-
-Shows:
-- Current milestone
-- Features complete/in-progress/planned
-- Overall progress percentage
-- Estimated completion
-
-## Milestone Completion
-
-When all features complete:
-
-```
-/goop-complete
-```
-
-This:
-- Archives milestone files
-- Generates retrospective
-- Extracts learnings
-- Tags git version
-- Prepares for next milestone
-
-## Best Practices
-
-### Good Milestone Scope
-
-**Right size:**
-- 3-8 related features
-- 1-4 weeks of work
-- Clear theme/objective
-- Delivers user value
-
-**Too small:**
-- Single feature (use `/goop-plan`)
-- < 1 week work
-- No clear theme
-
-**Too large:**
-- > 10 features
-- > 1 month work
-- Multiple unrelated areas
-- Split into multiple milestones
-
-### Milestone Planning
-
-1. **Start with objectives** - What value does this deliver?
-2. **List features** - What's needed to achieve objectives?
-3. **Map dependencies** - What order makes sense?
-4. **Estimate effort** - How long will this take?
-5. **Get confirmation** - Does user agree with scope?
-
-## Next Steps
-
-After milestone started:
-- `/goop-plan [feature]` - Plan first feature
-- `/goop-status` - Check milestone progress
-
-After milestone complete:
-- `/goop-milestone [next]` - Start next milestone
-- Review RETROSPECTIVE.md for insights
-
----
-
-**GoopSpec**: Think in milestones, deliver in features.
+> **User:** `/goop-milestone start "User Dashboard"`
+> **Agent:** "Milestone 'User Dashboard' started.
+> Plan your first feature with `/goop-plan`."

package/commands/goop-pause.md

@@ -1,61 +1,40 @@
 ---
 name: goop-pause
-description: Save a checkpoint to pause work
+description: Save a checkpoint and pause work
 ---
 
-# GoopSpec Pause (Checkpoint)
+# /goop-pause
 
-Save your current progress as a checkpoint that you can resume later.
+**Pause work and save state.** Create a resumption checkpoint.
 
 ## Usage
 
-```
-/goop-pause [checkpoint-name]
+```bash
+/goop-pause [optional message]
 ```
 
-## What Gets Saved
+## How It Works
 
-A checkpoint captures:
-- Current session ID
-- Current phase and spec
-- Incomplete todos
-- Modified files
-- Git commit hash
-- Timestamp
+Safely stops the current workflow and saves a snapshot of the context. This allows you to switch tasks or end your session without losing "brain state."
 
-## Storage
+### What is Saved?
+- **Workflow State:** Phase, Wave, active Plan/Spec.
+- **Task Context:** Which task was active.
+- **Memory Buffer:** Short-term observations not yet persisted.
+- **Git State:** Current branch and status.
 
-Checkpoints are saved to:
-`.goopspec/checkpoints/checkpoint-{id}.json`
+### When to Use
+- Ending a work session.
+- Switching to a different urgent task.
+- Before a risky manual experiment.
 
-## Auto-Cleanup
+## Output
 
-Old checkpoints are automatically cleaned up (configurable limit, default 10).
+- Saves a checkpoint file (JSON) in `.goopspec/checkpoints/`.
+- Confirms the checkpoint ID for resumption.
 
 ## Example
 
-```
-/goop-pause "Before major refactor"
-```
-
-## Resume Later
-
-To resume from this checkpoint:
-```
-/goop-resume [checkpoint-id]
-```
-
-Or resume the latest:
-```
-/goop-resume
-```
-
-## Use Cases
-
-- End of work day - save and resume tomorrow
-- Before experimental changes - save as backup
-- Context switching - pause one task, work on another
-
----
-
-**GoopSpec**: Never lose your place.
+> **User:** `/goop-pause Heading to lunch`
+> **Agent:** "Checkpoint `cp-123` saved. 'Heading to lunch'.
+> Run `/goop-resume` to pick up exactly here."