critical file issues in prd refactor resolved.

2026-01-30 04:32:02 +00:00 · 2026-01-08 15:27:13 +08:00
parent 8e165b9b57
commit fac1308e97
120 changed files with 1885 additions and 1385 deletions
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-01-init.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-01-init.md
@@ -6,8 +6,8 @@ description: 'Initialize quiz game with mode selection and category choice'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-q1.md'
+thisStepFile: './step-01-init.md'
+nextStepFile: './step-02-q1.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 csvTemplate: '{workflow_path}/templates/csv-headers.template'
@@ -146,7 +146,7 @@ Display: **Starting your quiz adventure...**

 ## CRITICAL STEP COMPLETION NOTE

-ONLY WHEN setup is complete (mode selected, category chosen, CSV initialized) will you then load, read fully, and execute `{workflow_path}/steps/step-02-q1.md` to begin the first question.
+ONLY WHEN setup is complete (mode selected, category chosen, CSV initialized) will you then load, read fully, and execute `./step-02-q1.md` to begin the first question.

 ## 🚨 SYSTEM SUCCESS/FAILURE METRICS

--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-02-q1.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-02-q1.md
@@ -6,9 +6,9 @@ description: 'Question 1 - Level 1 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-02-q1.md'
-nextStepFile: '{workflow_path}/steps/step-03-q2.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-02-q1.md'
+nextStepFile: './step-03-q2.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 # Task References
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-03-q2.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-03-q2.md
@@ -6,9 +6,9 @@ description: 'Question 2 - Level 2 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-03-q2.md'
-nextStepFile: '{workflow_path}/steps/step-04-q3.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-03-q2.md'
+nextStepFile: './step-04-q3.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 ---
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-04-q3.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-04-q3.md
@@ -6,9 +6,9 @@ description: 'Question 3 - Level 3 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-04-q3.md'
-nextStepFile: '{workflow_path}/steps/step-04-q3.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-04-q3.md'
+nextStepFile: './step-04-q3.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 ---
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-05-q4.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-05-q4.md
@@ -6,9 +6,9 @@ description: 'Question 4 - Level 4 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-05-q4.md'
-nextStepFile: '{workflow_path}/steps/step-05-q4.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-05-q4.md'
+nextStepFile: './step-05-q4.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 ---
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-06-q5.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-06-q5.md
@@ -6,9 +6,9 @@ description: 'Question 5 - Level 5 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-06-q5.md'
-nextStepFile: '{workflow_path}/steps/step-06-q5.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-06-q5.md'
+nextStepFile: './step-06-q5.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 ---
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-07-q6.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-07-q6.md
@@ -6,9 +6,9 @@ description: 'Question 6 - Level 6 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-07-q6.md'
-nextStepFile: '{workflow_path}/steps/step-07-q6.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-07-q6.md'
+nextStepFile: './step-07-q6.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 ---
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-08-q7.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-08-q7.md
@@ -6,9 +6,9 @@ description: 'Question 7 - Level 7 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-08-q7.md'
-nextStepFile: '{workflow_path}/steps/step-08-q7.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-08-q7.md'
+nextStepFile: './step-08-q7.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 ---
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-09-q8.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-09-q8.md
@@ -6,9 +6,9 @@ description: 'Question 8 - Level 8 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-09-q8.md'
-nextStepFile: '{workflow_path}/steps/step-09-q8.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-09-q8.md'
+nextStepFile: './step-09-q8.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 ---
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-10-q9.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-10-q9.md
@@ -6,9 +6,9 @@ description: 'Question 9 - Level 9 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-10-q9.md'
-nextStepFile: '{workflow_path}/steps/step-10-q9.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-10-q9.md'
+nextStepFile: './step-10-q9.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 ---
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-11-q10.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-11-q10.md
@@ -6,9 +6,9 @@ description: 'Question 10 - Level 10 difficulty'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-11-q10.md'
-nextStepFile: '{workflow_path}/steps/results.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
+thisStepFile: './step-11-q10.md'
+nextStepFile: './results.md'
+resultsStepFile: './step-12-results.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 ---
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-12-results.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-12-results.md
@@ -6,8 +6,8 @@ description: 'Final results and celebration'
 workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'

 # File References
-thisStepFile: '{workflow_path}/steps/step-12-results.md'
-initStepFile: '{workflow_path}/steps/step-01-init.md'
+thisStepFile: './step-12-results.md'
+initStepFile: './step-01-init.md'
 workflowFile: '{workflow_path}/workflow.md'
 csvFile: '{project-root}/BMad-quiz-results.csv'
 # Task References
--- a/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/workflow.md
+++ b/samples/sample-custom-modules/sample-unitary-module/workflows/quiz-master/workflow.md
@@ -51,4 +51,4 @@ Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:

 ### 2. First Step EXECUTION

-Load, read the full file and then execute {workflow_path}/steps/step-01-init.md to begin the workflow.
+Load, read the full file and then execute ./step-01-init.md to begin the workflow.
--- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md
+++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md
@@ -6,12 +6,12 @@ description: 'Initialize the nutrition plan workflow by detecting continuation s
 workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-profile.md'
+thisStepFile: './step-01-init.md'
+nextStepFile: './step-02-profile.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
 templateFile: '{workflow_path}/templates/nutrition-plan.md'
-continueFile: '{workflow_path}/steps/step-01b-continue.md'
+continueFile: './step-01b-continue.md'
 # Template References
 # This step doesn't use content templates, only the main template
 ---
--- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md
+++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md
@@ -6,7 +6,7 @@ description: 'Handle workflow continuation from previous session'
 workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
 ---

--- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md
+++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md
@@ -6,8 +6,8 @@ description: 'Gather comprehensive user profile information through collaborativ
 workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'

 # File References (all use {variable} format in file)
-thisStepFile: '{workflow_path}/steps/step-02-profile.md'
-nextStepFile: '{workflow_path}/steps/step-03-assessment.md'
+thisStepFile: './step-02-profile.md'
+nextStepFile: './step-03-assessment.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.md'

--- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md
+++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md
@@ -6,8 +6,8 @@ description: 'Analyze nutritional requirements, identify restrictions, and calcu
 workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'

 # File References
-thisStepFile: '{workflow_path}/steps/step-03-assessment.md'
-nextStepFile: '{workflow_path}/steps/step-04-strategy.md'
+thisStepFile: './step-03-assessment.md'
+nextStepFile: './step-04-strategy.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.md'

--- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md
+++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md
@@ -6,9 +6,9 @@ description: 'Design a personalized meal strategy that meets nutritional needs a
 workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'

 # File References
-thisStepFile: '{workflow_path}/steps/step-04-strategy.md'
-nextStepFile: '{workflow_path}/steps/step-05-shopping.md'
-alternateNextStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
+thisStepFile: './step-04-strategy.md'
+nextStepFile: './step-05-shopping.md'
+alternateNextStepFile: './step-06-prep-schedule.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.md'

--- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md
+++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md
@@ -6,8 +6,8 @@ description: 'Create a comprehensive shopping list that supports the meal strate
 workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'

 # File References
-thisStepFile: '{workflow_path}/steps/step-05-shopping.md'
-nextStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
+thisStepFile: './step-05-shopping.md'
+nextStepFile: './step-06-prep-schedule.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.md'

--- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md
+++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md
@@ -6,7 +6,7 @@ description: "Create a realistic meal prep schedule that fits the user's lifesty
 workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'

 # File References
-thisStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
+thisStepFile: './step-06-prep-schedule.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.md'

--- a/src/modules/bmb/workflows/workflow/data/architecture.md
+++ b/src/modules/bmb/workflows/workflow/data/architecture.md
@@ -91,8 +91,8 @@ workflow.md → step-01-init.md (detects existing) → step-01b-continue.md →
 ### Standard (All Workflows)
 ```yaml
 workflow_path: '{project-root}/_bmad/[module]/workflows/[name]'
-thisStepFile: '{workflow_path}/steps/step-[N]-[name].md'
-nextStepFile: '{workflow_path}/steps/step-[N+1]-[name].md'
+thisStepFile: './step-[N]-[name].md'
+nextStepFile: './step-[N+1]-[name].md'
 outputFile: '{output_folder}/[output].md'
 ```

--- a/src/modules/bmb/workflows/workflow/data/frontmatter-standards.md
+++ b/src/modules/bmb/workflows/workflow/data/frontmatter-standards.md
@@ -14,14 +14,14 @@

 ## Standard Variables (Always Available)

-| Variable          | Example Value                          |
-| ----------------- | -------------------------------------- |
-| `{project-root}`  | `/Users/user/dev/BMAD-METHOD`          |
-| `{project_name}`  | `my-project`                            |
-| `{output_folder}` | `/Users/user/dev/BMAD-METHOD/output`    |
-| `{user_name}`     | `Brian`                                 |
-| `{communication_language}` | `english`                       |
-| `{document_output_language}` | `english`                   |
+| Variable                     | Example Value                        |
+| ---------------------------- | ------------------------------------ |
+| `{project-root}`             | `/Users/user/dev/BMAD-METHOD`        |
+| `{project_name}`             | `my-project`                         |
+| `{output_folder}`            | `/Users/user/dev/BMAD-METHOD/output` |
+| `{user_name}`                | `Brian`                              |
+| `{communication_language}`   | `english`                            |
+| `{document_output_language}` | `english`                            |

 ---

@@ -101,7 +101,7 @@ nextStepFile: './step-02-foo.md'
 ### 1. Step to Step (SAME folder) = ./filename.md
 ```yaml
 # ❌ WRONG
-nextStepFile: '{workflow_path}/steps/step-02.md'
+nextStepFile: './step-02.md'
 nextStepFile: '{project-root}/_bmad/bmm/workflows/foo/steps/step-02.md'

 # ✅ CORRECT
@@ -145,14 +145,14 @@ outputFile: '{output_folder}/output.md'

 These patterns are **NEVER ALLOWED** in workflow step frontmatter:

-| Pattern | Why It's Wrong |
-|---------|----------------|
-| `workflow_path: '{project-root}/...'` | Use relative paths instead |
-| `thisStepFile: './step-XX.md'` | Almost never used - remove unless actually referenced |
-| `workflowFile: './workflow.md'` | Almost never used - remove unless actually referenced |
-| `{workflow_path}/steps/...` | Use `./step-XX.md` (same folder) |
-| `{workflow_path}/templates/...` | Use `../template.md` (parent folder) |
-| `{workflow_path}/data/...` | Use `./data/file.md` (subfolder) |
+| Pattern                               | Why It's Wrong                                        |
+| ------------------------------------- | ----------------------------------------------------- |
+| `workflow_path: '{project-root}/...'` | Use relative paths instead                            |
+| `thisStepFile: './step-XX.md'`        | Almost never used - remove unless actually referenced |
+| `workflowFile: './workflow.md'`       | Almost never used - remove unless actually referenced |
+| `./...`                               | Use `./step-XX.md` (same folder)                      |
+| `{workflow_path}/templates/...`       | Use `../template.md` (parent folder)                  |
+| `{workflow_path}/data/...`            | Use `./data/file.md` (subfolder)                      |

 ---

@@ -160,13 +160,13 @@ These patterns are **NEVER ALLOWED** in workflow step frontmatter:

 Use `snake_case` with descriptive prefixes:

-| Pattern   | Usage                  | Example                    |
-| --------- | ---------------------- | -------------------------- |
-| `{*_File}`   | File references        | `outputFile`, `nextStepFile`     |
-| `{*_Task}`   | Task references        | `advancedElicitationTask`       |
-| `{*_Workflow}` | Workflow references   | `partyModeWorkflow`            |
-| `{*_Template}` | Templates            | `productBriefTemplate`         |
-| `{*_Data}`    | Data files            | `dietaryData`                 |
+| Pattern        | Usage               | Example                      |
+| -------------- | ------------------- | ---------------------------- |
+| `{*_File}`     | File references     | `outputFile`, `nextStepFile` |
+| `{*_Task}`     | Task references     | `advancedElicitationTask`    |
+| `{*_Workflow}` | Workflow references | `partyModeWorkflow`          |
+| `{*_Template}` | Templates           | `productBriefTemplate`       |
+| `{*_Data}`     | Data files          | `dietaryData`                |

 ---

--- a/src/modules/bmb/workflows/workflow/data/step-type-patterns.md
+++ b/src/modules/bmb/workflows/workflow/data/step-type-patterns.md
@@ -11,7 +11,7 @@ All steps share this skeleton:
 ---
 name: 'step-[N]-[name]'
 description: '[what it does]'
-[file references - ONLY used variables]
+[file references - relative path and only if used in this steps file]
 ---

 # Step [N]: [Name]
@@ -76,10 +76,9 @@ description: '[what it does]'
 ---
 name: 'step-01-init'
 description: 'Initialize [workflow]'
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-[name].md'
+nextStepFile: './step-02-[name].md'
 outputFile: '{output_folder}/[output].md'
-templateFile: '{workflow_path}/templates/[template].md'
+templateFile: '../templates/[template].md'
 ---
 ```

