     1→---
     2→name: help
     3→description: Get unstuck by showing what workflow steps come next or answering questions about what to do
     4→---
     5→
     6→# Task: BMAD Help
     7→
     8→## ROUTING RULES
     9→
    10→- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
    11→- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order (naming varies by module)
    12→- **Phase with no Required Steps** - If an entire phase has no required, true items, the entire phase is optional. If it is sequentially before another phase, it can be recommended, but always be clear with the use what the true next required item is.
    13→- **Stay in module** — Guide through the active module's workflow based on phase+sequence ordering
    14→- **Descriptions contain routing** — Read for alternate paths (e.g., "back to previous if fixes needed")
    15→- **`required=true` blocks progress** — Required workflows must complete before proceeding to later phases
    16→- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns, fuzzy-match found files to workflow rows
    17→
    18→## DISPLAY RULES
    19→
    20→### Command-Based Workflows
    21→When `command` field has a value:
    22→- Show the command prefixed with `/` (e.g., `/bmad-bmm-create-prd`)
    23→
    24→### Agent-Based Workflows
    25→When `command` field is empty:
    26→- User loads agent first via `/agent-command`
    27→- Then invokes by referencing the `code` field or describing the `name` field
    28→- Do NOT show a slash command — show the code value and agent load instruction instead
    29→
    30→Example presentation for empty command:
    31→```
    32→Explain Concept (EC)
    33→Load: /tech-writer, then ask to "EC about [topic]"
    34→Agent: Tech Writer
    35→Description: Create clear technical explanations with examples...
    36→```
    37→
    38→## MODULE DETECTION
    39→
    40→- **Empty `module` column** → universal tools (work across all modules)
    41→- **Named `module`** → module-specific workflows
    42→
    43→Detect the active module from conversation context, recent workflows, or user query keywords. If ambiguous, ask the user.
    44→
    45→## INPUT ANALYSIS
    46→
    47→Determine what was just completed:
    48→- Explicit completion stated by user
    49→- Workflow completed in current conversation
    50→- Artifacts found matching `outputs` patterns
    51→- If `index.md` exists, read it for additional context
    52→- If still unclear, ask: "What workflow did you most recently complete?"
    53→
    54→## EXECUTION
    55→
    56→1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
    57→
    58→2. **Resolve output locations and config** — Scan each folder under `{project-root}/_bmad/` (except `_config`) for `config.yaml`. For each workflow row, resolve its `output-location` variables against that module's config so artifact paths can be searched. Also extract `communication_language` and `project_knowledge` from each scanned module's config.
    59→
    60→3. **Ground in project knowledge** — If `project_knowledge` resolves to an existing path, read available documentation files (architecture docs, project overview, tech stack references) for grounding context. Use discovered project facts when composing any project-specific output. Never fabricate project-specific details — if documentation is unavailable, state so.
    61→
    62→4. **Detect active module** — Use MODULE DETECTION above
    63→
    64→5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
    65→
    66→6. **Present recommendations** — Show next steps based on:
    67→   - Completed workflows detected
    68→   - Phase/sequence ordering (ROUTING RULES)
    69→   - Artifact presence
    70→
    71→   **Optional items first** — List optional workflows until a required step is reached
    72→   **Required items next** — List the next required workflow
    73→
    74→   For each item, apply DISPLAY RULES above and include:
    75→   - Workflow **name**
    76→   - **Command** OR **Code + Agent load instruction** (per DISPLAY RULES)
    77→   - **Agent** title and display name from the CSV (e.g., "🎨 Alex (Designer)")
    78→   - Brief **description**
    79→
    80→7. **Additional guidance to convey**:
    81→   - Present all output in `{communication_language}`
    82→   - Run each workflow in a **fresh context window**
    83→   - For **validation workflows**: recommend using a different high-quality LLM if available
    84→   - For conversational requests: match the user's tone while presenting clearly
    85→
    86→8. Return to the calling process after presenting recommendations.
    87→

Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


No matches found

Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


No files found

Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


src/core/module-help.csv:4:core,anytime,bmad-help,BH,,_bmad/core/tasks/help.md,bmad-help,false,,,"Get unstuck by showing what workflow steps come next or answering BMad Method questions.",,
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md:200:  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md:90:PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md:112:Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md:131:Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md:85:UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md:147:Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md:44:Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


Bash

find /Users/alex/src/bmad/quick-flow-redesign/src -name "*.csv" | xargs grep -l "create-product-brief\|create-prd\|create-ux\|create-architecture\|create-epics\|check-implementation" 2>/dev/null

