feat(BMAD): add shared step completion template and integrate into workflows

- Create new step-completion.md template for consistent step completion behavior
- Add template path to placeholders.js configuration
- Replace individual step completion sections with template reference in all workflow files
- Add content saving step at start of completion sequences

Author: moazbuilds

config/placeholders.js

@@ -42,5 +42,8 @@ module.exports = {
     // BMAD SM workflow shared files
     sprint_status_template: path.join('prompts', 'templates', 'bmad', '06-sm', '01-sprint-planning', 'sprint-status-template.yaml'),
     story_template: path.join('prompts', 'templates', 'bmad', '06-sm', '02-create-story', 'template.md'),
+
+    // BMAD shared step rules
+    step_completion: path.join('prompts', 'templates', 'bmad', 'shared', 'step-completion.md'),
   }
 };

prompts/templates/bmad/01-analyst/chained/step-01-vision.md

@@ -121,18 +121,7 @@ status: 'draft'
 [Key differentiators based on conversation]
 ```
 
-### 7. Step Completion
-
-**Save Content:**
-Create the document and write the generated content to `.codemachine/artifacts/product-brief-{date}.md` now.
-
-**Confirmation:**
-"Content saved to document.
-
-I've drafted the executive summary and core vision based on our conversation. This captures the essence of the project and what makes it special.
-
-- If you want to **modify or add details**, just tell me what you'd like to change
-- If you're satisfied, **press Enter in the promptbox to go to the next step**"
+{step_completion}
 
 
 ## 🚨 SYSTEM SUCCESS/FAILURE METRICS

prompts/templates/bmad/01-analyst/chained/step-02-users.md

@@ -34,6 +34,10 @@ Define target users with rich personas and map their key interactions with the p
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Save Previous Step Content
+
+**First Action:** Create the product brief document at `.codemachine/artifacts/product-brief-{date}.md` using the content confirmed in Step 1.
+
 ### 1. Begin User Discovery
 
 **Opening Exploration:**
@@ -123,18 +127,7 @@ Prepare the following structure for document append:
 [User journey content based on conversation, or N/A if not discussed]
 ```
 
-### 6. Step Completion
-
-**Save Content:**
-Append the generated content to the document now.
-
-**Confirmation:**
-"Content saved to document.
-
-I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
-
-- If you want to **modify or add details**, just tell me what you'd like to change
-- If you're satisfied, **press Enter in the promptbox to go to the next step**"
+{step_completion}
 
 ---
 

prompts/templates/bmad/01-analyst/chained/step-03-metrics.md

@@ -34,6 +34,10 @@ Define comprehensive success metrics that include user success, business objecti
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Save Previous Step Content
+
+**First Action:** Append the confirmed content from Step 2 to the product brief document.
+
 ### 1. Begin Success Metrics Discovery
 
 **Opening Exploration:**
@@ -126,18 +130,7 @@ Prepare the following structure for document append:
 [Key performance indicators content based on conversation, or N/A if not discussed]
 ```
 
-### 7. Step Completion
-
-**Save Content:**
-Append the generated content to the document now.
-
-**Confirmation:**
-"Content saved to document.
-
-I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
-
-- If you want to **modify or add details**, just tell me what you'd like to change
-- If you're satisfied, **press Enter in the promptbox to go to the next step**"
+{step_completion}
 
 ---
 

prompts/templates/bmad/01-analyst/chained/step-04-scope.md

@@ -34,6 +34,10 @@ Define MVP scope with clear boundaries and outline future vision through collabo
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Save Previous Step Content
+
+**First Action:** Append the confirmed content from Step 3 to the product brief document.
+
 ### 1. Begin Scope Definition
 
 **Opening Exploration:**
@@ -140,18 +144,7 @@ Prepare the following structure for document append:
 [Future vision content based on conversation, or N/A if not discussed]
 ```
 
-### 7. Step Completion
-
-**Save Content:**
-Append the generated content to the document now.
-
-**Confirmation:**
-"Content saved to document.
-
-I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
-
-- If you want to **modify or add details**, just tell me what you'd like to change
-- If you're satisfied, **press Enter in the promptbox to go to the next step**"
+{step_completion}
 
 ---
 

prompts/templates/bmad/01-analyst/chained/step-05-complete.md