@@ -97,7 +96,7 @@ templateFile: '{workflow_path}/templates/[template].md'

 **Frontmatter:** Add `continueFile` reference
 ```yaml
-continueFile: '{workflow_path}/steps/step-01b-continue.md'
+continueFile: './step-01b-continue.md'
 ```

 **Logic:**
@@ -140,7 +139,7 @@ workflowFile: '{workflow_path}/workflow.md'
 ```yaml
 ---
 name: 'step-[N]-[name]'
-nextStepFile: '{workflow_path}/steps/step-[N+1]-[name].md'
+nextStepFile: './step-[N+1]-[name].md'
 outputFile: '{output_folder}/[output].md'
 advancedElicitationTask: '{project-root}/.../advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/.../party-mode/workflow.md'
@@ -161,8 +160,8 @@ partyModeWorkflow: '{project-root}/.../party-mode/workflow.md'

 **Frontmatter:**
 ```yaml
-nextStepFile: '{workflow_path}/steps/step-[default].md'
-altStepFile: '{workflow_path}/steps/step-[alternate].md'
+nextStepFile: './step-[default].md'
+altStepFile: './step-[alternate].md'
 ```

 **Menu:** Custom letters (L/R/etc.) with branching logic
@@ -297,16 +296,16 @@ Mark workflow complete

 ## Step Size Guidelines

-| Type                     | Recommended | Maximum |
-| ------------------------ | ----------- | ------- |
-| Init                     | < 100       | 150     |
-| Init (with discovery)    | < 150       | 200     |
-| Continuation             | < 150       | 200     |
-| Middle (simple)           | < 150       | 200     |
-| Middle (complex)          | < 200       | 250     |
-| Branch                   | < 150       | 200     |
-| Validation sequence       | < 100       | 150     |
-| Final polish              | < 150       | 200     |
-| Final                    | < 150       | 200     |
+| Type                  | Recommended | Maximum |
+| --------------------- | ----------- | ------- |
+| Init                  | < 100       | 150     |
+| Init (with discovery) | < 150       | 200     |
+| Continuation          | < 150       | 200     |
+| Middle (simple)       | < 150       | 200     |
+| Middle (complex)      | < 200       | 250     |
+| Branch                | < 150       | 200     |
+| Validation sequence   | < 100       | 150     |
+| Final polish          | < 150       | 200     |
+| Final                 | < 150       | 200     |

 **If exceeded:** Split into multiple steps or extract to `/data/` files.
--- a/src/modules/bmb/workflows/workflow/steps-v/step-02-frontmatter-validation.md
+++ b/src/modules/bmb/workflows/workflow/steps-v/step-02-frontmatter-validation.md
@@ -60,7 +60,7 @@ Load {frontmatterStandards} to understand validation criteria.
 - `workflow_path: '...'` - use relative paths instead
 - `thisStepFile: '...'` - remove unless actually referenced in body
 - `workflowFile: '...'` - remove unless actually referenced in body
- `{workflow_path}/steps/...` - use `./step-XX.md`
+- `./...` - use `./step-XX.md`
 - `{workflow_path}/templates/...` - use `../template.md`

 ### 2. Validate EVERY Step File - Systematic Algorithm
@@ -132,10 +132,10 @@ Create report table:
 ```markdown
 ### Frontmatter Validation Results

-| File | Required | All Vars Used | Relative Paths | No Forbidden | Status |
-|------|----------|---------------|----------------|-------------|--------|
-| step-01-init.md | ✅ | ❌ Unused: thisStepFile, workflowFile | ✅ | ✅ | ❌ FAIL |
-| step-02-vision.md | ✅ | ✅ | ✅ | ✅ | ✅ PASS |
+| File              | Required | All Vars Used                        | Relative Paths | No Forbidden | Status |
+| ----------------- | -------- | ------------------------------------ | -------------- | ------------ | ------ |
+| step-01-init.md   | ✅        | ❌ Unused: thisStepFile, workflowFile | ✅              | ✅            | ❌ FAIL |
+| step-02-vision.md | ✅        | ✅                                    | ✅              | ✅            | ✅ PASS |
 ```

 ### 4. List All Violations
--- a/src/modules/bmb/workflows/workflow/templates/step-01-init-continuable-template.md
+++ b/src/modules/bmb/workflows/workflow/templates/step-01-init-continuable-template.md
@@ -17,11 +17,11 @@ workflow\*path: `{project-root}/_bmad/[module-path]/workflows/[workflow-name]`

 # File References (all use {variable} format in file)

-thisStepFile: `{workflow_path}/steps/step-01-init.md`
-nextStepFile: `{workflow_path}/steps/step-02-[step-name].md`
+thisStepFile: `./step-01-init.md`
+nextStepFile: `./step-02-[step-name].md`
 workflowFile: `{workflow_path}/workflow.md`
 outputFile: `{output_folder}/[output-file-name]-{project_name}.md`
-continueFile: `{workflow_path}/steps/step-01b-continue.md`
+continueFile: `./step-01b-continue.md`
 templateFile: `{workflow_path}/templates/[main-template].md`

 # Template References
--- a/src/modules/bmb/workflows/workflow/templates/step-1b-template.md
+++ b/src/modules/bmb/workflows/workflow/templates/step-1b-template.md
@@ -17,7 +17,7 @@ workflow\*path: '{project-root}/_bmad/[module-path]/workflows/[workflow-name]'

 # File References (all use {variable} format in file)

-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
 workflowFile: '{workflow_path}/workflow.md'

--- a/src/modules/bmb/workflows/workflow/templates/step-template.md
+++ b/src/modules/bmb/workflows/workflow/templates/step-template.md
@@ -15,9 +15,9 @@ workflow\*path: '{project-root}/_bmad/[module]/reference/workflows/[workflow-nam

 # File References (all use {variable} format in file)

-thisStepFile: '{workflow_path}/steps/step-[N]-[short-name].md'
-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
+thisStepFile: './step-[N]-[short-name].md'
+nextStep{N+1}: './step-[N+1]-[next-short-name].md' # Remove for final step or no next step
+altStep{Y}: './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'

--- a/src/modules/bmb/workflows/workflow/templates/workflow-template.md
+++ b/src/modules/bmb/workflows/workflow/templates/workflow-template.md
@@ -97,7 +97,7 @@ Copy the template above and replace:

 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.
+Example: Load, read the full file and then execute `./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

--- a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-01-init.md
+++ b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-01-init.md
@@ -6,8 +6,8 @@ description: 'Initialize the game brainstorming workflow and validate readiness'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-context.md'
+thisStepFile: './step-01-init.md'
+nextStepFile: './step-02-context.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/brainstorming-session-{date}.md'

--- a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-02-context.md
+++ b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-02-context.md
@@ -6,8 +6,8 @@ description: 'Load game-specific brainstorming context and techniques'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'

 # File References
-thisStepFile: '{workflow_path}/steps/step-02-context.md'
-nextStepFile: '{workflow_path}/steps/step-03-ideation.md'
+thisStepFile: './step-02-context.md'
+nextStepFile: './step-03-ideation.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/brainstorming-session-{date}.md'

--- a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-03-ideation.md
+++ b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-03-ideation.md
@@ -6,8 +6,8 @@ description: 'Execute the brainstorming session with game-specific techniques'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'

 # File References
-thisStepFile: '{workflow_path}/steps/step-03-ideation.md'
-nextStepFile: '{workflow_path}/steps/step-04-complete.md'
+thisStepFile: './step-03-ideation.md'
+nextStepFile: './step-04-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/brainstorming-session-{date}.md'

--- a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-04-complete.md
+++ b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-04-complete.md
@@ -6,7 +6,7 @@ description: 'Complete the brainstorming session with summary and next steps'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'

 # File References
-thisStepFile: '{workflow_path}/steps/step-04-complete.md'
+thisStepFile: './step-04-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/brainstorming-session-{date}.md'

--- a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md
+++ b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md
@@ -28,7 +28,7 @@ stepsCompleted: [1, 2, 3, ...] # Array of completed step numbers
 To begin, load and execute step-01-init.md:

 ```
-{workflow_path}/steps/step-01-init.md
+./step-01-init.md
 ```

 ## Critical Rules
--- a/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-01-init.md
+++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-01-init.md
@@ -6,9 +6,9 @@ description: 'Initialize the Game Brief workflow by detecting continuation state
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-vision.md'
-continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01-init.md'
+nextStepFile: './step-02-vision.md'
+continueStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'

--- a/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-01b-continue.md
+++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-01b-continue.md
@@ -6,7 +6,7 @@ description: 'Resume an interrupted Game Brief workflow from the last completed
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 ---
--- a/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-02-vision.md
+++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-02-vision.md
@@ -6,8 +6,8 @@ description: 'Define the core game vision including name, concept, pitch, and vi
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'

 # File References
-thisStepFile: '{workflow_path}/steps/step-02-vision.md'
-nextStepFile: '{workflow_path}/steps/step-03-market.md'
+thisStepFile: './step-02-vision.md'
+nextStepFile: './step-03-market.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'

--- a/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-03-market.md
+++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-03-market.md
@@ -6,8 +6,8 @@ description: 'Define target audience and market context'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'

 # File References
-thisStepFile: '{workflow_path}/steps/step-03-market.md'
-nextStepFile: '{workflow_path}/steps/step-04-fundamentals.md'
+thisStepFile: './step-03-market.md'
+nextStepFile: './step-04-fundamentals.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'

--- a/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-04-fundamentals.md
+++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-04-fundamentals.md
@@ -6,8 +6,8 @@ description: 'Define core gameplay pillars, mechanics, and player experience goa
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'

 # File References
-thisStepFile: '{workflow_path}/steps/step-04-fundamentals.md'
-nextStepFile: '{workflow_path}/steps/step-05-scope.md'
+thisStepFile: './step-04-fundamentals.md'
+nextStepFile: './step-05-scope.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'

--- a/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-05-scope.md
+++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-05-scope.md
@@ -6,8 +6,8 @@ description: 'Define project scope including platforms, constraints, and resourc
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'

 # File References
-thisStepFile: '{workflow_path}/steps/step-05-scope.md'
-nextStepFile: '{workflow_path}/steps/step-06-references.md'
+thisStepFile: './step-05-scope.md'
+nextStepFile: './step-06-references.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'

--- a/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-06-references.md
+++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-06-references.md
@@ -6,8 +6,8 @@ description: 'Define inspiration games, competitive analysis, and key differenti
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'

 # File References
-thisStepFile: '{workflow_path}/steps/step-06-references.md'
-nextStepFile: '{workflow_path}/steps/step-07-content.md'
+thisStepFile: './step-06-references.md'
+nextStepFile: './step-07-content.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'

--- a/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-07-content.md
+++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-07-content.md
@@ -6,8 +6,8 @@ description: 'Define content framework, art/audio direction, and risk assessment
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'

 # File References
-thisStepFile: '{workflow_path}/steps/step-07-content.md'
-nextStepFile: '{workflow_path}/steps/step-08-complete.md'
+thisStepFile: './step-07-content.md'
+nextStepFile: './step-08-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'

--- a/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-08-complete.md
+++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-08-complete.md
@@ -6,7 +6,7 @@ description: 'Define success criteria and complete the game brief with handoff g
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'

 # File References