Find CSV files referencing the affected workflows

Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


     1→module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
     2→bmm,anytime,Document Project,DP,,_bmad/bmm/workflows/document-project/workflow.yaml,bmad-bmm-document-project,false,analyst,Create Mode,"Analyze an existing project to produce useful documentation",project-knowledge,*,
     3→bmm,anytime,Generate Project Context,GPC,,_bmad/bmm/workflows/generate-project-context/workflow.md,bmad-bmm-generate-project-context,false,analyst,Create Mode,"Scan existing codebase to generate a lean LLM-optimized project-context.md containing critical implementation rules patterns and conventions for AI agents. Essential for brownfield projects and quick-flow.",output_folder,"project context",
     4→bmm,anytime,Quick Spec,QS,,_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md,bmad-bmm-quick-spec,false,quick-flow-solo-dev,Create Mode,"Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method. Quick one-off tasks small changes simple apps brownfield additions to well established patterns utilities without extensive planning",planning_artifacts,"tech spec",
     5→bmm,anytime,Quick Dev,QD,,_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md,bmad-bmm-quick-dev,false,quick-flow-solo-dev,Create Mode,"Quick one-off tasks small changes simple apps utilities without extensive planning - Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method, unless the user is already working through the implementation phase and just requests a 1 off things not already in the plan",,,
     6→bmm,anytime,Quick Dev 2,QD2,,_bmad/bmm/workflows/bmad-quick-flow/quick-dev2/workflow.md,bmad-bmm-quick-dev2,false,quick-flow-solo-dev,Create Mode,"Unified quick flow (experimental): clarify intent plan implement review and present in a single workflow",implementation_artifacts,"tech spec implementation",
     7→bmm,anytime,Correct Course,CC,,_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml,bmad-bmm-correct-course,false,sm,Create Mode,"Anytime: Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories",planning_artifacts,"change proposal",
     8→bmm,anytime,Write Document,WD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Describe in detail what you want, and the agent will follow the documentation best practices defined in agent memory. Multi-turn conversation with subprocess for research/review.",project-knowledge,"document",
     9→bmm,anytime,Update Standards,US,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Update agent memory documentation-standards.md with your specific preferences if you discover missing document conventions.",_bmad/_memory/tech-writer-sidecar,"standards",
    10→bmm,anytime,Mermaid Generate,MG,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Create a Mermaid diagram based on user description. Will suggest diagram types if not specified.",planning_artifacts,"mermaid diagram",
    11→bmm,anytime,Validate Document,VD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Review the specified document against documentation standards and best practices. Returns specific actionable improvement suggestions organized by priority.",planning_artifacts,"validation report",
    12→bmm,anytime,Explain Concept,EC,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Create clear technical explanations with examples and diagrams for complex concepts. Breaks down into digestible sections using task-oriented approach.",project_knowledge,"explanation",
    13→bmm,1-analysis,Brainstorm Project,BP,10,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,data=_bmad/bmm/data/project-context-template.md,"Expert Guided Facilitation through a single or multiple techniques",planning_artifacts,"brainstorming session",
    14→bmm,1-analysis,Market Research,MR,20,_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md,bmad-bmm-market-research,false,analyst,Create Mode,"Market analysis competitive landscape customer needs and trends","planning_artifacts|project-knowledge","research documents",
    15→bmm,1-analysis,Domain Research,DR,21,_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md,bmad-bmm-domain-research,false,analyst,Create Mode,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project_knowledge","research documents",
    16→bmm,1-analysis,Technical Research,TR,22,_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md,bmad-bmm-technical-research,false,analyst,Create Mode,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project_knowledge","research documents",
    17→bmm,1-analysis,Create Brief,CB,30,_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md,bmad-bmm-create-product-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
    18→bmm,2-planning,Create PRD,CP,10,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
    19→bmm,2-planning,Validate PRD,VP,20,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md,bmad-bmm-validate-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report",
    20→bmm,2-planning,Edit PRD,EP,25,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md,bmad-bmm-edit-prd,false,pm,Edit Mode,"Improve and enhance an existing PRD",planning_artifacts,"updated prd",
    21→bmm,2-planning,Create UX,CU,30,_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md,bmad-bmm-create-ux-design,false,ux-designer,Create Mode,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project",planning_artifacts,"ux design",
    22→bmm,3-solutioning,Create Architecture,CA,10,_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md,bmad-bmm-create-architecture,true,architect,Create Mode,"Guided Workflow to document technical decisions",planning_artifacts,architecture,
    23→bmm,3-solutioning,Create Epics and Stories,CE,30,_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md,bmad-bmm-create-epics-and-stories,true,pm,Create Mode,"Create the Epics and Stories Listing",planning_artifacts,"epics and stories",
    24→bmm,3-solutioning,Check Implementation Readiness,IR,70,_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md,bmad-bmm-check-implementation-readiness,true,architect,Validate Mode,"Ensure PRD UX Architecture and Epics Stories are aligned",planning_artifacts,"readiness report",
    25→bmm,4-implementation,Sprint Planning,SP,10,_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml,bmad-bmm-sprint-planning,true,sm,Create Mode,"Generate sprint plan for development tasks - this kicks off the implementation phase by producing a plan the implementation agents will follow in sequence for every story in the plan.",implementation_artifacts,"sprint status",
    26→bmm,4-implementation,Sprint Status,SS,20,_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml,bmad-bmm-sprint-status,false,sm,Create Mode,"Anytime: Summarize sprint status and route to next workflow",,,
    27→bmm,4-implementation,Validate Story,VS,35,_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml,bmad-bmm-create-story,false,sm,Validate Mode,"Validates story readiness and completeness before development work begins",implementation_artifacts,"story validation report",
    28→bmm,4-implementation,Create Story,CS,30,_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml,bmad-bmm-create-story,true,sm,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story,
    29→bmm,4-implementation,Dev Story,DS,40,_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml,bmad-bmm-dev-story,true,dev,Create Mode,"Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed",,,
    30→bmm,4-implementation,Code Review,CR,50,_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml,bmad-bmm-code-review,false,dev,Create Mode,"Story cycle: If issues back to DS if approved then next CS or ER if epic complete",,,
    31→bmm,4-implementation,QA Automation Test,QA,45,_bmad/bmm/workflows/qa/automate/workflow.yaml,bmad-bmm-qa-automate,false,qa,Create Mode,"Generate automated API and E2E tests for implemented code using the project's existing test framework (detects existing well known in use test frameworks). Use after implementation to add test coverage. NOT for code review or story validation - use CR for that.",implementation_artifacts,"test suite",
    32→bmm,4-implementation,Retrospective,ER,60,_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml,bmad-bmm-retrospective,false,sm,Create Mode,"Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC",implementation_artifacts,retrospective,
    33→

Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


