@hopla/claude-setup 1.2.3 → 1.2.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.
@@ -201,17 +201,17 @@ 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. 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."
204
+ > "Draft saved to `PRD.draft.md` — open it in your editor. You can add `<? 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?"
208
+ - If the user says **"apply comments"** (or similar) → scan `PRD.draft.md` for `<? ... ?>` 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
209
  - If the user requests changes in chat → apply them directly to `PRD.draft.md`, then say: "Updated — anything else, or ready to finalize?"
210
210
  - If the user says the draft is ready (e.g. "looks good", "finalize", "listo") → proceed to Step 6
211
211
 
212
212
  **Comment format the user can add directly in the draft:**
213
213
  ```
214
- <!-- TODO: your instruction here -->
214
+ <? your instruction here ?>
215
215
  ```
216
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
217
 
@@ -134,13 +134,13 @@ Before saving the draft, review the plan against these criteria:
134
134
 
135
135
  1. Save the plan to `.agents/plans/[kebab-case-feature-name].draft.md`
136
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."
137
+ > "Plan draft saved to `.agents/plans/[feature-name].draft.md` — open it in your editor. You can add `<? your note ?>` comments anywhere and tell me 'apply comments', request changes in chat, or say 'looks good' to finalize."
138
138
  3. Also mention:
139
139
  - How many tasks are in the plan
140
140
  - Any open questions or decisions that require human input before execution
141
141
 
142
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
143
+ - If the user says **"apply comments"** → scan the draft for `<? ... ?>`, apply each one, remove the comment tags, update the file, report what changed
144
144
  - If the user requests changes in chat → apply directly to the draft, confirm what changed
145
145
  - If the user says the plan is ready → proceed to finalize
146
146
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hopla/claude-setup",
3
- "version": "1.2.3",
3
+ "version": "1.2.4",
4
4
  "description": "Hopla team agentic coding system for Claude Code",
5
5
  "type": "module",
6
6
  "bin": {