-thisStepFile: '{workflow_path}/steps/step-08-complete.md'
+thisStepFile: './step-08-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-01-init.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-01-init.md
@@ -6,9 +6,9 @@ description: 'Initialize the GDD workflow by detecting continuation state and se
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-context.md'
-continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01-init.md'
+nextStepFile: './step-02-context.md'
+continueStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-01b-continue.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-01b-continue.md
@@ -6,7 +6,7 @@ description: 'Resume an interrupted GDD workflow from the last completed step'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'
 ---
--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-02-context.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-02-context.md
@@ -6,8 +6,8 @@ description: 'Load game context from brief and determine the game type'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-02-context.md'
-nextStepFile: '{workflow_path}/steps/step-03-platforms.md'
+thisStepFile: './step-02-context.md'
+nextStepFile: './step-03-platforms.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-03-platforms.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-03-platforms.md
@@ -6,8 +6,8 @@ description: 'Define target platforms and target audience for the game'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-03-platforms.md'
-nextStepFile: '{workflow_path}/steps/step-04-vision.md'
+thisStepFile: './step-03-platforms.md'
+nextStepFile: './step-04-vision.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-04-vision.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-04-vision.md
@@ -6,8 +6,8 @@ description: 'Define project goals, context, and unique selling points'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-04-vision.md'
-nextStepFile: '{workflow_path}/steps/step-05-core-gameplay.md'
+thisStepFile: './step-04-vision.md'
+nextStepFile: './step-05-core-gameplay.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-05-core-gameplay.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-05-core-gameplay.md
@@ -6,8 +6,8 @@ description: 'Define game pillars, core gameplay loop, and win/loss conditions'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-05-core-gameplay.md'
-nextStepFile: '{workflow_path}/steps/step-06-mechanics.md'
+thisStepFile: './step-05-core-gameplay.md'
+nextStepFile: './step-06-mechanics.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-06-mechanics.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-06-mechanics.md
@@ -6,8 +6,8 @@ description: 'Define primary game mechanics and control schemes'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-06-mechanics.md'
-nextStepFile: '{workflow_path}/steps/step-07-game-type.md'
+thisStepFile: './step-06-mechanics.md'
+nextStepFile: './step-07-game-type.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-07-game-type.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-07-game-type.md
@@ -6,8 +6,8 @@ description: 'Process game-type specific sections from the loaded game type guid
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-07-game-type.md'
-nextStepFile: '{workflow_path}/steps/step-08-progression.md'
+thisStepFile: './step-07-game-type.md'
+nextStepFile: './step-08-progression.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-08-progression.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-08-progression.md
@@ -6,8 +6,8 @@ description: 'Define player progression systems and game balance'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-08-progression.md'
-nextStepFile: '{workflow_path}/steps/step-09-levels.md'
+thisStepFile: './step-08-progression.md'
+nextStepFile: './step-09-levels.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-09-levels.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-09-levels.md
@@ -6,8 +6,8 @@ description: 'Define level design framework and level progression'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-09-levels.md'
-nextStepFile: '{workflow_path}/steps/step-10-art-audio.md'
+thisStepFile: './step-09-levels.md'
+nextStepFile: './step-10-art-audio.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-10-art-audio.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-10-art-audio.md
@@ -6,8 +6,8 @@ description: 'Define art style and audio direction'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-10-art-audio.md'
-nextStepFile: '{workflow_path}/steps/step-11-technical.md'
+thisStepFile: './step-10-art-audio.md'
+nextStepFile: './step-11-technical.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-11-technical.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-11-technical.md
@@ -6,8 +6,8 @@ description: 'Define technical specifications and requirements'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-11-technical.md'
-nextStepFile: '{workflow_path}/steps/step-12-epics.md'
+thisStepFile: './step-11-technical.md'
+nextStepFile: './step-12-epics.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-12-epics.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-12-epics.md
@@ -6,8 +6,8 @@ description: 'Define development epics and high-level story breakdown'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-12-epics.md'
-nextStepFile: '{workflow_path}/steps/step-13-metrics.md'
+thisStepFile: './step-12-epics.md'
+nextStepFile: './step-13-metrics.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'
 epicsOutputFile: '{output_folder}/epics.md'
--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-13-metrics.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-13-metrics.md
@@ -6,8 +6,8 @@ description: 'Define success metrics for technical and gameplay evaluation'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-13-metrics.md'
-nextStepFile: '{workflow_path}/steps/step-14-complete.md'
+thisStepFile: './step-13-metrics.md'
+nextStepFile: './step-14-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'

--- a/src/modules/bmgd/workflows/2-design/gdd/steps/step-14-complete.md
+++ b/src/modules/bmgd/workflows/2-design/gdd/steps/step-14-complete.md
@@ -6,7 +6,7 @@ description: 'Document out of scope items, capture assumptions, and provide hand
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'

 # File References
-thisStepFile: '{workflow_path}/steps/step-14-complete.md'
+thisStepFile: './step-14-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'
 epicsFile: '{output_folder}/epics.md'
--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-01-init.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-01-init.md
@@ -6,9 +6,9 @@ description: 'Initialize narrative workflow, load GDD context, and assess narrat
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
-nextStepFile: '{workflow_path}/steps/step-02-foundation.md'
+thisStepFile: './step-01-init.md'
+continueStepFile: './step-01b-continue.md'
+nextStepFile: './step-02-foundation.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 templateFile: '{workflow_path}/templates/narrative-template.md'
--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-01b-continue.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-01b-continue.md
@@ -6,21 +6,21 @@ description: 'Continue an existing narrative workflow from where it left off'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

 # Step Files (for routing)
-step02: '{workflow_path}/steps/step-02-foundation.md'
-step03: '{workflow_path}/steps/step-03-story.md'
-step04: '{workflow_path}/steps/step-04-characters.md'
-step05: '{workflow_path}/steps/step-05-world.md'
-step06: '{workflow_path}/steps/step-06-dialogue.md'
-step07: '{workflow_path}/steps/step-07-environmental.md'
-step08: '{workflow_path}/steps/step-08-delivery.md'
-step09: '{workflow_path}/steps/step-09-integration.md'
-step10: '{workflow_path}/steps/step-10-production.md'
-step11: '{workflow_path}/steps/step-11-complete.md'
+step02: './step-02-foundation.md'
+step03: './step-03-story.md'
+step04: './step-04-characters.md'
+step05: './step-05-world.md'
+step06: './step-06-dialogue.md'
+step07: './step-07-environmental.md'
+step08: './step-08-delivery.md'
+step09: './step-09-integration.md'
+step10: './step-10-production.md'
+step11: './step-11-complete.md'
 ---

 # Step 1b: Continue Existing Narrative
--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-02-foundation.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-02-foundation.md
@@ -6,8 +6,8 @@ description: 'Define narrative premise, themes, tone, and story structure'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-02-foundation.md'
-nextStepFile: '{workflow_path}/steps/step-03-story.md'
+thisStepFile: './step-02-foundation.md'
+nextStepFile: './step-03-story.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-03-story.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-03-story.md
@@ -6,8 +6,8 @@ description: 'Define major story beats and narrative pacing'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-03-story.md'
-nextStepFile: '{workflow_path}/steps/step-04-characters.md'
+thisStepFile: './step-03-story.md'
+nextStepFile: './step-04-characters.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-04-characters.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-04-characters.md
@@ -6,8 +6,8 @@ description: 'Develop all characters including protagonists, antagonists, suppor
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-04-characters.md'
-nextStepFile: '{workflow_path}/steps/step-05-world.md'
+thisStepFile: './step-04-characters.md'
+nextStepFile: './step-05-world.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-05-world.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-05-world.md
@@ -6,8 +6,8 @@ description: 'Build the world including setting, history, factions, and key loca
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-05-world.md'
-nextStepFile: '{workflow_path}/steps/step-06-dialogue.md'
+thisStepFile: './step-05-world.md'
+nextStepFile: './step-06-dialogue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-06-dialogue.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-06-dialogue.md
@@ -6,8 +6,8 @@ description: 'Define dialogue style, key conversations, and branching systems'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-06-dialogue.md'
-nextStepFile: '{workflow_path}/steps/step-07-environmental.md'
+thisStepFile: './step-06-dialogue.md'
+nextStepFile: './step-07-environmental.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-07-environmental.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-07-environmental.md
@@ -6,8 +6,8 @@ description: 'Plan environmental storytelling including visual, audio, and found
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-07-environmental.md'
-nextStepFile: '{workflow_path}/steps/step-08-delivery.md'
+thisStepFile: './step-07-environmental.md'
+nextStepFile: './step-08-delivery.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-08-delivery.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-08-delivery.md
@@ -6,8 +6,8 @@ description: 'Design narrative delivery methods including cutscenes, in-game sto
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-08-delivery.md'
-nextStepFile: '{workflow_path}/steps/step-09-integration.md'
+thisStepFile: './step-08-delivery.md'
+nextStepFile: './step-09-integration.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-09-integration.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-09-integration.md
@@ -6,8 +6,8 @@ description: 'Define how narrative integrates with gameplay including gating, ag
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-09-integration.md'
-nextStepFile: '{workflow_path}/steps/step-10-production.md'
+thisStepFile: './step-09-integration.md'
+nextStepFile: './step-10-production.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-10-production.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-10-production.md
@@ -6,8 +6,8 @@ description: 'Plan production scope including writing estimates, localization, a
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-10-production.md'
-nextStepFile: '{workflow_path}/steps/step-11-complete.md'
+thisStepFile: './step-10-production.md'
+nextStepFile: './step-11-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/steps/step-11-complete.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/steps/step-11-complete.md
@@ -6,7 +6,7 @@ description: 'Complete the narrative workflow with final summary, visualizations
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'

 # File References
-thisStepFile: '{workflow_path}/steps/step-11-complete.md'
+thisStepFile: './step-11-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'

--- a/src/modules/bmgd/workflows/2-design/narrative/workflow.md
+++ b/src/modules/bmgd/workflows/2-design/narrative/workflow.md
@@ -36,7 +36,7 @@ stepsCompleted: [1, 2, 3, ...] # Array of completed step numbers
 To begin, load and execute step-01-init.md:

 ```
-{workflow_path}/steps/step-01-init.md
+./step-01-init.md
 ```

 ## Critical Rules
--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-01-init.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-01-init.md
@@ -6,9 +6,9 @@ description: 'Initialize the architecture workflow, validate readiness, and disc
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
-nextStepFile: '{workflow_path}/steps/step-02-context.md'
+thisStepFile: './step-01-init.md'
+continueStepFile: './step-01b-continue.md'
+nextStepFile: './step-02-context.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 templateFile: '{workflow_path}/templates/architecture-template.md'
--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-01b-continue.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-01b-continue.md
@@ -6,19 +6,19 @@ description: 'Continue an existing architecture workflow from where it left off'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'

 # Step Files (for routing)
-step02: '{workflow_path}/steps/step-02-context.md'
-step03: '{workflow_path}/steps/step-03-starter.md'
-step04: '{workflow_path}/steps/step-04-decisions.md'
-step05: '{workflow_path}/steps/step-05-crosscutting.md'
-step06: '{workflow_path}/steps/step-06-structure.md'
-step07: '{workflow_path}/steps/step-07-patterns.md'
-step08: '{workflow_path}/steps/step-08-validation.md'
-step09: '{workflow_path}/steps/step-09-complete.md'
+step02: './step-02-context.md'
+step03: './step-03-starter.md'
+step04: './step-04-decisions.md'
+step05: './step-05-crosscutting.md'
+step06: './step-06-structure.md'
+step07: './step-07-patterns.md'
+step08: './step-08-validation.md'
+step09: './step-09-complete.md'
 ---

 # Step 1b: Continue Existing Architecture
--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-02-context.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-02-context.md
@@ -6,8 +6,8 @@ description: 'Load and understand project context from GDD and supporting docume
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-02-context.md'
-nextStepFile: '{workflow_path}/steps/step-03-starter.md'
+thisStepFile: './step-02-context.md'
+nextStepFile: './step-03-starter.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'

--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-03-starter.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-03-starter.md
@@ -6,8 +6,8 @@ description: 'Discover and evaluate game engine and starter template options'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-03-starter.md'
-nextStepFile: '{workflow_path}/steps/step-04-decisions.md'
+thisStepFile: './step-03-starter.md'
+nextStepFile: './step-04-decisions.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'

