@hopla/claude-setup 1.1.8 → 1.2.0

package/files/commands/hopla-create-prd.md

@@ -1,8 +1,10 @@
 ---
-description: Create a Product Requirements Document (PRD) for a project through guided questions
+description: Create or update the PRD for this project through guided questions
 ---
 
-Create a PRD for this project following the Layer 1 Planning approach: an exploratory conversation that defines scope, reduces assumptions, and generates both a `PRD.md` and supporting on-demand context documents.
+Create or update a `PRD.md` for this project following the Layer 1 Planning approach: an exploratory conversation that defines scope, reduces assumptions, and generates both a `PRD.md` and supporting on-demand context documents.
+
+**If a `PRD.md` already exists**, this command will read it first and only ask about what's missing, outdated, or changing — it will not start from scratch.
 
 > Layer 1 Planning = Global Rules + On-Demand Context + PRD
 
@@ -11,7 +13,9 @@ Create a PRD for this project following the Layer 1 Planning approach: an explor
 Before asking anything, read what already exists:
 - `CLAUDE.md` or `AGENTS.md` — extract product name, tech stack, business context
 - `README.md` — extract any existing product description
-- Any existing `PRD.md` — understand what's already defined
+- Any existing `PRD.md` — understand what's already defined and what needs updating
+
+If a `PRD.md` exists, tell the user: "I found an existing PRD. I'll update it rather than start from scratch — only asking about what's missing or has changed."
 
 Use this to avoid asking questions that are already answered.
 
@@ -106,7 +110,7 @@ These become **on-demand context** referenced from the PRD and used in future pl
 
 ## Step 4: Generate the PRD
 
-Save to `PRD.md` at the project root. Use this structure:
+Write the full PRD content in memory using this structure (it will be saved as a draft in Step 5):
 
 ```markdown
 # PRD — [Product Name]
@@ -190,13 +194,21 @@ The MVP is working when:
 - [on-demand context doc] — [what it contains]
 ```
 
-## Step 5: Confirm and Save
+## Step 5: Save Draft and Wait for Approval
+
+Do NOT show the full PRD in the chat. Instead:
+
+1. Save the draft to `PRD.draft.md` at the project root
+2. Save any on-demand context documents created in Step 3 (also with `.draft` suffix if new)
+3. Tell the user:
+   > "Draft saved to `PRD.draft.md` — open it in your editor, make any changes you want, and let me know when it's ready to finalize."
+
+Wait for explicit approval before continuing.
 
-Show the draft PRD to the user and ask:
-> "Does this accurately reflect the product? Any corrections before I save it?"
+## Step 6: Finalize
 
-Once confirmed:
-1. Save `PRD.md` to the project root
-2. Save any on-demand context documents created in Step 3
-3. List all files created
-4. Suggest running `/hopla-commit` to save everything to the repository
+Once the user approves:
+1. Rename `PRD.draft.md` → `PRD.md` (overwrite if it existed)
+2. Rename any `.draft` context documents to their final names
+3. Delete the `.draft` files
+4. Confirm: "PRD.md saved. Run `/hopla-commit` to save it to the repository."

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hopla/claude-setup",
-  "version": "1.1.8",
+  "version": "1.2.0",
   "description": "Hopla team agentic coding system for Claude Code",
   "type": "module",
   "bin": {