grep -rn "Validate PRD\|Create PRD\|Create Architecture\|Create UX\|implementation readiness\|Create Epics\|Product Brief" /Users/alex/src/bmad/quick-flow-redesign/src/bmm/module-help.csv | head -20

Check CSV codes for affected workflows

Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


/Users/alex/src/bmad/quick-flow-redesign/src/bmm/module-help.csv:18:bmm,2-planning,Create PRD,CP,10,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
/Users/alex/src/bmad/quick-flow-redesign/src/bmm/module-help.csv:19:bmm,2-planning,Validate PRD,VP,20,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md,bmad-bmm-validate-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report",
/Users/alex/src/bmad/quick-flow-redesign/src/bmm/module-help.csv:21:bmm,2-planning,Create UX,CU,30,_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md,bmad-bmm-create-ux-design,false,ux-designer,Create Mode,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project",planning_artifacts,"ux design",
/Users/alex/src/bmad/quick-flow-redesign/src/bmm/module-help.csv:22:bmm,3-solutioning,Create Architecture,CA,10,_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md,bmad-bmm-create-architecture,true,architect,Create Mode,"Guided Workflow to document technical decisions",planning_artifacts,architecture,
/Users/alex/src/bmad/quick-flow-redesign/src/bmm/module-help.csv:23:bmm,3-solutioning,Create Epics and Stories,CE,30,_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md,bmad-bmm-create-epics-and-stories,true,pm,Create Mode,"Create the Epics and Stories Listing",planning_artifacts,"epics and stories",

Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).


grep -rn "with argument\|argument" /Users/alex/src/bmad/quick-flow-redesign/src --include="*.md" | grep -v "_experiment" | head -30

Check for any remaining "with argument" references anywhere in src

Prompt:
You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone.

You have ZERO conversation context. You only have the diff and the source files. Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve.

## The Diff

7 markdown workflow completion step files are being modified. In each file, the same pattern is applied: removing ` with argument \`[workflow name]\`` from a line that chains to `help.md`.

```diff
diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
-PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create PRD`.
+PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
-  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.
+  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
-UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.
+UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
-Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
-Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## The help.md file that is being chained to

```markdown
# Task: BMAD Help

## ROUTING RULES
- **Empty `phase` = anytime** — Universal tools work regardless of workflow state
- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order
- **Phase with no Required Steps** - entire phase is optional
- **Stay in module** — Guide through the active module's workflow
- **Descriptions contain routing** — Read for alternate paths
- **`required=true` blocks progress** — Required workflows must complete before proceeding
- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns

## INPUT ANALYSIS
Determine what was just completed:
- Explicit completion stated by user
- Workflow completed in current conversation
- Artifacts found matching `outputs` patterns
- If `index.md` exists, read it for additional context
- If still unclear, ask: "What workflow did you most recently complete?"

## EXECUTION
1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
2. **Resolve output locations and config**
3. **Ground in project knowledge**
4. **Detect active module**
5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
6. **Present recommendations**
7. **Additional guidance**
8. Return to the calling process after presenting recommendations.
```

## Also consider
- Whether the "with argument" was serving a purpose that the remaining text doesn't cover
- Whether help.md can reliably infer the completed workflow from just the "[Workflow] complete." prefix text
- Whether there are any other files in the codebase that might reference these arguments
- Whether the change is consistent across all 7 files

Output your findings as a Markdown list (descriptions only).