@hopla/claude-setup 1.2.1 → 1.2.3
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.
|
@@ -201,12 +201,20 @@ Do NOT show the full PRD in the chat. Instead:
|
|
|
201
201
|
1. Save the draft to `PRD.draft.md` at the project root
|
|
202
202
|
2. Save any on-demand context documents created in Step 3 (also with `.draft` suffix if new)
|
|
203
203
|
3. Tell the user:
|
|
204
|
-
> "Draft saved to `PRD.draft.md` — open it in your editor.
|
|
204
|
+
> "Draft saved to `PRD.draft.md` — open it in your editor. You can add `<!-- TODO: your note -->` comments anywhere in the file and tell me 'apply comments', request changes in chat, or say 'looks good' to finalize."
|
|
205
205
|
|
|
206
206
|
**Review loop:** Stay in this loop until the user finalizes:
|
|
207
|
-
|
|
207
|
+
|
|
208
|
+
- If the user says **"apply comments"** (or similar) → scan `PRD.draft.md` for `<!-- TODO: ... -->` comments, apply each one, remove the comment tags, update the file, then list what was changed: "Applied 3 changes: [list]. Anything else, or ready to finalize?"
|
|
209
|
+
- If the user requests changes in chat → apply them directly to `PRD.draft.md`, then say: "Updated — anything else, or ready to finalize?"
|
|
208
210
|
- If the user says the draft is ready (e.g. "looks good", "finalize", "listo") → proceed to Step 6
|
|
209
211
|
|
|
212
|
+
**Comment format the user can add directly in the draft:**
|
|
213
|
+
```
|
|
214
|
+
<!-- TODO: your instruction here -->
|
|
215
|
+
```
|
|
216
|
+
Comments can be placed anywhere in the file — inline after a line, or on their own line above a section. Process them in order from top to bottom.
|
|
217
|
+
|
|
210
218
|
Do not ask clarifying questions about changes — just apply them and confirm what was changed.
|
|
211
219
|
|
|
212
220
|
## Step 6: Finalize
|
|
@@ -59,7 +59,7 @@ Based on research, define:
|
|
|
59
59
|
|
|
60
60
|
## Phase 5: Generate the Plan
|
|
61
61
|
|
|
62
|
-
|
|
62
|
+
Write the full plan in memory using the structure below, then save it as a draft (do NOT output the plan content in the chat).
|
|
63
63
|
|
|
64
64
|
Use this structure:
|
|
65
65
|
|
|
@@ -122,7 +122,7 @@ Run in this order — do not proceed if a level fails:
|
|
|
122
122
|
|
|
123
123
|
## Phase 6: Verify the Plan
|
|
124
124
|
|
|
125
|
-
Before
|
|
125
|
+
Before saving the draft, review the plan against these criteria:
|
|
126
126
|
|
|
127
127
|
- [ ] Every task has a specific file path (no vague "update the component")
|
|
128
128
|
- [ ] Every task has: Action, File, Pattern, Details, Gotcha, Validate — no field left empty
|
|
@@ -130,10 +130,20 @@ Before finishing, review the plan against these criteria:
|
|
|
130
130
|
- [ ] The plan is complete enough that another agent can execute it without this conversation
|
|
131
131
|
- [ ] No ambiguous requirements left unresolved
|
|
132
132
|
|
|
133
|
-
##
|
|
133
|
+
## Phase 7: Save Draft and Enter Review Loop
|
|
134
134
|
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
-
|
|
138
|
-
|
|
139
|
-
-
|
|
135
|
+
1. Save the plan to `.agents/plans/[kebab-case-feature-name].draft.md`
|
|
136
|
+
2. Tell the user:
|
|
137
|
+
> "Plan draft saved to `.agents/plans/[feature-name].draft.md` — open it in your editor. You can add `<!-- TODO: your note -->` comments anywhere and tell me 'apply comments', request changes in chat, or say 'looks good' to finalize."
|
|
138
|
+
3. Also mention:
|
|
139
|
+
- How many tasks are in the plan
|
|
140
|
+
- Any open questions or decisions that require human input before execution
|
|
141
|
+
|
|
142
|
+
**Review loop:** Stay in this loop until the user finalizes:
|
|
143
|
+
- If the user says **"apply comments"** → scan the draft for `<!-- TODO: ... -->`, apply each one, remove the comment tags, update the file, report what changed
|
|
144
|
+
- If the user requests changes in chat → apply directly to the draft, confirm what changed
|
|
145
|
+
- If the user says the plan is ready → proceed to finalize
|
|
146
|
+
|
|
147
|
+
**Finalize:**
|
|
148
|
+
1. Rename `.agents/plans/[feature-name].draft.md` → `.agents/plans/[feature-name].md`
|
|
149
|
+
2. Confirm: "✅ Plan saved to `.agents/plans/[feature-name].md`. Run `/hopla-execute .agents/plans/[feature-name].md` to implement it, or `/hopla-commit` to save the plan first."
|