--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-04-decisions.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-04-decisions.md
@@ -6,8 +6,8 @@ description: 'Facilitate collaborative architectural decision making for game sy
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-04-decisions.md'
-nextStepFile: '{workflow_path}/steps/step-05-crosscutting.md'
+thisStepFile: './step-04-decisions.md'
+nextStepFile: './step-05-crosscutting.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'

--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-05-crosscutting.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-05-crosscutting.md
@@ -6,8 +6,8 @@ description: 'Address cross-cutting concerns that affect all game systems'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-05-crosscutting.md'
-nextStepFile: '{workflow_path}/steps/step-06-structure.md'
+thisStepFile: './step-05-crosscutting.md'
+nextStepFile: './step-06-structure.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'

--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-06-structure.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-06-structure.md
@@ -6,8 +6,8 @@ description: 'Define project structure, directory organization, and architectura
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-06-structure.md'
-nextStepFile: '{workflow_path}/steps/step-07-patterns.md'
+thisStepFile: './step-06-structure.md'
+nextStepFile: './step-07-patterns.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'

--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-07-patterns.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-07-patterns.md
@@ -6,8 +6,8 @@ description: 'Design implementation patterns and novel architectural patterns fo
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-07-patterns.md'
-nextStepFile: '{workflow_path}/steps/step-08-validation.md'
+thisStepFile: './step-07-patterns.md'
+nextStepFile: './step-08-validation.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'

--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-08-validation.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-08-validation.md
@@ -6,8 +6,8 @@ description: 'Validate architectural coherence and completeness'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-08-validation.md'
-nextStepFile: '{workflow_path}/steps/step-09-complete.md'
+thisStepFile: './step-08-validation.md'
+nextStepFile: './step-09-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 checklistFile: '{workflow_path}/checklist.md'
--- a/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-09-complete.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-09-complete.md
@@ -6,7 +6,7 @@ description: 'Complete the architecture workflow with final review and handoff g
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'

 # File References
-thisStepFile: '{workflow_path}/steps/step-09-complete.md'
+thisStepFile: './step-09-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'

--- a/src/modules/bmgd/workflows/3-technical/game-architecture/workflow.md
+++ b/src/modules/bmgd/workflows/3-technical/game-architecture/workflow.md
@@ -34,7 +34,7 @@ stepsCompleted: [1, 2, 3, ...] # Array of completed step numbers
 To begin, load and execute step-01-init.md:

 ```
-{workflow_path}/steps/step-01-init.md
+./step-01-init.md
 ```

 ## Critical Rules
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/data/domain-complexity.csv
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/data/domain-complexity.csv
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/data/project-types.csv
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/data/project-types.csv
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-01-init.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-01-init.md
@@ -2,19 +2,13 @@
 name: 'step-01-init'
 description: 'Initialize the PRD workflow by detecting continuation state and setting up the document'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-discovery.md'
-continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-02-discovery.md'
+continueStepFile: './step-01b-continue.md'
 outputFile: '{planning_artifacts}/prd.md'

-
-# Template References
-prdTemplate: '{workflow_path}/prd-template.md'
+# Template Reference
+prdTemplate: '../templates/prd-template.md'
 ---

 # Step 1: Workflow Initialization
@@ -157,7 +151,7 @@ Display menu after setup report:

 #### Menu Handling Logic:

- IF C: Update frontmatter with `stepsCompleted: [1]`, then load, read entire {nextStepFile}, then execute {nextStepFile}
+- IF C: Update output file frontmatter, adding this step name to the end of the list of stepsCompleted, then load, read entire {nextStepFile}, then execute {nextStepFile}
 - IF user provides additional files: Load them, update inputDocuments and documentCounts, redisplay report
 - IF user asks questions: Answer and redisplay menu

@@ -168,7 +162,7 @@ Display menu after setup report:

 ## CRITICAL STEP COMPLETION NOTE

-ONLY WHEN [C continue option] is selected and [frontmatter properly updated with stepsCompleted: [1] and documentCounts], will you then load and read fully `{nextStepFile}` to execute and begin project discovery.
+ONLY WHEN [C continue option] is selected and [frontmatter properly updated with this step added to stepsCompleted and documentCounts], will you then load and read fully `{nextStepFile}` to execute and begin project discovery.

 ---

@@ -182,7 +176,7 @@ ONLY WHEN [C continue option] is selected and [frontmatter properly updated with
 - All discovered files tracked in frontmatter `inputDocuments`
 - User clearly informed of brownfield vs greenfield status
 - Menu presented and user input handled correctly
- Frontmatter updated with `stepsCompleted: [1]` before proceeding
+- Frontmatter updated with this step name added to stepsCompleted before proceeding

 ### ❌ SYSTEM FAILURE:

--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-01b-continue.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-01b-continue.md
@@ -2,12 +2,7 @@
 name: 'step-01b-continue'
 description: 'Resume an interrupted PRD workflow from the last completed step'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
-workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/prd.md'
 ---

@@ -60,10 +55,9 @@ Resume the PRD workflow from where it was left off, ensuring smooth continuation
 **State Assessment:**
 Review the frontmatter to understand:

- `stepsCompleted`: Which steps are already done
- `lastStep`: The most recently completed step number
+- `stepsCompleted`: Array of completed step filenames
+- Last element of `stepsCompleted` array: The most recently completed step
 - `inputDocuments`: What context was already loaded
- `documentCounts`: briefs, research, brainstorming, projectDocs counts
 - All other frontmatter variables

 ### 2. Restore Context Documents
@@ -74,47 +68,27 @@ Review the frontmatter to understand:
 - This ensures you have full context for continuation
 - Don't discover new documents - only reload what was previously processed

-### 3. Present Current Progress
+### 3. Determine Next Step

-**Progress Report to User:**
-"Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.
+**Simplified Next Step Logic:**
+1. Get the last element from the `stepsCompleted` array (this is the filename of the last completed step, e.g., "step-03-success.md")
+2. Load that step file and read its frontmatter
+3. Extract the `nextStepFile` value from the frontmatter
+4. That's the next step to load!

-**Current Progress:**
+**Example:**
+- If `stepsCompleted = ["step-01-init.md", "step-02-discovery.md", "step-03-success.md"]`
+- Last element is `"step-03-success.md"`
+- Load `step-03-success.md`, read its frontmatter
+- Find `nextStepFile: './step-04-journeys.md'`
+- Next step to load is `./step-04-journeys.md`

- Steps completed: {stepsCompleted}
- Last worked on: Step {lastStep}
- Context documents available: {len(inputDocuments)} files
+### 4. Handle Workflow Completion

-**Document Status:**
-
- Current PRD document is ready with all completed sections
- Ready to continue from where we left off
-
-Does this look right, or do you want to make any adjustments before we proceed?"
-
-### 4. Determine Continuation Path
-
-**Next Step Logic:**
-Based on `lastStep` value, determine which step to load next:
-
- If `lastStep = 1` → Load `./step-02-discovery.md`
- If `lastStep = 2` → Load `./step-03-success.md`
- If `lastStep = 3` → Load `./step-04-journeys.md`
- If `lastStep = 4` → Load `./step-05-domain.md`
- If `lastStep = 5` → Load `./step-06-innovation.md`
- If `lastStep = 6` → Load `./step-07-project-type.md`
- If `lastStep = 7` → Load `./step-08-scoping.md`
- If `lastStep = 8` → Load `./step-09-functional.md`
- If `lastStep = 9` → Load `./step-10-nonfunctional.md`
- If `lastStep = 10` → Load `./step-11-complete.md`
- If `lastStep = 11` → Workflow already complete
-
-### 5. Handle Workflow Completion
-
-**If workflow already complete (`lastStep = 11`):**
+**If `stepsCompleted` array contains `"step-11-complete.md"`:**
 "Great news! It looks like we've already completed the PRD workflow for {{project_name}}.

-The final document is ready at `{outputFile}` with all sections completed through step 11.
+The final document is ready at `{outputFile}` with all sections completed.

 Would you like me to:

@@ -124,16 +98,29 @@ Would you like me to:

 What would be most helpful?"

-### 6. Present MENU OPTIONS
+### 5. Present Current Progress

 **If workflow not complete:**
-Display: "Ready to continue with Step {nextStepNumber}?
+"Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.

-**Select an Option:** [C] Continue to next step"
+**Current Progress:**
+- Last completed: {last step filename from stepsCompleted array}
+- Next up: {nextStepFile determined from that step's frontmatter}
+- Context documents available: {len(inputDocuments)} files
+
+**Document Status:**
+- Current PRD document is ready with all completed sections
+- Ready to continue from where we left off
+
+Does this look right, or do you want to make any adjustments before we proceed?"
+
+### 6. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to {next step name}"

 #### Menu Handling Logic:

- IF C: Load, read entire file, then execute the appropriate next step file based on `lastStep`
+- IF C: Load, read entire file, then execute the {nextStepFile} determined in step 3
 - IF Any other comments or queries: respond and redisplay menu

 #### EXECUTION RULES:
@@ -143,7 +130,7 @@ Display: "Ready to continue with Step {nextStepNumber}?

 ## CRITICAL STEP COMPLETION NOTE

-ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the appropriate next step file to resume the workflow.
+ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the {nextStepFile} to resume the workflow.

 ---

@@ -160,7 +147,7 @@ ONLY WHEN [C continue option] is selected and [current state confirmed], will yo

 - Discovering new input documents instead of reloading existing ones
 - Modifying content from already completed steps
- Loading wrong next step based on `lastStep` value
+- Failing to extract nextStepFile from the last completed step's frontmatter
 - Proceeding without user confirmation of current state

 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-02-discovery.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-02-discovery.md
@@ -0,0 +1,197 @@
+---
+name: 'step-02-discovery'
+description: 'Discover project type, domain, and context through collaborative dialogue'
+
+# File References
+nextStepFile: './step-03-success.md'
+outputFile: '{planning_artifacts}/prd.md'
+
+# Data Files
+projectTypesCSV: '../data/project-types.csv'
+domainComplexityCSV: '../data/domain-complexity.csv'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 2: Project Discovery
+
+**Progress: Step 2 of 13** - Next: Product Vision
+
+## STEP GOAL:
+
+Discover and classify the project - understand what type of product this is, what domain it operates in, and the project context (greenfield vs brownfield).
+
+## 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 the entire file is read
+- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused PM facilitator collaborating with an expert peer
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+
+### Step-Specific Rules:
+
+- 🎯 Focus on classification and understanding - no content generation yet
+- 🚫 FORBIDDEN to generate executive summary or vision statements (that's next steps)
+- 💬 APPROACH: Natural conversation to understand the project
+- 🎯 LOAD classification data BEFORE starting discovery conversation
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after classification complete
+- 💾 ONLY save classification to frontmatter when user chooses C (Continue)
+- 📖 Update frontmatter, adding this step to the end of the list of stepsCompleted
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from step 1 are available
+- Input documents already loaded are in memory (product briefs, research, brainstorming, project docs)
+- **Document counts available in frontmatter `documentCounts`**
+- Classification CSV data will be loaded in this step only
+- No executive summary or vision content yet (that's steps 2b and 2c)
+
+## YOUR TASK:
+
+Discover and classify the project through natural conversation:
+- What type of product is this? (web app, API, mobile, etc.)
+- What domain does it operate in? (healthcare, fintech, e-commerce, etc.)
+- What's the project context? (greenfield new product vs brownfield existing system)
+- How complex is this domain? (low, medium, high)
+
+## DISCOVERY SEQUENCE:
+
+### 1. Check Document State
+
+Read the frontmatter from `{outputFile}` to get document counts:
+- `briefCount` - Product briefs available
+- `researchCount` - Research documents available
+- `brainstormingCount` - Brainstorming docs available
+- `projectDocsCount` - Existing project documentation
+
+**Announce your understanding:**
+
+"From step 1, I have loaded:
+- Product briefs: {{briefCount}}
+- Research: {{researchCount}}
+- Brainstorming: {{brainstormingCount}}
+- Project docs: {{projectDocsCount}}
+
+{{if projectDocsCount > 0}}This is a brownfield project - I'll focus on understanding what you want to add or change.{{else}}This is a greenfield project - I'll help you define the full product vision.{{/if}}"
+
+### 2. Load Classification Data
+
+Load classification reference data:
+- Load `{projectTypesCSV}` - project types with detection signals
+- Load `{domainComplexityCSV}` - domain complexity levels
+- Keep in memory for intelligent classification
+
+### 3. Begin Discovery Conversation
+
+**Start with what you know:**
+
+If the user has a product brief or project docs, acknowledge them and share your understanding. Then ask clarifying questions to deepen your understanding.
+
+If this is a greenfield project with no docs, start with open-ended discovery:
+- What problem does this solve?
+- Who's it for?
+- What excites you about building this?
+
+**Listen for classification signals:**
+
+As the user describes their product, match against:
+- **Project type signals** (API, mobile, SaaS, etc.)
+- **Domain signals** (healthcare, fintech, education, etc.)
+- **Complexity indicators** (regulated industries, novel technology, etc.)
+
+### 4. Confirm Classification
+
+Once you have enough understanding, share your classification:
+
+"I'm hearing this as:
+- **Project Type:** {{detectedType}}
+- **Domain:** {{detectedDomain}}
+- **Complexity:** {{complexityLevel}}
+
+Does this sound right to you?"
+
+Let the user confirm or refine your classification.
+
+### 5. Save Classification to Frontmatter
+
+When user selects 'C', update frontmatter with classification:
+```yaml
+classification:
+  projectType: {{projectType}}
+  domain: {{domain}}
+  complexity: {{complexityLevel}}
+  projectContext: {{greenfield|brownfield}}
+```
+
+### N. Present MENU OPTIONS
+
+Present the project classification for review, then display menu:
+
+"Based on our conversation, I've discovered and classified your project.
+
+**Here's the classification:**
+
+**Project Type:** {{detectedType}}
+**Domain:** {{detectedDomain}}
+**Complexity:** {{complexityLevel}}
+**Project Context:** {{greenfield|brownfield}}
+
+**What would you like to do?**"
+
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Product Vision (Step 2b of 13)"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current classification, process the enhanced insights that come back, ask user if they accept the improvements, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the current classification, process the collaborative insights, ask user if they accept the changes, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
+- IF C: Save classification to {outputFile} frontmatter, add this step name to the end of stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu
+
+#### EXECUTION RULES:
+- 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
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [classification saved to frontmatter], will you then load and read fully `{nextStepFile}` to explore product vision.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Document state checked and announced to user
+- Classification data loaded and used intelligently
+- Natural conversation to understand project type, domain, complexity
+- Classification validated with user before saving
+- Frontmatter updated with classification when C selected
+- User's existing documents acknowledged and built upon
+
+### ❌ SYSTEM FAILURE:
+
+- Not reading documentCounts from frontmatter first
+- Skipping classification data loading
+- Generating executive summary or vision content (that's later steps!)
+- Not validating classification with user
+- Being prescriptive instead of having natural conversation
+- Proceeding without user selecting 'C'
+
+**Master Rule:** This is classification and understanding only. No content generation yet. Build on what the user already has. Have natural conversations, don't follow scripts.
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-03-success.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-03-success.md
@@ -2,13 +2,8 @@
 name: 'step-03-success'
 description: 'Define comprehensive success criteria covering user, business, and technical success'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-03-success.md'
-nextStepFile: '{workflow_path}/steps/step-04-journeys.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-04-journeys.md'
 outputFile: '{planning_artifacts}/prd.md'

 # Task References
@@ -37,24 +32,9 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 🎯 Show your analysis before taking any action
 - ⚠️ Present A/P/C menu after generating success criteria content
 - 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected

-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper insights about success metrics
- **P (Party Mode)**: Bring multiple perspectives to define comprehensive success criteria
- **C (Continue)**: Save the content to the document and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding
-
 ## CONTEXT BOUNDARIES:

 - Current document and frontmatter from previous steps are available
@@ -211,43 +191,30 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Content about future vision based on conversation]
 ```

-### 8. Present Content and Menu
+### 8. Present MENU OPTIONS

-Show the generated content and present choices:
-"I've drafted our success criteria and scope definition based on our conversation.
+Present the success criteria content for user review, then display menu:
+
+"Based on our conversation, I've drafted success criteria and scope definition.

 **Here's what I'll add to the document:**

-[Show the complete markdown content from step 7]
+[Show the complete markdown content from section 7]

-**What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper and refine these success metrics
-[P] Party Mode - Bring in different perspectives on success criteria
-[C] Continue - Save success criteria and move to User Journey Mapping (Step 4 of 11)"
+**What would you like to do?**"

-### 9. Handle Menu Selection
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to User Journey Mapping (Step 4 of 11)"

-#### If 'A' (Advanced Elicitation):
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current success criteria content, process the enhanced success metrics that come back, ask user "Accept these improvements to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the current success criteria, process the collaborative improvements to metrics and scope, ask user "Accept these changes to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu

- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current success criteria content
- Process the enhanced success metrics that come back
- Ask user: "Accept these improvements to the success criteria? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current success criteria
- Process the collaborative improvements to metrics and scope
- Ask user: "Accept these changes to the success criteria? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
- Append the final content to `{outputFile}`
- Update frontmatter: add this step to the end of the steps completed array
- Load `./step-04-journeys.md`
+#### EXECUTION RULES:
+- 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

 ## APPEND TO DOCUMENT:

--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-04-journeys.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-04-journeys.md
@@ -2,13 +2,8 @@
 name: 'step-04-journeys'
 description: 'Map ALL user types that interact with the system with narrative story-based journeys'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-04-journeys.md'
-nextStepFile: '{workflow_path}/steps/step-05-domain.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-05-domain.md'
 outputFile: '{planning_artifacts}/prd.md'

 # Task References
@@ -37,24 +32,9 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 🎯 Show your analysis before taking any action
 - ⚠️ Present A/P/C menu after generating journey content
 - 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected

-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper journey insights
- **P (Party Mode)**: Bring multiple perspectives to map comprehensive user journeys
- **C (Continue)**: Save the content to the document and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding
-
 ## CONTEXT BOUNDARIES:

 - Current document and frontmatter from previous steps are available
@@ -205,43 +185,30 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Summary of capabilities revealed by journeys based on conversation]
 ```

-### 7. Present Content and Menu
+### 7. Present MENU OPTIONS

-Show the generated journey content and present choices:
-"I've mapped out the user journeys based on our conversation. Each journey reveals different capabilities needed for {{project_name}}.
+Present the user journey content for review, then display menu:
+
+"Based on our conversation, I've mapped out user journeys. Each journey reveals different capabilities needed for {{project_name}}.

 **Here's what I'll add to the document:**

-[Show the complete markdown content from step 6]
+[Show the complete markdown content from section 6]

-**What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper into these user journeys
-[P] Party Mode - Bring different perspectives to ensure we have all journeys
-[C] Continue - Save this and move to Domain Requirements (Step 5 of 11)"
+**What would you like to do?**"

-### 8. Handle Menu Selection
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Domain Requirements (Step 5 of 11)"

-#### If 'A' (Advanced Elicitation):
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current journey content, process the enhanced journey insights that come back, ask user "Accept these improvements to the user journeys? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the current journeys, process the collaborative journey improvements and additions, ask user "Accept these changes to the user journeys? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu

- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current journey content
- Process the enhanced journey insights that come back
- Ask user: "Accept these improvements to the user journeys? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current journeys
- Process the collaborative journey improvements and additions
- Ask user: "Accept these changes to the user journeys? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
- Append the final content to `{outputFile}`
- Update frontmatter: add this step name to the end of the steps completed array
- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md` (or determine if step is optional based on domain complexity)
+#### EXECUTION RULES:
+- 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

 ## APPEND TO DOCUMENT:

--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-05-domain.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-05-domain.md
@@ -0,0 +1,193 @@
+---
+name: 'step-05-domain'
+description: 'Explore domain-specific requirements for complex domains (optional step)'
+
+# File References
+nextStepFile: './step-06-innovation.md'
+outputFile: '{planning_artifacts}/prd.md'
+domainComplexityCSV: '../data/domain-complexity.csv'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 5: Domain-Specific Requirements (Optional)
+
+**Progress: Step 5 of 13** - Next: Innovation Focus
+
+## STEP GOAL:
+
+For complex domains only that have a mapping in {domainComplexityCSV}, explore domain-specific constraints, compliance requirements, and technical considerations that shape the product.
+
+## 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 the entire file is read
+- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused PM facilitator collaborating with an expert peer
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise
+
+### Step-Specific Rules:
+
+- 🎯 This step is OPTIONAL - only needed for complex domains
+- 🚫 SKIP if domain complexity is "low" from step-02
+- 💬 APPROACH: Natural conversation to discover domain-specific needs
+- 🎯 Focus on constraints, compliance, and domain patterns
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Check domain complexity from step-02 classification first
+- ⚠️ If complexity is "low", offer to skip this step
+- ⚠️ Present A/P/C menu after domain requirements defined (or skipped)
+- 💾 ONLY save when user chooses C (Continue)
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Domain classification from step-02 is available
+- If complexity is low, this step may be skipped
+- Domain CSV data provides complexity reference
+- Focus on domain-specific constraints, not general requirements
+
+## YOUR TASK:
+
+For complex domains, explore what makes this domain special:
+- **Compliance requirements** - regulations, standards, certifications
+- **Technical constraints** - security, privacy, integration requirements
+- **Domain patterns** - common patterns, best practices, anti-patterns
+- **Risks and mitigations** - what could go wrong, how to prevent it
+
+## DOMAIN DISCOVERY SEQUENCE:
+
+### 1. Check Domain Complexity
+
+**Review classification from step-02:**
+
+- What's the domain complexity level? (low/medium/high)
+- What's the specific domain? (healthcare, fintech, education, etc.)
+
+**If complexity is LOW:**
+
+Offer to skip:
+"The domain complexity from our discovery is low. We may not need deep domain-specific requirements. Would you like to:
+- [C] Skip this step and move to Innovation
+- [D] Do domain exploration anyway"
+
+**If complexity is MEDIUM or HIGH:**
+
+Proceed with domain exploration.
+
+### 2. Load Domain Reference Data
+
+Load `{domainComplexityCSV}` to understand:
+- Typical concerns for this domain
+- Common compliance requirements
+- Technical constraints to consider
+
+### 3. Explore Domain-Specific Concerns
+
+**Start with what you know:**
+
+Acknowledge the domain and explore what makes it complex:
+- What regulations apply? (HIPAA, PCI-DSS, GDPR, SOX, etc.)
+- What standards matter? (ISO, NIST, domain-specific standards)
+- What certifications are needed? (security, privacy, domain-specific)
+- What integrations are required? (EMR systems, payment processors, etc.)
+
+**Explore technical constraints:**
+- Security requirements (encryption, audit logs, access control)
+- Privacy requirements (data handling, consent, retention)
+- Performance requirements (real-time, batch, latency)
+- Availability requirements (uptime, disaster recovery)
+
+### 4. Document Domain Requirements
+
+**Structure the requirements around key concerns:**
+
+```markdown
+### Compliance & Regulatory
+- [Specific requirements]
+
+### Technical Constraints
+- [Security, privacy, performance needs]
+
+### Integration Requirements
+- [Required systems and data flows]
+
+### Risk Mitigations
+- [Domain-specific risks and how to address them]
+```
+
+### 5. Validate Completeness
+
+**Check with the user:**
+
+"Are there other domain-specific concerns we should consider? For [this domain], what typically gets overlooked?"
+
+### N. Present MENU OPTIONS
+
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue - Save and Proceed to Innovation (Step 6 of 13)"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
+- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
+- IF C: Save content to {outputFile}, update frontmatter, 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)
+
+#### EXECUTION RULES:
+- 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
+
+## APPEND TO DOCUMENT
+
+When user selects 'C', append to `{outputFile}`:
+
+```markdown
+## Domain-Specific Requirements
+
+{{discovered domain requirements}}
+```
+
+If step was skipped, append nothing and proceed.
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [content saved or skipped], will you then load and read fully `{nextStepFile}` to explore innovation.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Domain complexity checked before proceeding
+- Offered to skip if complexity is low
+- Natural conversation exploring domain concerns
+- Compliance, technical, and integration requirements identified
+- Domain-specific risks documented with mitigations
+- User validated completeness
+- Content properly saved (or step skipped) when C selected
+
+### ❌ SYSTEM FAILURE:
+
+- Not checking domain complexity first
+- Not offering to skip for low-complexity domains
+- Missing critical compliance requirements
+- Not exploring technical constraints
+- Not asking about domain-specific risks
+- Being generic instead of domain-specific
+- Proceeding without user validation
+
+**Master Rule:** This step is OPTIONAL for simple domains. For complex domains, focus on compliance, constraints, and domain patterns. Natural conversation, not checklists.
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-06-innovation.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-06-innovation.md
@@ -2,17 +2,12 @@
 name: 'step-06-innovation'
 description: 'Detect and explore innovative aspects of the product (optional step)'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-06-innovation.md'
-nextStepFile: '{workflow_path}/steps/step-07-project-type.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-07-project-type.md'
 outputFile: '{planning_artifacts}/prd.md'

 # Data Files
-projectTypesCSV: '{workflow_path}/project-types.csv'
+projectTypesCSV: '../data/project-types.csv'

 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
@@ -40,24 +35,9 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 🎯 Show your analysis before taking any action
 - ⚠️ Present A/P/C menu after generating innovation content
 - 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected

-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper innovation insights
- **P (Party Mode)**: Bring creative perspectives to explore innovation opportunities
- **C (Continue)**: Save the content to the document and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding
-
 ## CONTEXT BOUNDARIES:

 - Current document and frontmatter from previous steps are available
@@ -169,54 +149,47 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Innovation risks and fallbacks based on conversation]
 ```

-### 6. Present Content and Menu (Only if Innovation Detected)
+### 6. Present MENU OPTIONS (Only if Innovation Detected)

-Show the generated innovation content and present choices:
-"I've identified some innovative aspects of {{project_name}} that differentiate it from existing solutions.
+Present the innovation content for review, then display menu:
+
+"Based on our conversation, I've identified innovative aspects of {{project_name}} that differentiate it from existing solutions.

 **Here's what I'll add to the document:**

-[Show the complete markdown content from step 5]
+[Show the complete markdown content from section 5]

-**What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper into these innovation opportunities
-[P] Party Mode - Bring creative perspectives to explore innovation further
-[C] Continue - Save this and move to Project Type Analysis (Step 7 of 11)"
+**What would you like to do?**"

-### 7. Handle Menu Selection
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Project Type Analysis (Step 7 of 11)"

-#### If 'A' (Advanced Elicitation):
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current innovation content, process the enhanced innovation insights that come back, ask user "Accept these improvements to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the current innovation content, process the collaborative innovation exploration and ideation, ask user "Accept these changes to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu

- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current innovation content
- Process the enhanced innovation insights that come back
- Ask user: "Accept these improvements to the innovation analysis? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current innovation content
- Process the collaborative innovation exploration and ideation
- Ask user: "Accept these changes to the innovation analysis? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
- Append the final content to `{outputFile}`
- Update frontmatter: add this step name to the end of the steps completed array
- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`
+#### EXECUTION RULES:
+- 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

 ## NO INNOVATION DETECTED:

 If no genuine innovation signals are found after exploration:
 "After exploring {{project_name}}, I don't see clear innovation signals that warrant a dedicated innovation section. This is perfectly fine - many successful products are excellent executions of existing concepts rather than breakthrough innovations.

-**Options:**
-[A] Force innovation exploration - Let's try to find innovative angles
-[C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)"
+**What would you like to do?**"

-If user selects 'A', proceed with content generation anyway. If 'C', skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.
+Display: "**Select:** [A] Advanced Elicitation - Let's try to find innovative angles [C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)"
+
+#### Menu Handling Logic:
+- IF A: Proceed with content generation anyway, then return to menu
+- IF C: Skip this step, then load, read entire file, then execute {nextStepFile}
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'

 ## APPEND TO DOCUMENT:

--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-07-project-type.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-07-project-type.md
@@ -2,17 +2,12 @@
 name: 'step-07-project-type'
 description: 'Conduct project-type specific discovery using CSV-driven guidance'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-07-project-type.md'
-nextStepFile: '{workflow_path}/steps/step-08-scoping.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-08-scoping.md'
 outputFile: '{planning_artifacts}/prd.md'

 # Data Files
-projectTypesCSV: '{workflow_path}/project-types.csv'
+projectTypesCSV: '../data/project-types.csv'

 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
@@ -40,24 +35,9 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 🎯 Show your analysis before taking any action
 - ⚠️ Present A/P/C menu after generating project-type content
 - 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected

-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper project-type insights
- **P (Party Mode)**: Bring technical perspectives to explore project-specific requirements
- **C (Continue)**: Save the content to the document and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding
-
 ## CONTEXT BOUNDARIES:

 - Current document and frontmatter from previous steps are available
@@ -75,7 +55,7 @@ Conduct project-type specific discovery using CSV-driven guidance to define tech

 Load project-type specific configuration:

- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
+- Load `{projectTypesCSV}` completely
 - Find the row where `project_type` matches detected type from step-02
 - Extract these columns:
  - `key_questions` (semicolon-separated list of discovery questions)
@@ -165,47 +145,34 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Implementation specific requirements based on conversation]
 ```

-### 6. Present Content and Menu
+### 6. Present MENU OPTIONS

-Show the generated project-type content and present choices:
-"I've documented the {project_type}-specific requirements for {{project_name}} based on our conversation and best practices for this type of product.
+Present the project-type content for review, then display menu:
+
+"Based on our conversation and best practices for this product type, I've documented the {project_type}-specific requirements for {{project_name}}.

 **Here's what I'll add to the document:**

-[Show the complete markdown content from step 5]
+[Show the complete markdown content from section 5]

-**What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper into these technical requirements
-[P] Party Mode - Bring technical expertise perspectives to validate requirements
-[C] Continue - Save this and move to Scoping (Step 8 of 11)"
+**What would you like to do?**"

-### 7. Handle Menu Selection
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Scoping (Step 8 of 11)"

-#### If 'A' (Advanced Elicitation):
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current project-type content, process the enhanced technical insights that come back, ask user "Accept these improvements to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the current project-type requirements, process the collaborative technical expertise and validation, ask user "Accept these changes to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu

- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current project-type content
- Process the enhanced technical insights that come back
- Ask user: "Accept these improvements to the technical requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project-type requirements
- Process the collaborative technical expertise and validation
- Ask user: "Accept these changes to the technical requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
- Append the final content to `{outputFile}`
- Update frontmatter: add this step name to the end of the steps completed array
- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md`
+#### EXECUTION RULES:
+- 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

 ## APPEND TO DOCUMENT:

-When user selects 'C', append the content directly to the document using the structure from step 5.
+When user selects 'C', append the content directly to the document using the structure from previous steps.

 ## SUCCESS METRICS:

@@ -253,6 +220,6 @@ When user selects 'C', append the content directly to the document using the str

 ## NEXT STEP:

-After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` to define project scope.
+After user selects 'C' and content is saved to document, load `{nextStepFile}` to define project scope.

 Remember: Do NOT proceed to step-08 (Scoping) until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-08-scoping.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-08-scoping.md
@@ -2,13 +2,8 @@
 name: 'step-08-scoping'
 description: 'Define MVP boundaries and prioritize features across development phases'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-08-scoping.md'
-nextStepFile: '{workflow_path}/steps/step-09-functional.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-09-functional.md'
 outputFile: '{planning_artifacts}/prd.md'

 # Task References
@@ -38,23 +33,9 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 📚 Review the complete PRD document built so far
 - ⚠️ Present A/P/C menu after generating scoping decisions
 - 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected

-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
- **A (Advanced Elicitation)**: Use discovery protocols to explore innovative scoping approaches
- **P (Party Mode)**: Bring multiple perspectives to ensure comprehensive scope decisions
- **C (Continue)**: Save the scoping decisions and proceed to functional requirements
-
-## PROTOCOL INTEGRATION:
-
- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding

 ## CONTEXT BOUNDARIES:

@@ -225,44 +206,30 @@ Prepare comprehensive scoping section:
 **Resource Risks:** {{contingency_approach}}
 ```

-### 7. Present Content and Menu
+### 7. Present MENU OPTIONS

-Show the scoping decisions and present choices:
+Present the scoping decisions for review, then display menu:

-"I've analyzed your complete PRD and created a strategic scoping plan for {{project_name}}.
+"Based on our conversation, I've analyzed your complete PRD and created a strategic scoping plan for {{project_name}}.

 **Here's what I'll add to the document:**

 [Show the complete markdown content from step 6]

-**What would you like to do?**
-[A] Advanced Elicitation - Explore alternative scoping strategies
-[P] Party Mode - Bring different perspectives on MVP and roadmap decisions
-[C] Continue - Save scoping decisions and move to Functional Requirements (Step 9 of 11)"
+**What would you like to do?**"

-### 8. Handle Menu Selection
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Functional Requirements (Step 9 of 11)"

-#### If 'A' (Advanced Elicitation):
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current scoping analysis, process the enhanced insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the scoping context, process the collaborative insights on MVP and roadmap decisions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu

- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current scoping analysis
- Process enhanced scoping insights that come back
- Ask user: "Accept these improvements to the scoping decisions? (y/n)"
- If yes: Update content, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with scoping context
- Process collaborative insights on MVP and roadmap decisions
- Ask user: "Accept these changes to the scoping decisions? (y/n)"
- If yes: Update content, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
- Append the final content to `{outputFile}`
- Update frontmatter: add this step name to the end of the steps completed array
- Load `./step-09-functional.md`
+#### EXECUTION RULES:
+- 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

 ## APPEND TO DOCUMENT:

@@ -294,6 +261,6 @@ When user selects 'C', append the content directly to the document using the str

 ## NEXT STEP:

-After user selects 'C' and content is saved to document, load `./step-09-functional.md`.
+After user selects 'C' and content is saved to document, load {nextStepFile}.

 Remember: Do NOT proceed to step-09 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-09-functional.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-09-functional.md
@@ -2,13 +2,8 @@
 name: 'step-09-functional'
 description: 'Synthesize all discovery into comprehensive functional requirements'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-09-functional.md'
-nextStepFile: '{workflow_path}/steps/step-10-nonfunctional.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-10-nonfunctional.md'
 outputFile: '{planning_artifacts}/prd.md'

 # Task References
@@ -37,23 +32,9 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 🎯 Show your analysis before taking any action
 - ⚠️ Present A/P/C menu after generating functional requirements
 - 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected

-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
- **A (Advanced Elicitation)**: Use discovery protocols to ensure comprehensive requirement coverage
- **P (Party Mode)**: Bring multiple perspectives to validate complete requirement set
- **C (Continue)**: Save the content to the document and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding

 ## CONTEXT BOUNDARIES:

@@ -186,10 +167,11 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Continue for all capability areas discovered in conversation]
 ```

-### 7. Present Content and Menu
+### 7. Present MENU OPTIONS

-Show the generated functional requirements and present choices:
-"I've synthesized all our discussions into comprehensive functional requirements. This becomes the capability contract that UX designers, architects, and developers will all work from.
+Present the functional requirements for review, then display menu:
+
+"Based on our conversation, I've synthesized all our discussions into comprehensive functional requirements. This becomes the capability contract that UX designers, architects, and developers will all work from.

 **Here's what I'll add to the document:**

@@ -201,34 +183,20 @@ Show the generated functional requirements and present choices:
 - UX designers will ONLY design interactions for these capabilities
 - Architects will ONLY build systems to support these capabilities

-**What would you like to do?**
-[A] Advanced Elicitation - Let's ensure we haven't missed any capabilities
-[P] Party Mode - Bring different perspectives to validate complete coverage
-[C] Continue - Save this and move to Non-Functional Requirements (Step 10 of 11)"
+**What would you like to do?**"

-### 8. Handle Menu Selection
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Non-Functional Requirements (Step 10 of 11)"

-#### If 'A' (Advanced Elicitation):
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current FR list, process the enhanced capability coverage that comes back, ask user if they accept the additions, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the current FR list, process the collaborative capability validation and additions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu

- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current FR list
- Process the enhanced capability coverage that comes back
- Ask user: "Accept these additions to the functional requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current FR list
- Process the collaborative capability validation and additions
- Ask user: "Accept these changes to the functional requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
- Append the final content to `{outputFile}`
- Update frontmatter: add this step name to the end of the steps completed array
- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md`
+#### EXECUTION RULES:
+- 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

 ## APPEND TO DOCUMENT:

@@ -265,6 +233,6 @@ Emphasize to user: "This FR list is now binding. Any feature not listed here wil

 ## NEXT STEP:

-After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md` to define non-functional requirements.
+After user selects 'C' and content is saved to document, load {nextStepFile} to define non-functional requirements.

 Remember: Do NOT proceed to step-10 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-10-nonfunctional.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-10-nonfunctional.md
@@ -2,13 +2,8 @@
 name: 'step-10-nonfunctional'
 description: 'Define quality attributes that matter for this specific product'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-10-nonfunctional.md'
-nextStepFile: '{workflow_path}/steps/step-11-complete.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-11-complete.md'
 outputFile: '{planning_artifacts}/prd.md'

 # Task References
@@ -37,23 +32,9 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 🎯 Show your analysis before taking any action
 - ⚠️ Present A/P/C menu after generating NFR content
 - 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected

-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
- **A (Advanced Elicitation)**: Use discovery protocols to ensure comprehensive quality attributes
- **P (Party Mode)**: Bring technical perspectives to validate NFR completeness
- **C (Continue)**: Save the content to the document and proceed to final step
-
-## PROTOCOL INTEGRATION:
-
- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding

 ## CONTEXT BOUNDARIES:

@@ -190,10 +171,11 @@ When saving to document, append these Level 2 and Level 3 sections (only include
 [Integration requirements based on conversation - only include if relevant]
 ```

-### 6. Present Content and Menu
+### 6. Present MENU OPTIONS

-Show the generated NFR content and present choices:
-"I've defined the non-functional requirements that specify how well {{project_name}} needs to perform. I've only included categories that actually matter for this product.
+Present the non-functional requirements for review, then display menu:
+
+"Based on our conversation, I've defined the non-functional requirements that specify how well {{project_name}} needs to perform. I've only included categories that actually matter for this product.

 **Here's what I'll add to the document:**

@@ -201,34 +183,20 @@ Show the generated NFR content and present choices:

 **Note:** We've skipped categories that don't apply to avoid unnecessary requirements.

-**What would you like to do?**
-[A] Advanced Elicitation - Let's ensure we haven't missed critical quality attributes
-[P] Party Mode - Bring technical perspectives to validate NFR specifications
-[C] Continue - Save this and move to Complete PRD (Step 11 of 11)"
+**What would you like to do?**"

-### 7. Handle Menu Selection
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Complete PRD (Step 11 of 11)"

-#### If 'A' (Advanced Elicitation):
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current NFR content, process the enhanced quality attribute insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the current NFR list, process the collaborative technical validation and additions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu

- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current NFR content
- Process the enhanced quality attribute insights that come back
- Ask user: "Accept these improvements to the non-functional requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current NFR list
- Process the collaborative technical validation and additions
- Ask user: "Accept these changes to the non-functional requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
- Append the final content to `{outputFile}`
- Update frontmatter: add this step name to the end of the steps completed array
- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md`
+#### EXECUTION RULES:
+- 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

 ## APPEND TO DOCUMENT:

@@ -289,6 +257,6 @@ When user selects 'C', append the content directly to the document using the str

 ## NEXT STEP:

-After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md` to finalize the PRD and complete the workflow.
+After user selects 'C' and content is saved to document, load {nextStepFile} to finalize the PRD and complete the workflow.

 Remember: Do NOT proceed to step-11 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-11-complete.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps-c/step-11-complete.md
@@ -2,12 +2,7 @@
 name: 'step-11-complete'
 description: 'Complete the PRD workflow, update status files, and suggest next steps'

-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-11-complete.md'
-workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/prd.md'
 ---

--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md
@@ -1,421 +0,0 @@
---
-name: 'step-02-discovery'
-description: 'Conduct project and domain discovery with data-driven classification'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-02-discovery.md'
-nextStepFile: '{workflow_path}/steps/step-03-success.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/prd.md'
-
-# Data Files
-projectTypesCSV: '{workflow_path}/project-types.csv'
-domainComplexityCSV: '{workflow_path}/domain-complexity.csv'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
-
-# Step 2: Project & Domain Discovery
-
-**Progress: Step 2 of 11** - Next: Success Criteria Definition
-
-## STEP GOAL:
-
-Conduct comprehensive project discovery that leverages existing input documents while allowing user refinement, with data-driven classification, and generate the Executive Summary content.
-
-## 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
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
- ✅ You are a product-focused PM facilitator collaborating with an expert peer
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
-
-### Step-Specific Rules:
-
- 🎯 Focus on project classification and vision alignment only
- 🚫 FORBIDDEN to generate content without real user input
- 💬 APPROACH: Adapt questions based on document context (brownfield vs greenfield)
- 🎯 LOAD classification data BEFORE starting discovery conversation
-
-## EXECUTION PROTOCOLS:
-
- 🎯 Show your analysis before taking any action
- ⚠️ Present A/P/C menu after generating executive summary content
- 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
- 🚫 FORBIDDEN to load next step until C is selected
-
-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper insights about the generated content
- **P (Party Mode)**: Bring multiple perspectives to discuss and improve the generated content
- **C (Continue)**: Append and save the content to the `{outputFile}` and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
- When 'A' selected: Execute {advancedElicitationTask}
- When 'P' selected: Execute {partyModeWorkflow}
- PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding
-
-## CONTEXT BOUNDARIES:
-
- Current document and frontmatter from step 1 are available
- Input documents already loaded are in memory (product briefs, research, brainstorming, project docs)
- **Document counts available in frontmatter `documentCounts`**
- Classification CSV data will be loaded in this step only
- This will be the first content section appended to the document
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Read Document State from Frontmatter
-
-**CRITICAL FIRST ACTION:** Read the frontmatter from `{outputFile}` to get document counts.
-
-```
-Read documentCounts from prd.md frontmatter:
- briefCount = documentCounts.briefs
- researchCount = documentCounts.research
- brainstormingCount = documentCounts.brainstorming
- projectDocsCount = documentCounts.projectDocs
-```
-
-**ANNOUNCE your understanding:**
-
-"From step 1, I have loaded:
-
- Product briefs: {{briefCount}} files
- Research: {{researchCount}} files
- Brainstorming: {{brainstormingCount}} files
- Project docs: {{projectDocsCount}} files
-
-{if projectDocsCount > 0}This is a **brownfield project** - I'll focus on understanding what you want to add or change.{else}This is a **greenfield project** - I'll help you define the full product vision.{/if}"
-
-### 2. Load Classification Data
-
-Load and prepare CSV data for intelligent classification:
-
- Load `{projectTypesCSV}` completely
- Load `{domainComplexityCSV}` completely
- Parse column structures and store in memory for this step only
-
-### 3. Begin Discovery Conversation
-
-**SELECT EXACTLY ONE DISCOVERY PATH based on document state:**
-
---
-
-#### PATH A: Has Product Brief (briefCount > 0)
-
-**Use this path when:** `briefCount > 0`
-
-"As your PM peer, I've reviewed your product brief and have a great starting point for our discovery. Let me share what I understand and you can refine or correct as needed.
-
-**Based on your product brief:**
-
-**What you're building:**
-{{extracted_vision_from_brief}}
-
-**Problem it solves:**
-{{extracted_problem_from_brief}}
-
-**Target users:**
-{{extracted_users_from_brief}}
-
-**What makes it special:**
-{{extracted_differentiator_from_brief}}
-
-{if projectDocsCount > 0}I also see you have existing project documentation. This PRD will define how new features integrate with your existing system architecture.{/if}
-
-**How does this align with your vision?** Should we refine any of these points or are there important aspects I'm missing?"
-
-**AFTER this message, SKIP to Section 4.**
-
---
-
-#### PATH B: No Brief but Has Project Docs - Brownfield (briefCount == 0 AND projectDocsCount > 0)
-
-**Use this path when:** `briefCount == 0 AND projectDocsCount > 0`
-
-**NOTE:** Extract the following from loaded project documentation (index.md, architecture.md, project-overview.md, etc.):
-
-"As your PM peer, I've reviewed your existing project documentation from document-project.
-
-**Your existing system includes:**
-
- **Tech Stack:** {analyze index.md and architecture.md for technologies used}
- **Architecture:** {summarize architecture patterns from architecture.md}
- **Key Components:** {list main components from source-tree-analysis.md or project-overview.md}
-
-This PRD will define **new features or changes** to add to this existing codebase.
-
-**Tell me about what you want to add or change:**
-
- What new capability or feature do you want to build?
- What problem will this solve for your users?
- How should it integrate with the existing system?
- Is this adding new functionality, improving existing features, or fixing issues?
-
-I'll help you create a PRD focused on these additions while respecting your existing patterns and architecture."
-
-**AFTER this message, SKIP to Section 4.**
-
---
-
-#### PATH C: No Documents - Greenfield (briefCount == 0 AND projectDocsCount == 0)
-
-**Use this path when:** `briefCount == 0 AND projectDocsCount == 0`
-
-"As your PM peer, I'm excited to help you shape {{project_name}}. Let me start by understanding what you want to build.
-
-**Tell me about what you want to create:**
-
- What problem does it solve?
- Who are you building this for?
- What excites you most about this product?
-
-I'll be listening for signals to help us classify the project and domain so we can ask the right questions throughout our process."
-
-**AFTER this message, continue to Section 4.**
-
---
-
-### 4. Listen for Classification Signals
-
-As the user describes their product/feature, listen for and match against:
-
-#### Project Type Signals
-
-Compare user description against `detection_signals` from `project-types.csv`:
-
- Look for keyword matches from semicolon-separated signals
- Examples: "API,REST,GraphQL" → api_backend
- Examples: "iOS,Android,app,mobile" → mobile_app
- Store the best matching `project_type`
-
-#### Domain Signals
-
-Compare user description against `signals` from `domain-complexity.csv`:
-
- Look for domain keyword matches
- Examples: "medical,diagnostic,clinical" → healthcare
- Examples: "payment,banking,trading" → fintech
- Store the matched `domain` and `complexity_level`
-
-### 5. Present Classification for Validation
-
-**SELECT EXACTLY ONE CLASSIFICATION PRESENTATION based on document state:**
-
---
-
-#### IF PATH A was used (briefCount > 0):
-
-"Based on your product brief and our discussion, I'm classifying this as:
-
- **Project Type:** {project_type_from_brief_or_conversation}
- **Domain:** {domain_from_brief_or_conversation}
- **Complexity:** {complexity_from_brief_or_conversation}
-
-From your brief, I detected these classification signals:
-{{classification_signals_from_brief}}
-
-{if projectDocsCount > 0}Your existing project documentation also indicates:
-
- **Existing Tech Stack:** {from architecture.md or index.md}
- **Architecture Pattern:** {from architecture.md}
-
-I'll ensure the new features align with your existing system.{/if}
-
-Combined with our conversation, this suggests the above classification. Does this sound right?"
-
---
-
-#### IF PATH B was used (briefCount == 0 AND projectDocsCount > 0):
-
-"Based on your existing project documentation and our discussion about new features:
-
- **Existing Project Type:** {detected from project docs - e.g., web_app, api_backend}
- **Tech Stack:** {from architecture.md or index.md}
- **New Feature Type:** {from user's description of what they want to add}
- **Domain:** {detected_domain}
- **Complexity:** {complexity_level}
-
-I'll ensure the PRD aligns with your existing architecture patterns. Does this classification sound right?"
-
---
-
-#### IF PATH C was used (briefCount == 0 AND projectDocsCount == 0):
-
-"Based on our conversation, I'm hearing this as:
-
- **Project Type:** {detected_project_type}
- **Domain:** {detected_domain}
- **Complexity:** {complexity_level}
-
-Does this sound right to you? I want to make sure we're on the same page before diving deeper."
-
---
-
-### 6. Identify What Makes It Special
-
-**SELECT EXACTLY ONE DIFFERENTIATOR DISCOVERY based on document state:**
-
---
-
-#### IF PATH A was used (briefCount > 0):
-
-"From your product brief, I understand that what makes this special is:
-{{extracted_differentiator_from_brief}}
-
-Let's explore this deeper:
-
- **Refinement needed:** Does this capture the essence correctly, or should we adjust it?
- **Missing aspects:** Are there other differentiators that aren't captured in your brief?
- **Evolution:** How has your thinking on this evolved since you wrote the brief?"
-
---
-
-#### IF PATH B was used (briefCount == 0 AND projectDocsCount > 0):
-
-"Your existing system already provides certain capabilities. Now let's define what makes these **new additions** special:
-
- What gap in your current system will this fill?
- How will this improve the experience for your existing users?
- What's the key insight that led you to prioritize this addition?
- What would make users say 'finally, this is what we needed'?"
-
---
-
-#### IF PATH C was used (briefCount == 0 AND projectDocsCount == 0):
-
-Ask focused questions to capture the product's unique value:
-
- "What would make users say 'this is exactly what I needed'?"
- "What's the moment where users realize this is different/better?"
- "What assumption about [problem space] are you challenging?"
- "If this succeeds wildly, what changed for your users?"
-
---
-
-### 7. Generate Executive Summary Content
-
-Based on the conversation, prepare the content to append to the document:
-
-#### Content Structure:
-
-```markdown
-## Executive Summary
-
-{vision_alignment_content}
-
-### What Makes This Special
-
-{product_differentiator_content}
-
-## Project Classification
-
-**Technical Type:** {project_type}
-**Domain:** {domain}
-**Complexity:** {complexity_level}
-{if projectDocsCount > 0}**Project Context:** Brownfield - extending existing system{else}**Project Context:** Greenfield - new project{/if}
-
-{project_classification_content}
-```
-
-### 8. Present Content and Menu
-
-Show the generated content to the user and present:
-
-"I've drafted our Executive Summary based on our conversation. This will be the first section of your PRD.
-
-**Here's what I'll add to the document:**
-
-[Show the complete markdown content from step 7]
-
-**Select an Option:**
-[A] Advanced Elicitation - Let's dive deeper and refine this content
-[P] Party Mode - Bring in different perspectives to improve this
-[C] Continue - Save this and move to Success Criteria Definition (Step 3 of 11)"
-
-### 9. Handle Menu Selection
-
-#### IF A (Advanced Elicitation):
-
- Execute {advancedElicitationTask} with the current content
- Process the enhanced content that comes back
- Ask user: "Accept these changes to the Executive Summary? (y/n)"
- If yes: Update the content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### IF P (Party Mode):
-
- Execute {partyModeWorkflow} with the current content
- Process the collaborative improvements that come back
- Ask user: "Accept these changes to the Executive Summary? (y/n)"
- If yes: Update the content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### IF C (Continue):
-
- Append the final content to `{outputFile}`
- Update frontmatter: add this step name to the end of the steps completed array
- Load `{nextStepFile}`
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [executive summary content finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin success criteria definition.
-
---
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
- Document counts read from frontmatter and announced
- Classification data loaded and used effectively
- **Correct discovery path selected based on document counts**
- Input documents analyzed and leveraged for head start
- User classifications validated and confirmed
- Product differentiator clearly identified and refined
- Executive summary content generated collaboratively with document context
- A/P/C menu presented and handled correctly
- Content properly appended to document when C selected
- Frontmatter updated with stepsCompleted: [1, 2]
-
-### ❌ SYSTEM FAILURE:
-
- **Not reading documentCounts from frontmatter first**
- **Executing multiple discovery paths instead of exactly one**
- Skipping classification data loading and guessing classifications
- Not leveraging existing input documents to accelerate discovery
- Not validating classifications with user before proceeding
- Generating executive summary without real user input
- Missing the "what makes it special" discovery and refinement
- Not presenting A/P/C menu after content generation
- Appending content without user selecting 'C'
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
-
-## COMPLEXITY HANDLING:
-
-If `complexity_level = "high"`:
-
- Note the `suggested_workflow` and `web_searches` from domain CSV
- Consider mentioning domain research needs in classification section
- Document complexity implications in project classification
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md
@@ -1,271 +0,0 @@
---
-name: 'step-05-domain'
-description: 'Explore domain-specific requirements for complex domains (optional step)'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-05-domain.md'
-nextStepFile: '{workflow_path}/steps/step-06-innovation.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/prd.md'
-
-# Data Files
-domainComplexityCSV: '{workflow_path}/domain-complexity.csv'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
-
-# Step 5: Domain-Specific Exploration
-
-**Progress: Step 5 of 11** - Next: Innovation Focus
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
- 🛑 NEVER generate content without user input
-
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
- ✅ ALWAYS treat this as collaborative discovery between PM peers
- 📋 YOU ARE A FACILITATOR, not a content generator
- 💬 FOCUS on domain-specific requirements and compliance needs
- 🎯 OPTIONAL STEP: Only proceed if complexity_level = "high" from step-02
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
- 🎯 Show your analysis before taking any action
- ⚠️ Present A/P/C menu after generating domain content
- 💾 ONLY save when user chooses C (Continue)
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step
- 🚫 FORBIDDEN to load next step until C is selected
-
-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper domain insights
- **P (Party Mode)**: Bring domain expertise perspectives to explore requirements
- **C (Continue)**: Save the content to the document and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding
-
-## CONTEXT BOUNDARIES:
-
- Current document and frontmatter from previous steps are available
- Domain complexity from step-02 should be "high" to justify this step
- Domain-specific CSV data will be loaded in this step
- Focus on compliance, regulations, and domain-specific constraints
-
-## OPTIONAL STEP CHECK:
-
-Before proceeding with this step, verify:
-
- Is `complexity_level` from step-02 equal to "high" and/or does the domain have specific regulatory/compliance needs?
- Would domain exploration significantly impact the product requirements?
-
-If NO to these questions, skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.
-
-## YOUR TASK:
-
-Explore domain-specific requirements for complex domains that need specialized compliance, regulatory, or industry-specific considerations.
-
-## DOMAIN EXPLORATION SEQUENCE:
-
-### 1. Load Domain Configuration Data
-
-Load domain-specific configuration for complex domains:
-
- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv` completely
- Find the row where `domain` matches the detected domain from step-02
- Extract these columns:
-  - `key_concerns` (semicolon-separated list)
-  - `required_knowledge` (domain expertise needed)
-  - `web_searches` (suggested research queries)
-  - `special_sections` (domain-specific sections to document)
-
-### 2. Present Domain Complexity Context
-
-Start by explaining why this step is needed:
-"Since {{project_name}} is in the {domain} domain with high complexity, we need to explore domain-specific requirements.
-
-**Key Concerns for {domain}:**
-[List the key_concerns from CSV]
-
-This step will help us understand regulatory requirements, compliance needs, and industry-specific constraints that will shape our product."
-
-### 3. Explore Domain-Specific Requirements
-
-For each concern in `key_concerns` from the CSV:
-
-#### Domain Concern Exploration:
-
- Ask the user about their approach to this concern
- Discuss implications for the product design and requirements
- Document specific requirements, constraints, and compliance needs
-
-**Example for Healthcare Domain:**
-If key_concerns = "FDA approval;Clinical validation;HIPAA compliance;Patient safety;Medical device classification;Liability"
-
-Ask about each:
-
- "Will this product require FDA approval? What classification?"
- "How will you validate clinical accuracy and safety?"
- "What HIPAA compliance measures are needed?"
- "What patient safety protocols must be in place?"
- "What liability considerations affect the design?"
-
-### 4. Synthesize Domain Requirements
-
-Based on the conversation, synthesize domain requirements that will shape everything:
-
-#### Categories to Document:
-
- **Regulatory requirements** (from key_concerns)
- **Compliance needs** (from key_concerns)
- **Industry standards** (from required_knowledge)
- **Safety/risk factors** (from key_concerns)
- **Required validations** (from key_concerns)
- **Special expertise needed** (from required_knowledge)
-
-Explain how these inform:
-
- What features are mandatory
- What NFRs are critical
- How to sequence development
- What validation is required
-
-### 5. Generate Domain-Specific Content
-
-Prepare the content to append to the document:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Domain-Specific Requirements
-
-### [Domain Name] Compliance & Regulatory Overview
-
-[Domain context summary based on conversation]
-
-### Key Domain Concerns
-
-[Key concerns addressed based on conversation]
-
-### Compliance Requirements
-
-[Compliance requirements based on conversation]
-
-### Industry Standards & Best Practices
-
-[Industry standards based on conversation]
-
-### Required Expertise & Validation
-
-[Required knowledge and validation based on conversation]
-
-### Implementation Considerations
-
-[Implementation implications based on conversation]
-```
-
-### 6. Handle Special Sections
-
-Parse `special_sections` list from the matched CSV row. For each section name, generate corresponding subsections:
-
-**Example mappings from CSV:**
-
- "clinical_requirements" → Add clinical validation requirements
- "regulatory_pathway" → Document approval pathway timeline
- "safety_measures" → Specify safety protocols and monitoring
- "compliance_matrix" → Create compliance tracking matrix
-
-### 7. Present Content and Menu
-
-Show the generated domain content and present choices:
-"I've documented the {domain}-specific requirements that will shape {{project_name}}. These constraints are critical for success in this complex domain.
-
-**Here's what I'll add to the document:**
-
-[Show the complete markdown content from step 6]
-
-**What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper into these domain requirements
-[P] Party Mode - Bring domain expertise perspectives to validate requirements
-[C] Continue - Save this and move to Innovation Focus (Step 6 of 11)"
-
-### 8. Handle Menu Selection
-
-#### If 'A' (Advanced Elicitation):
-
- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current domain content
- Process the enhanced domain insights that come back
- Ask user: "Accept these domain requirement improvements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current domain requirements
- Process the collaborative domain expertise and validation
- Ask user: "Accept these changes to domain requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu
- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
- Append the content to `{outputFile}`
- Update frontmatter: add this step name to the end of the steps completed array
- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C', append the content directly to the document using the structure from step 6.
-
-## SUCCESS METRICS:
-
-✅ Domain complexity properly validated as high before proceeding
-✅ All key concerns from CSV explored with user input
-✅ Compliance requirements clearly documented
-✅ Domain expertise needs identified and documented
-✅ Special sections generated per CSV configuration
-✅ A/P/C menu presented and handled correctly
-✅ Content properly appended to document when C selected
-
-## FAILURE MODES:
-
-❌ Proceeding with domain exploration when complexity is not high
-❌ Not loading or using CSV domain configuration properly
-❌ Missing critical domain concerns from the key_concerns list
-❌ Not connecting domain requirements to product implications
-❌ Generating generic content without domain-specific details
-❌ Not presenting A/P/C menu after content generation
-❌ Appending content without user selecting 'C'
-
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## SKIP CONDITIONS:
-
-Skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md` if:
-
- `complexity_level` from step-02 is not "high"
- Domain has no specific regulatory/compliance requirements
- User confirms domain exploration is not needed
-
-## NEXT STEP:
-
-After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.
-
-Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/templates/prd-template.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/templates/prd-template.md
@@ -2,7 +2,6 @@
 stepsCompleted: []
 inputDocuments: []
 workflowType: 'prd'
-lastStep: 0
 ---

 # Product Requirements Document - {{project_name}}
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/validation-report-prd.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/validation-report-prd.md
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.md
@@ -2,6 +2,7 @@
 name: create-prd
 description: Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.
 main_config: '{project-root}/_bmad/bmm/config.yaml'
+nextStep: './steps-c/step-01-init.md'
 web_bundle: true
 ---

@@ -59,5 +60,5 @@ Load and read full config from {main_config} and resolve:
 ### 2. First Step EXECUTION


-YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`.
-Load, read the full file and then execute `steps/step-01-init.md` to begin the workflow.
+YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+Load, read the full file and then execute `{nextStep}` to begin the workflow.
--- a/Show More
+++ b/Show More