@@ -36,6 +36,10 @@ Complete the product brief workflow, update status files, and provide guidance o
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Save Previous Step Content
+
+**First Action:** Append the confirmed content from Step 4 to the product brief document.
+
 ### 1. Announce Workflow Completion
 
 **Completion Announcement:**

prompts/templates/bmad/02-pm/01-prd/chained/step-01-discovery.md

@@ -172,18 +172,7 @@ status: 'draft'
 {project_classification_content}
 ```
 
-### 6. Step Completion
-
-**Save Content:**
-Create the PRD document at `.codemachine/artifacts/prd-{date}.md` using the structure from step 5 now.
-
-**Confirmation:**
-"Document created and saved.
-
-I've drafted the Executive Summary based on our conversation. This will be the first section of your PRD and captures the project classification and vision.
-
-- If you want to **modify or add details**, just tell me what you'd like to change
-- If you're satisfied, **press Enter in the promptbox to go to the next step**"
+{step_completion}
 
 ## SUCCESS METRICS:
 

prompts/templates/bmad/02-pm/01-prd/chained/step-02-success.md

@@ -33,6 +33,10 @@ Define comprehensive success criteria that cover user success, business success,
 
 ## SUCCESS DISCOVERY SEQUENCE:
 
+### 0. Save Previous Step Content
+
+**First Action:** Create the PRD document at `.codemachine/artifacts/prd-{date}.md` using the content confirmed in Step 1.
+
 ### 1. Begin Success Definition Conversation
 
 **Check Product Brief for Success Indicators:**
@@ -168,18 +172,7 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Content about future vision based on conversation]
 ```
 
-### 8. Step Completion
-
-**Save Content:**
-Append the content to the document using the structure from step 7 now.
-
-**Confirmation:**
-"Content saved to document.
-
-I've drafted the Success Criteria and Scope based on our conversation. This captures what success looks like for users, business, and technical implementation.
-
-- If you want to **modify or add details**, just tell me what you'd like to change
-- If you're satisfied, **press Enter in the promptbox to go to the next step**"
+{step_completion}
 
 ## SUCCESS METRICS:
 

prompts/templates/bmad/02-pm/01-prd/chained/step-03-journeys.md

@@ -33,6 +33,10 @@ Create compelling narrative user journeys that leverage existing personas from p
 
 ## JOURNEY MAPPING SEQUENCE:
 
+### 0. Save Previous Step Content
+
+**First Action:** Append the confirmed content from Step 2 to the PRD document.
+
 ### 1. Leverage Existing Users & Identify Additional Types
 
 **Check Product Brief for Existing Personas:**
@@ -170,18 +174,7 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Summary of capabilities revealed by journeys based on conversation]
 ```
 
-### 7. Step Completion
-
-**Save Content:**
-Append the content to the document using the structure from step 6 now.
-
-**Confirmation:**
-"Content saved to document.
-
-I've mapped out the user journeys based on our conversation. Each journey reveals different capabilities needed for {{project_name}}.
-
-- If you want to **modify or add journeys**, just tell me what you'd like to change
-- If you're satisfied, **press Enter in the promptbox to go to the next step**"
+{step_completion}
 
 ## SUCCESS METRICS:
 

prompts/templates/bmad/02-pm/01-prd/chained/step-04-domain.md

@@ -42,6 +42,10 @@ Explore domain-specific requirements for complex domains that need specialized c
 
 ## DOMAIN EXPLORATION SEQUENCE:
 
+### 0. Save Previous Step Content
+
+**First Action:** Append the confirmed content from Step 3 to the PRD document.
+
 ### 1. Use Domain Configuration Data
 
 Use domain-specific configuration from workflow context:
@@ -151,18 +155,7 @@ Parse `special_sections` list from the matched CSV row. For each section name, g
 - "safety_measures" → Specify safety protocols and monitoring
 - "compliance_matrix" → Create compliance tracking matrix
 
-### 7. Step Completion
-
-**Save Content:**
-Append the content to the document using the structure from step 5 now.
-
-**Confirmation:**
-"Content saved to document.
-
-I've documented the {domain}-specific requirements that will shape {{project_name}}. These constraints are critical for success in this complex domain.
-
-- If you want to **modify or add details**, just tell me what you'd like to change
-- If you're satisfied, **press Enter in the promptbox to go to the next step**"
+{step_completion}
 
 ## SUCCESS METRICS: