bmad-method 6.0.0-alpha.13 → 6.0.0-alpha.14

package/src/modules/bmb/docs/workflows/templates/step-1b-template.md

@@ -0,0 +1,223 @@
+# BMAD Workflow Step 1B Continuation Template
+
+This template provides the standard structure for workflow continuation steps. It handles resuming workflows that were started but not completed, ensuring seamless continuation across multiple sessions.
+
+Use this template alongside **step-01-init-continuable-template.md** to create workflows that can be paused and resumed. The init template handles the detection and routing logic, while this template handles the resumption logic.
+
+<!-- TEMPLATE START -->
+
+---
+
+name: 'step-01b-continue'
+description: 'Handle workflow continuation from previous session'
+
+<!-- Path Definitions -->
+
+workflow*path: '{project-root}/{\_bmad_folder*}/[module-path]/workflows/[workflow-name]'
+
+# File References (all use {variable} format in file)
+
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
+workflowFile: '{workflow_path}/workflow.md'
+
+# Template References (if needed for analysis)
+
+## analysisTemplate: '{workflow_path}/templates/[some-template].md'
+
+# Step 1B: Workflow Continuation
+
+## STEP GOAL:
+
+To resume the [workflow-type] workflow from where it was left off, ensuring smooth continuation without loss of context or progress.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a [specific role, e.g., "business analyst" or "technical architect"]
+- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring [your expertise], user brings [their expertise], and together we produce something better than we could on our own
+- ✅ Maintain collaborative [adjective] tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on analyzing and resuming workflow state
+- 🚫 FORBIDDEN to modify content completed in previous steps
+- 💬 Maintain continuity with previous sessions
+- 🚪 DETECT exact continuation point from frontmatter of incomplete file {outputFile}
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking action
+- 💾 Keep existing frontmatter `stepsCompleted` values intact
+- 📖 Review the template content already generated in {outputFile}
+- 🚫 FORBIDDEN to modify content that was completed in previous steps
+- 📝 Update frontmatter with continuation timestamp when resuming
+
+## CONTEXT BOUNDARIES:
+
+- Current [output-file-name] document is already loaded
+- Previous context = complete template + existing frontmatter
+- [Key data collected] already gathered in previous sessions
+- Last completed step = last value in `stepsCompleted` array from frontmatter
+
+## CONTINUATION SEQUENCE:
+
+### 1. Analyze Current State
+
+Review the frontmatter of {outputFile} to understand:
+
+- `stepsCompleted`: Which steps are already done (the rightmost value is the last step completed)
+- `lastStep`: Name/description of last completed step (if exists)
+- `date`: Original workflow start date
+- `inputDocuments`: Any documents loaded during initialization
+- [Other relevant frontmatter fields]
+
+Example: If `stepsCompleted: [1, 2, 3, 4]`, then step 4 was the last completed step.
+
+### 2. Read All Completed Step Files
+
+For each step number in `stepsCompleted` array (excluding step 1, which is init):
+
+1. **Construct step filename**: `step-[N]-[name].md`
+2. **Read the complete step file** to understand:
+   - What that step accomplished
+   - What the next step should be (from nextStep references)
+   - Any specific context or decisions made
+
+Example: If `stepsCompleted: [1, 2, 3]`:
+
+- Read `step-02-[name].md`
+- Read `step-03-[name].md`
+- The last file will tell you what step-04 should be
+
+### 3. Review Previous Output
+
+Read the complete {outputFile} to understand:
+
+- Content generated so far
+- Sections completed vs pending
+- User decisions and preferences
+- Current state of the deliverable
+
+### 4. Determine Next Step
+
+Based on the last completed step file:
+
+1. **Find the nextStep reference** in the last completed step file
+2. **Validate the file exists** at the referenced path
+3. **Confirm the workflow is incomplete** (not all steps finished)
+
+### 5. Welcome Back Dialog
+
+Present a warm, context-aware welcome:
+
+"Welcome back! I see we've completed [X] steps of your [workflow-type].
+
+We last worked on [brief description of last step].
+
+Based on our progress, we're ready to continue with [next step description].
+
+Are you ready to continue where we left off?"
+
+### 6. Validate Continuation Intent
+
+Ask confirmation questions if needed:
+
+"Has anything changed since our last session that might affect our approach?"
+"Are you still aligned with the goals and decisions we made earlier?"
+"Would you like to review what we've accomplished so far?"
+
+### 7. Present MENU OPTIONS
+
+Display: "**Resuming workflow - Select an Option:** [C] Continue to [Next Step Name]"
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Update frontmatter with continuation timestamp when 'C' is selected
+
+#### Menu Handling Logic:
+
+- IF C:
+  1. Update frontmatter: add `lastContinued: [current date]`
+  2. Load, read entire file, then execute the appropriate next step file (determined in section 4)
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and continuation analysis is complete, will you then:
+
+1. Update frontmatter in {outputFile} with continuation timestamp
+2. Load, read entire file, then execute the next step file determined from the analysis
+
+Do NOT modify any other content in the output document during this continuation step.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Correctly identified last completed step from `stepsCompleted` array
+- Read and understood all previous step contexts
+- User confirmed readiness to continue
+- Frontmatter updated with continuation timestamp
+- Workflow resumed at appropriate next step
+
+### ❌ SYSTEM FAILURE:
+
+- Skipping analysis of existing state
+- Modifying content from previous steps
+- Loading wrong next step file
+- Not updating frontmatter with continuation info
+- Proceeding without user confirmation
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+<!-- TEMPLATE END -->
+
+## Customization Guidelines
+
+When adapting this template for your specific workflow:
+
+### 1. Update Placeholders
+
+Replace bracketed placeholders with your specific values:
+
+- `[module-path]` - e.g., "bmb/reference" or "custom"
+- `[workflow-name]` - your workflow directory name
+- `[workflow-type]` - e.g., "nutrition planning", "project requirements"
+- `[output-file-name]` - base name for output document
+- `[specific role]` - the role this workflow plays
+- `[your expertise]` - what expertise you bring
+- `[their expertise]` - what expertise user brings
+
+### 2. Add Workflow-Specific Context
+
+Add any workflow-specific fields to section 1 (Analyze Current State) if your workflow uses additional frontmatter fields for tracking.
+
+### 3. Customize Welcome Message
+
+Adapt the welcome dialog in section 5 to match your workflow's tone and context.
+
+### 4. Add Continuation-Specific Validations
+
+If your workflow has specific checkpoints or validation requirements, add them to section 6.
+
+## Implementation Notes
+
+1. **This step should NEVER modify the output content** - only analyze and prepare for continuation
+2. **Always preserve the `stepsCompleted` array** - don't modify it in this step
+3. **Timestamp tracking** - helps users understand when workflows were resumed
+4. **Context preservation** - the key is maintaining all previous work and decisions
+5. **Seamless experience** - user should feel like they never left the workflow

package/src/modules/bmb/{workflows/create-workflow → docs/workflows}/templates/step-file.md

@@ -3,7 +3,7 @@ name: "step-{{stepNumber}}-{{stepName}}"
 description: "{{stepDescription}}"
 
 # Path Definitions
-workflow_path: "{project-root}/{bmad_folder}/{{targetModule}}/workflows/{{workflowName}}"
+workflow_path: "{project-root}/{*bmad_folder*}/{{targetModule}}/workflows/{{workflowName}}"
 
 # File References
 thisStepFile: "{workflow_path}/steps/step-{{stepNumber}}-{{stepName}}.md"
@@ -15,9 +15,9 @@ workflowFile: "{workflow_path}/workflow.md"
 outputFile: "{output_folder}/{{outputFileName}}-{project_name}.md"
 {{/hasOutput}}
 
-# Task References
-advancedElicitationTask: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
-partyModeWorkflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+# Task References (list only if used in THIS step file instance and only the ones used, there might be others)
+advancedElicitationTask: "{project-root}/{*bmad_folder*}/core/tasks/advanced-elicitation.xml"
+partyModeWorkflow: "{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md"
 
 {{#hasTemplates}}
 # Template References

package/src/modules/bmb/docs/workflows/{step-template.md → templates/step-template.md}

@@ -2,33 +2,43 @@
 
 This template provides the standard structure for all BMAD workflow step files. Copy and modify this template for each new step you create.
 
----
+<!-- TEMPLATE START -->
 
-```yaml
 ---
+
 name: 'step-[N]-[short-name]'
 description: '[Brief description of what this step accomplishes]'
 
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/[workflow-name]'
+<!-- Path Definitions -->
+
+workflow*path: '{project-root}/{\_bmad_folder*}/bmb/reference/workflows/[workflow-name]' # the folder the workflow.md file is in
 
 # File References (all use {variable} format in file)
+
 thisStepFile: '{workflow_path}/steps/step-[N]-[short-name].md'
-nextStepFile: '{workflow_path}/steps/step-[N+1]-[next-short-name].md' # Remove for final step
+nextStep{N+1}: '{workflow_path}/steps/step-[N+1]-[next-short-name].md' # Remove for final step or no next step
+altStep{Y}: '{workflow_path}/steps/step-[Y]-[some-other-step].md' # if there is an alternate next story depending on logic
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
 
-# Task References
-advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
+# Task References (IF THE workflow uses and it makes sense in this step to have these )
+
+advancedElicitationTask: '{project-root}/{_bmad_folder_}/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/{_bmad_folder_}/core/workflows/party-mode/workflow.md'
+
+# Template References (if this step uses a specific templates)
 
-# Template References (if this step uses templates)
 profileTemplate: '{workflow_path}/templates/profile-section.md'
 assessmentTemplate: '{workflow_path}/templates/assessment-section.md'
 strategyTemplate: '{workflow_path}/templates/strategy-section.md'
-# Add more as needed
+
+# Data (CSV for example) References (if used in this step)
+
+someData: '{workflow_path}/data/foo.csv'
+
+# Add more as needed - but ONLY what is used in this specific step file!
+
 ---
-```
 
 # Step [N]: [Step Name]
 
@@ -52,7 +62,7 @@ Example: "To analyze user requirements and document functional specifications th
 - ✅ You are a [specific role, e.g., "business analyst" or "technical architect"]
 - ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring [your expertise], user brings [their expertise], and together we produce something better than the sum of our own parts
+- ✅ You bring [your expertise], user brings [their expertise], and together we produce something better than we could on our own
 - ✅ Maintain collaborative [adjective] tone throughout
 
 ### Step-Specific Rules:
@@ -88,15 +98,10 @@ Example: "To analyze user requirements and document functional specifications th
 
 [Specific instructions for second part of the work]
 
-#### Content to Append (if applicable):
+### N. Title (as many as needed)
 
-```markdown
-## [Section Title]
-
-[Content template or instructions for what to append]
-```
-
-### N. (Continue as needed)
+<!-- not ever step will include advanced elicitation or party mode, in which case generally will just have the C option -->
+<!-- for example an init step 1 that loads data, or step 1b continues a workflow would not need advanced elicitation or party mode - but any step where the user and the llm work together on content, thats where it makes sense to include them -->
 
 ### N. Present MENU OPTIONS
 
@@ -105,7 +110,7 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
 #### Menu Handling Logic:
 
 - IF A: Execute {advancedElicitationTask} # Or custom action
-- IF P: Execute {partyModeWorkflow}
+- IF P: Execute {partyModeWorkflow} # Or custom action
 - IF C: Save content to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#n-present-menu-options)
 
@@ -113,8 +118,8 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
 
 - ALWAYS halt and wait for user input after presenting menu
 - ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu
-- User can chat or ask questions - always respond and then end with display again of the menu options
+- After other menu items execution completes, redisplay the menu
+- User can chat or ask questions - always respond when conversation ends, redisplay the menu
 
 ## CRITICAL STEP COMPLETION NOTE
 
@@ -122,8 +127,6 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
 
 ONLY WHEN [C continue option] is selected and [completion requirements], will you then load and read fully `[installed_path]/step-[next-number]-[name].md` to execute and begin [next step description].
 
----
-
 ## 🚨 SYSTEM SUCCESS/FAILURE METRICS
 
 ### ✅ SUCCESS:
@@ -140,15 +143,19 @@ ONLY WHEN [C continue option] is selected and [completion requirements], will yo
 - [Step-specific failure mode 2]
 - Proceeding without user input/selection
 - Not updating required documents/frontmatter
-- [General failure modes]
+- [Step-specific failure mode N]
 
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
 
----
+<!-- TEMPLATE END-->
+
+## Common Menu Patterns to use in the final sequence item in a step file
+
+FYI Again - party mode is useful for the user to reach out and get opinions from other agents.
 
-## Common Menu Patterns
+Advanced elicitation is use to direct you to think of alternative outputs of a sequence you just performed.
 
-### Standard Menu (A/P/C)
+### Standard Menu - when a sequence in a step results in content produced by the agent or human that could be improved before proceeding
 
 ```markdown
 ### N. Present MENU OPTIONS
@@ -170,7 +177,7 @@ Display: "**Select an Option:** [A] [Advanced Elicitation] [P] Party Mode [C] Co
 - User can chat or ask questions - always respond and then end with display again of the menu options
 ```
 
-### Auto-Proceed Menu (No User Choice)
+### Optional Menu - Auto-Proceed Menu (No User Choice or confirm, just flow right to the next step once completed)
 
 ```markdown
 ### N. Present MENU OPTIONS
@@ -196,8 +203,8 @@ Display: "**Select an Option:** [A] [Custom Action 1] [B] [Custom Action 2] [C]
 
 #### Menu Handling Logic:
 
-- IF A: [Custom handler for option A]
-- IF B: [Custom handler for option B]
+- IF A: [Custom handler route for option A]
+- IF B: [Custom handler route for option B]
 - IF C: Save content to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#n-present-menu-options)
 
@@ -214,7 +221,7 @@ Display: "**Select an Option:** [A] [Custom Action 1] [B] [Custom Action 2] [C]
 ```markdown
 ### N. Present MENU OPTIONS
 
-Display: "**Select an Option:** [A] [Custom Label] [C] Continue"
+Display: "**Select an Option:** [A] [Continue to Step Foo] [A] [Continue to Step Bar]"
 
 #### Menu Handling Logic:
 

package/src/modules/bmb/docs/workflows/templates/workflow-template.md

@@ -0,0 +1,104 @@
+# BMAD Workflow Template
+
+This template provides the standard structure for all BMAD workflow files. Copy and modify this template for each new workflow you create.
+
+<!-- TEMPLATE START -->
+
+---
+
+name: [WORKFLOW_DISPLAY_NAME]
+description: [Brief description of what this workflow accomplishes]
+web_bundle: [true/false] # Set to true for inclusion in web bundle builds
+
+---
+
+# [WORKFLOW_DISPLAY_NAME]
+
+**Goal:** [State the primary goal of this workflow in one clear sentence]
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a [role] collaborating with [user type]. This is a partnership, not a client-vendor relationship. You bring [your expertise], while the user brings [their expertise]. Work together as equals.
+
+## WORKFLOW ARCHITECTURE
+
+### Core Principles
+
+- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
+- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Module Configuration Loading
+
+Load and read full config from {project-root}/{_bmad_folder_}/[MODULE FOLDER]/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, [MODULE VARS]
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute [FIRST STEP FILE PATH] to begin the workflow.
+
+<!-- TEMPLATE END -->
+
+## How to Use This Template
+
+### Step 1: Copy and Replace Placeholders
+
+Copy the template above and replace:
+
+- `[WORKFLOW_DISPLAY_NAME]` → Your workflow's display name
+- `[MODULE FOLDER]` → Default is `core` unless this is for another module (such as bmm, cis, or another as directed by user)
+- `[Brief description]` → One-sentence description
+- `[true/false]` → Whether to include in web bundle
+- `[role]` → AI's role in this workflow
+- `[user type]` → Who the user is
+- `[CONFIG_PATH]` → Path to config file (usually `bmm/config.yaml` or `bmb/config.yaml`)
+- `[WORKFLOW_PATH]` → Path to your workflow folder
+- `[MODULE VARS]` → Extra config variables available in a module configuration that the workflow would need to use
+
+### Step 2: Create the Folder Structure
+
+```
+[workflow-folder]/
+├── workflow.md          # This file
+├── data/                # (Optional csv or other data files)
+├── templates/           # template files for output
+└── steps/
+    ├── step-01-init.md
+    ├── step-02-[name].md
+    └── ...
+
+```
+
+### Step 3: Configure the Initialization Path
+
+Update the last line of the workflow.md being created to replace [FIRST STEP FILE PATH] with the path to the actual first step file.
+
+Example: Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.
+
+### NOTE: You can View a real example of a perfect workflow.md file that was created from this template
+
+`{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/workflow.md`

package/src/modules/bmb/{workflows/create-workflow → docs/workflows}/templates/workflow.md

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/{bmad_folder}/{{targetModule}}/config.yaml and resolve:
+Load and read full config from {project-root}/{_bmad_folder_}/{{targetModule}}/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 

package/src/modules/bmb/reference/agents/expert-examples/journal-keeper/README.md

@@ -51,7 +51,7 @@ menu:
 
   # Direct sidecar file action
   - trigger: 'insight'
-    action: 'Document this breakthrough in {agent-folder}/journal-keeper-sidecar/breakthroughs.md'
+    action: 'Document this breakthrough in ./journal-keeper-sidecar/breakthroughs.md'
     description: 'Record a meaningful insight'
 ```
 
@@ -63,9 +63,9 @@ Expert Agents MUST load sidecar files explicitly:
 
 ```yaml
 critical_actions:
-  - 'Load COMPLETE file {agent-folder}/journal-keeper-sidecar/memories.md'
-  - 'Load COMPLETE file {agent-folder}/journal-keeper-sidecar/instructions.md'
-  - 'ONLY read/write files in {agent-folder}/journal-keeper-sidecar/'
+  - 'Load COMPLETE file ./journal-keeper-sidecar/memories.md'
+  - 'Load COMPLETE file ./journal-keeper-sidecar/instructions.md'
+  - 'ONLY read/write files in ./journal-keeper-sidecar/'
 ```
 
 **Key points:**

package/src/modules/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml

@@ -20,9 +20,9 @@ agent:
       - Reflection transforms experience into wisdom
 
   critical_actions:
-    - "Load COMPLETE file {agent-folder}/journal-keeper-sidecar/memories.md and remember all past insights"
-    - "Load COMPLETE file {agent-folder}/journal-keeper-sidecar/instructions.md and follow ALL journaling protocols"
-    - "ONLY read/write files in {agent-folder}/journal-keeper-sidecar/ - this is our private space"
+    - "Load COMPLETE file {agent_sidecar_folder}/journal-keeper-sidecar/memories.md and remember all past insights"
+    - "Load COMPLETE file {agent_sidecar_folder}/journal-keeper-sidecar/instructions.md and follow ALL journaling protocols"
+    - "ONLY read/write files in {agent_sidecar_folder}/journal-keeper-sidecar/ - this is our private space"
     - "Track mood patterns, recurring themes, and breakthrough moments"
     - "Reference past entries naturally to show continuity"
 
@@ -120,7 +120,7 @@ agent:
       description: "Write today's journal entry"
 
     - trigger: quick
-      action: "Save a quick, unstructured entry to {agent-folder}/journal-keeper-sidecar/entries/entry-{date}.md with timestamp and any patterns noticed"
+      action: "Save a quick, unstructured entry to {agent_sidecar_folder}/journal-keeper-sidecar/entries/entry-{date}.md with timestamp and any patterns noticed"
       description: "Quick capture without prompts"
 
     - trigger: mood
@@ -133,20 +133,20 @@ agent:
 
     - trigger: gratitude
       action: "#gratitude-moment"
-      description: "Capture today's gratitudes"
+      description: "Capture today's gratitude"
 
     - trigger: weekly
       action: "#weekly-reflection"
       description: "Reflect on the past week"
 
     - trigger: insight
-      action: "Document this breakthrough in {agent-folder}/journal-keeper-sidecar/breakthroughs.md with date and significance"
+      action: "Document this breakthrough in {agent_sidecar_folder}/journal-keeper-sidecar/breakthroughs.md with date and significance"
       description: "Record a meaningful insight"
 
     - trigger: read-back
-      action: "Load and share entries from {agent-folder}/journal-keeper-sidecar/entries/ for requested timeframe, highlighting themes and growth"
+      action: "Load and share entries from {agent_sidecar_folder}/journal-keeper-sidecar/entries/ for requested timeframe, highlighting themes and growth"
       description: "Review past entries"
 
     - trigger: save
-      action: "Update {agent-folder}/journal-keeper-sidecar/memories.md with today's session insights and emotional markers"
+      action: "Update {agent_sidecar_folder}/journal-keeper-sidecar/memories.md with today's session insights and emotional markers"
       description: "Save what we discussed today"

package/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml

@@ -10,7 +10,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/security-engineer.md"
+    id: "{*bmad_folder*}/bmm/agents/security-engineer.md"
     name: "Sam"
     title: "Security Engineer"
     icon: "🔐"
@@ -32,22 +32,22 @@ agent:
   menu:
     # NOTE: These workflows are hypothetical examples assuming add to a module called bmm - not implemented
     - trigger: threat-model
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/threat-model/workflow.yaml"
+      exec: "{project-root}/{*bmad_folder*}/bmm/workflows/threat-model/workflow.md"
       description: "Create STRIDE threat model for architecture"
 
     - trigger: security-review
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/security-review/workflow.yaml"
+      exec: "{project-root}/{*bmad_folder*}/bmm/workflows/security-review/workflow.md"
       description: "Review code/design for security issues"
 
     - trigger: owasp-check
-      exec: "{project-root}/{bmad_folder}/bmm/tasks/owasp-top-10.xml"
+      TODO: true
       description: "Check against OWASP Top 10"
 
     - trigger: compliance
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/compliance-check/workflow.yaml"
+      exec: "{project-root}/{*bmad_folder*}/bmm/workflows/compliance-check/workflow.md"
       description: "Verify compliance requirements (SOC2, GDPR, etc.)"
 
     # Core workflow that exists
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md"
       description: "Multi-agent security discussion"