opencode-goopspec 0.1.2 → 0.1.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +255 -331
- package/agents/goop-debugger.md +175 -172
- package/agents/goop-designer.md +232 -160
- package/agents/goop-executor.md +197 -127
- package/agents/goop-explorer.md +148 -150
- package/agents/goop-librarian.md +218 -164
- package/agents/goop-orchestrator.md +392 -280
- package/agents/goop-planner.md +331 -153
- package/agents/goop-researcher.md +198 -126
- package/agents/goop-tester.md +277 -202
- package/agents/goop-verifier.md +191 -201
- package/agents/goop-writer.md +241 -133
- package/agents/memory-distiller.md +228 -136
- package/commands/goop-accept.md +434 -160
- package/commands/goop-amend.md +35 -151
- package/commands/goop-complete.md +39 -183
- package/commands/goop-debug.md +33 -298
- package/commands/goop-discuss.md +381 -85
- package/commands/goop-execute.md +391 -108
- package/commands/goop-help.md +11 -0
- package/commands/goop-map-codebase.md +16 -3
- package/commands/goop-memory.md +11 -0
- package/commands/goop-milestone.md +29 -192
- package/commands/goop-pause.md +31 -40
- package/commands/goop-plan.md +458 -46
- package/commands/goop-quick.md +38 -142
- package/commands/goop-recall.md +11 -0
- package/commands/goop-remember.md +12 -0
- package/commands/goop-research.md +52 -73
- package/commands/goop-resume.md +28 -37
- package/commands/goop-setup.md +225 -124
- package/commands/goop-specify.md +321 -121
- package/commands/goop-status.md +256 -110
- package/dist/index.js +6289 -2820
- package/package.json +1 -1
- package/references/context-injection.md +307 -0
- package/references/discovery-interview.md +278 -0
- package/references/enforcement-system.md +213 -0
- package/references/handoff-protocol.md +290 -0
- package/references/interactive-questioning.md +122 -0
- package/references/model-profiles.md +1 -1
- package/references/phase-gates.md +360 -0
- package/references/plugin-architecture.md +212 -0
- package/references/response-format.md +41 -9
- package/references/subagent-protocol.md +83 -33
- package/references/ui-interaction-patterns.md +133 -0
- package/references/visual-style.md +199 -0
- package/references/workflow-accept.md +60 -273
- package/references/workflow-execute.md +63 -274
- package/references/workflow-plan.md +86 -133
- package/references/workflow-research.md +78 -186
- package/references/workflow-specify.md +64 -221
- package/references/xml-response-schema.md +236 -0
- package/templates/blueprint.md +88 -41
- package/templates/chronicle.md +130 -16
- package/templates/handoff.md +140 -0
- package/templates/project.md +114 -0
- package/templates/requirements.md +121 -0
- package/templates/spec.md +85 -20
- package/templates/state.md +103 -0
|
@@ -3,211 +3,48 @@ name: goop-milestone
|
|
|
3
3
|
description: Start a new milestone
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
#
|
|
6
|
+
# /goop-milestone
|
|
7
7
|
|
|
8
|
-
|
|
8
|
+
**Manage project milestones.** Group features into a larger goal.
|
|
9
9
|
|
|
10
10
|
## Usage
|
|
11
11
|
|
|
12
|
+
```bash
|
|
13
|
+
/goop-milestone [start|status|list] [name]
|
|
12
14
|
```
|
|
13
|
-
/goop-milestone [milestone name]
|
|
14
|
-
```
|
|
15
|
-
|
|
16
|
-
## What is a Milestone?
|
|
17
|
-
|
|
18
|
-
A milestone is a collection of related features that together deliver significant value:
|
|
19
|
-
|
|
20
|
-
**Examples:**
|
|
21
|
-
- "Authentication System" (login, logout, password reset, OAuth)
|
|
22
|
-
- "Payment Integration" (checkout, subscriptions, invoices)
|
|
23
|
-
- "Admin Dashboard" (user management, analytics, settings)
|
|
24
|
-
- "Mobile App" (iOS/Android apps with core features)
|
|
25
|
-
|
|
26
|
-
**Not milestones:**
|
|
27
|
-
- Single features (use `/goop-plan` instead)
|
|
28
|
-
- Bug fixes (use `/goop-quick` instead)
|
|
29
|
-
- Small enhancements (use `/goop-plan` instead)
|
|
30
|
-
|
|
31
|
-
## What Happens
|
|
32
|
-
|
|
33
|
-
1. **Milestone Planning** - Define scope and features:
|
|
34
|
-
- Milestone objectives
|
|
35
|
-
- Feature list
|
|
36
|
-
- Success criteria
|
|
37
|
-
- Timeline estimate
|
|
38
|
-
|
|
39
|
-
2. **Create Milestone Structure**:
|
|
40
|
-
```
|
|
41
|
-
.goopspec/
|
|
42
|
-
└── milestones/
|
|
43
|
-
└── milestone-1-auth-system/
|
|
44
|
-
├── MILESTONE.md
|
|
45
|
-
├── features/
|
|
46
|
-
│ ├── feature-1-login/
|
|
47
|
-
│ ├── feature-2-password-reset/
|
|
48
|
-
│ └── feature-3-oauth/
|
|
49
|
-
└── shared/
|
|
50
|
-
```
|
|
51
|
-
|
|
52
|
-
3. **Feature Breakdown** - Identify individual features within milestone
|
|
53
|
-
|
|
54
|
-
4. **Dependency Mapping** - Determine feature order and dependencies
|
|
55
|
-
|
|
56
|
-
5. **User Confirmation** - Confirm milestone scope before starting
|
|
57
|
-
|
|
58
|
-
## MILESTONE.md Structure
|
|
59
|
-
|
|
60
|
-
```markdown
|
|
61
|
-
# Milestone: [Name]
|
|
62
|
-
|
|
63
|
-
**Status:** Active | Complete
|
|
64
|
-
**Started:** [Date]
|
|
65
|
-
**Target:** [Date]
|
|
66
|
-
**Progress:** [N/M features complete]
|
|
67
15
|
|
|
68
|
-
##
|
|
16
|
+
## Tools Used
|
|
69
17
|
|
|
70
|
-
|
|
18
|
+
| Tool | Purpose in This Command |
|
|
19
|
+
|------|------------------------|
|
|
20
|
+
| `goop_status` | Check current milestone state |
|
|
21
|
+
| `goop_adl` | Log milestone start/completion |
|
|
22
|
+
| `memory_search` | Find prior milestone context |
|
|
23
|
+
| `goop_checkpoint` | Save milestone boundaries |
|
|
71
24
|
|
|
72
|
-
|
|
25
|
+
**Hook Support:** `tool.execute.after` tracks milestone transitions.
|
|
73
26
|
|
|
74
|
-
|
|
75
|
-
**Status:** Planned | In Progress | Complete
|
|
76
|
-
**Dependencies:** None
|
|
77
|
-
**Estimated Effort:** [Size]
|
|
78
|
-
|
|
79
|
-
### Feature 2: [Name]
|
|
80
|
-
**Status:** Planned
|
|
81
|
-
**Dependencies:** Feature 1
|
|
82
|
-
**Estimated Effort:** [Size]
|
|
83
|
-
|
|
84
|
-
## Success Criteria
|
|
85
|
-
|
|
86
|
-
- [ ] Criterion 1
|
|
87
|
-
- [ ] Criterion 2
|
|
88
|
-
|
|
89
|
-
## Timeline
|
|
90
|
-
|
|
91
|
-
- Week 1: Features 1-2
|
|
92
|
-
- Week 2: Features 3-4
|
|
93
|
-
- Week 3: Integration and polish
|
|
94
|
-
|
|
95
|
-
## Notes
|
|
27
|
+
---
|
|
96
28
|
|
|
97
|
-
|
|
98
|
-
```
|
|
29
|
+
## How It Works
|
|
99
30
|
|
|
100
|
-
|
|
31
|
+
Milestones are containers for multiple features/tasks. They help track progress towards a larger release.
|
|
101
32
|
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
↓
|
|
107
|
-
Break into features
|
|
108
|
-
↓
|
|
109
|
-
For each feature:
|
|
110
|
-
/goop-plan → /goop-research → /goop-specify → /goop-execute → /goop-accept
|
|
111
|
-
↓
|
|
112
|
-
/goop-complete (archive milestone)
|
|
113
|
-
```
|
|
33
|
+
### Commands
|
|
34
|
+
- `/goop-milestone start "v1.0 Release"`: Begin a new milestone.
|
|
35
|
+
- `/goop-milestone status`: Show milestone progress (burndown).
|
|
36
|
+
- `/goop-milestone list`: Show history.
|
|
114
37
|
|
|
115
|
-
|
|
38
|
+
### Workflow
|
|
39
|
+
1. **Start:** Define the milestone goal.
|
|
40
|
+
2. **Execute:** Run multiple `/goop-plan` -> `/goop-execute` cycles within the milestone.
|
|
41
|
+
3. **Track:** Aggregates status across all contained features.
|
|
42
|
+
4. **Complete:** Run `/goop-complete` to finish the milestone.
|
|
116
43
|
|
|
117
|
-
|
|
118
|
-
-
|
|
119
|
-
- More thorough planning
|
|
120
|
-
- Extended verification
|
|
121
|
-
- Formal retrospectives
|
|
44
|
+
## Artifacts
|
|
45
|
+
- `.goopspec/MILESTONE.md`: Tracks overall progress and contained features.
|
|
122
46
|
|
|
123
47
|
## Example
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
```
|
|
128
|
-
/goop-milestone Authentication System
|
|
129
|
-
```
|
|
130
|
-
|
|
131
|
-
Agent creates:
|
|
132
|
-
- MILESTONE.md with objectives
|
|
133
|
-
- Feature breakdown:
|
|
134
|
-
- Feature 1: Email/password login
|
|
135
|
-
- Feature 2: Session management
|
|
136
|
-
- Feature 3: Password reset
|
|
137
|
-
- Feature 4: OAuth integration
|
|
138
|
-
- Dependency map
|
|
139
|
-
- Timeline estimate
|
|
140
|
-
|
|
141
|
-
User confirms scope, then proceeds feature by feature.
|
|
142
|
-
|
|
143
|
-
## Milestone Tracking
|
|
144
|
-
|
|
145
|
-
Track progress with:
|
|
146
|
-
|
|
147
|
-
```
|
|
148
|
-
/goop-status
|
|
149
|
-
```
|
|
150
|
-
|
|
151
|
-
Shows:
|
|
152
|
-
- Current milestone
|
|
153
|
-
- Features complete/in-progress/planned
|
|
154
|
-
- Overall progress percentage
|
|
155
|
-
- Estimated completion
|
|
156
|
-
|
|
157
|
-
## Milestone Completion
|
|
158
|
-
|
|
159
|
-
When all features complete:
|
|
160
|
-
|
|
161
|
-
```
|
|
162
|
-
/goop-complete
|
|
163
|
-
```
|
|
164
|
-
|
|
165
|
-
This:
|
|
166
|
-
- Archives milestone files
|
|
167
|
-
- Generates retrospective
|
|
168
|
-
- Extracts learnings
|
|
169
|
-
- Tags git version
|
|
170
|
-
- Prepares for next milestone
|
|
171
|
-
|
|
172
|
-
## Best Practices
|
|
173
|
-
|
|
174
|
-
### Good Milestone Scope
|
|
175
|
-
|
|
176
|
-
**Right size:**
|
|
177
|
-
- 3-8 related features
|
|
178
|
-
- 1-4 weeks of work
|
|
179
|
-
- Clear theme/objective
|
|
180
|
-
- Delivers user value
|
|
181
|
-
|
|
182
|
-
**Too small:**
|
|
183
|
-
- Single feature (use `/goop-plan`)
|
|
184
|
-
- < 1 week work
|
|
185
|
-
- No clear theme
|
|
186
|
-
|
|
187
|
-
**Too large:**
|
|
188
|
-
- > 10 features
|
|
189
|
-
- > 1 month work
|
|
190
|
-
- Multiple unrelated areas
|
|
191
|
-
- Split into multiple milestones
|
|
192
|
-
|
|
193
|
-
### Milestone Planning
|
|
194
|
-
|
|
195
|
-
1. **Start with objectives** - What value does this deliver?
|
|
196
|
-
2. **List features** - What's needed to achieve objectives?
|
|
197
|
-
3. **Map dependencies** - What order makes sense?
|
|
198
|
-
4. **Estimate effort** - How long will this take?
|
|
199
|
-
5. **Get confirmation** - Does user agree with scope?
|
|
200
|
-
|
|
201
|
-
## Next Steps
|
|
202
|
-
|
|
203
|
-
After milestone started:
|
|
204
|
-
- `/goop-plan [feature]` - Plan first feature
|
|
205
|
-
- `/goop-status` - Check milestone progress
|
|
206
|
-
|
|
207
|
-
After milestone complete:
|
|
208
|
-
- `/goop-milestone [next]` - Start next milestone
|
|
209
|
-
- Review RETROSPECTIVE.md for insights
|
|
210
|
-
|
|
211
|
-
---
|
|
212
|
-
|
|
213
|
-
**GoopSpec**: Think in milestones, deliver in features.
|
|
48
|
+
> **User:** `/goop-milestone start "User Dashboard"`
|
|
49
|
+
> **Agent:** "Milestone 'User Dashboard' started.
|
|
50
|
+
> Plan your first feature with `/goop-plan`."
|
package/commands/goop-pause.md
CHANGED
|
@@ -1,61 +1,52 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: goop-pause
|
|
3
|
-
description: Save a checkpoint
|
|
3
|
+
description: Save a checkpoint and pause work
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
#
|
|
6
|
+
# /goop-pause
|
|
7
7
|
|
|
8
|
-
|
|
8
|
+
**Pause work and save state.** Create a resumption checkpoint.
|
|
9
9
|
|
|
10
10
|
## Usage
|
|
11
11
|
|
|
12
|
+
```bash
|
|
13
|
+
/goop-pause [optional message]
|
|
12
14
|
```
|
|
13
|
-
/goop-pause [checkpoint-name]
|
|
14
|
-
```
|
|
15
|
-
|
|
16
|
-
## What Gets Saved
|
|
17
|
-
|
|
18
|
-
A checkpoint captures:
|
|
19
|
-
- Current session ID
|
|
20
|
-
- Current phase and spec
|
|
21
|
-
- Incomplete todos
|
|
22
|
-
- Modified files
|
|
23
|
-
- Git commit hash
|
|
24
|
-
- Timestamp
|
|
25
|
-
|
|
26
|
-
## Storage
|
|
27
15
|
|
|
28
|
-
|
|
29
|
-
`.goopspec/checkpoints/checkpoint-{id}.json`
|
|
16
|
+
## Tools Used
|
|
30
17
|
|
|
31
|
-
|
|
18
|
+
| Tool | Purpose in This Command |
|
|
19
|
+
|------|------------------------|
|
|
20
|
+
| `goop_checkpoint` | Save execution state for later resume |
|
|
21
|
+
| `goop_status` | Capture current phase and progress |
|
|
22
|
+
| `memory_save` | Persist session context |
|
|
32
23
|
|
|
33
|
-
|
|
24
|
+
**Hook Support:** `system.transform` includes checkpoint in future sessions.
|
|
34
25
|
|
|
35
|
-
|
|
26
|
+
---
|
|
36
27
|
|
|
37
|
-
|
|
38
|
-
/goop-pause "Before major refactor"
|
|
39
|
-
```
|
|
28
|
+
## How It Works
|
|
40
29
|
|
|
41
|
-
|
|
30
|
+
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."
|
|
42
31
|
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
32
|
+
### What is Saved?
|
|
33
|
+
- **Workflow State:** Phase, Wave, active Plan/Spec.
|
|
34
|
+
- **Task Context:** Which task was active.
|
|
35
|
+
- **Memory Buffer:** Short-term observations not yet persisted.
|
|
36
|
+
- **Git State:** Current branch and status.
|
|
47
37
|
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
38
|
+
### When to Use
|
|
39
|
+
- Ending a work session.
|
|
40
|
+
- Switching to a different urgent task.
|
|
41
|
+
- Before a risky manual experiment.
|
|
52
42
|
|
|
53
|
-
##
|
|
43
|
+
## Output
|
|
54
44
|
|
|
55
|
-
-
|
|
56
|
-
-
|
|
57
|
-
- Context switching - pause one task, work on another
|
|
45
|
+
- Saves a checkpoint file (JSON) in `.goopspec/checkpoints/`.
|
|
46
|
+
- Confirms the checkpoint ID for resumption.
|
|
58
47
|
|
|
59
|
-
|
|
48
|
+
## Example
|
|
60
49
|
|
|
61
|
-
**
|
|
50
|
+
> **User:** `/goop-pause Heading to lunch`
|
|
51
|
+
> **Agent:** "Checkpoint `cp-123` saved. 'Heading to lunch'.
|
|
52
|
+
> Run `/goop-resume` to pick up exactly here."
|