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/bmm/workflows -name "*complete*" -o -name "*final*" | sort
find /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows -name "*complete*" -o -name "*final*" | xargs grep -l "help\.md" 2>/dev/null

Find all completion steps and which ones reference 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).


sort: invalid option -- a
Usage: sort [-bcCdfigMmnrsuz] [-kPOS1[,POS2] ... ] [+POS1 [-POS2]] [-S memsize] [-T tmpdir] [-t separator] [-o outfile] [--batch-size size] [--files0-from file] [--heapsort] [--mergesort] [--radixsort] [--qsort] [--mmap] [--parallel thread_no] [--human-numeric-sort] [--version-sort] [--random-sort [--random-source file]] [--compress-program program] [file ...]

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).


find /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows -name "*complete*" -o -name "*final*"

Find all completion and final step files

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).


# step-e-04-complete.md does NOT chain to help.md - is this an oversight?
# step-03-complete (generate-project-context) does NOT chain to help.md - is this an oversight?
# These are completion steps that the diff didn't touch

# Now check: do the research workflows (market/domain/technical) have completion steps at all?
find /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/1-analysis/research -name "*.md"

Check research workflow step files

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).


grep -n "help\.md\|with argument" /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md
grep -n "help\.md\|with argument" /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md
grep -n "help\.md\|with argument" /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md

Check research completion steps for help.md references

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).


# Also check sprint planning and retrospective completion steps
find /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/4-implementation -name "*.md" -o -name "*.yaml" | xargs grep -l "help\.md" 2>/dev/null

# Check quick-spec and quick-dev completion steps
find /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/bmad-quick-flow -name "*complete*" -o -name "*final*"

Check implementation workflows for help.md references

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).


# Step-06-complete (product brief) references "### 3. Suggest Next Steps" AND "### 5. Suggest next steps"
# The header at step 3 explicitly suggests next steps (with workflow names), THEN step 5 is the help.md chain
# This means help.md is being called AFTER the step file already provides next step guidance
# This is potentially redundant or could cause conflicting guidance

# Also: in step-12-complete (PRD), the ordering is:
# 1. Announce, 2. Status Update, 3. Validation Options, 4. Suggest Next Workflows (help.md), 5. Final Completion
# The help.md chain is BEFORE the "Final Completion Confirmation" - meaning it fires mid-sequence
# After help.md returns (step 8: "Return to calling process"), does step 5 still execute?

grep -n "Return to the calling process\|calling process" /Users/alex/src/bmad/quick-flow-redesign/src/core/tasks/help.md

Check how help.md returns control and implications for sequence ordering

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).


86:8. Return to the calling process after presenting recommendations.

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).


# Check step-12-complete specifically: help.md is called in step 4 "Suggest Next Workflows"
# then step 5 "Final Completion Confirmation" asks user to acknowledge and choose
# After help.md returns, the calling step file continues to step 5
# But step-08-complete (architecture) has help.md in step 3 followed by "offer to answer any questions"
# which is just a sentence, not a numbered step

grep -n "### [0-9]\|help\.md\|offer to answer" /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md

Check architecture completion step sequencing around help.md call

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).


28:### 1. Congratulate the User on Completion
32:### 2. Update the created document's frontmatter
42:### 3. Next Steps Guidance
44:Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
46:Upon Completion of task output: offer to answer any questions about the Architecture Document.

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).


# Now check the create-prd step-12 which has help.md in step 4 BEFORE step 5 "Final Completion Confirmation"
# After help.md executes and returns, the agent is supposed to continue to step 5
# But step 5 says "Ask if they'd like to run validation workflow or proceed" - this is now AFTER help.md already showed next steps
# This creates a confusing double-prompt for next steps

grep -n "90\|88\|89\|91\|92\|93\|94\|95" /dev/null
sed -n '85,100p' /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md

Read PRD step-12 around the help.md call to see sequencing issue

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).


- Validation can be done later if needed
- Some teams prefer to validate during architecture reviews

### 4. Suggest Next Workflows

PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`

### 5. Final Completion Confirmation

- Confirm completion with user and summarize what has been accomplished
- Document now contains: Executive Summary, Success Criteria, User Journeys, Domain Requirements (if applicable), Innovation Analysis (if applicable), Project-Type Requirements, Functional Requirements (capability contract), Non-Functional Requirements, and has been polished for flow and coherence
- Ask if they'd like to run validation workflow or proceed to next workflows

## SUCCESS METRICS:

✅ PRD document contains all required sections and has been polished

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).


# Check the "implementation readiness" argument - it was lowercase while CSV has "Check Implementation Readiness"
# This inconsistency is pre-existing but worth noting since the removal affects all of them

# Now check if help.md has ANY mechanism to accept or process an argument at all
# The diff claim is "removing `with argument`" - but does help.md's EXECUTION step reference any argument input?
grep -n "argument\|parameter\|input\|caller\|invoke" /Users/alex/src/bmad/quick-flow-redesign/src/core/tasks/help.md

Check if help.md has any argument processing mechanism

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).


27:- Then invokes by referencing the `code` field or describing the `name` field
64:5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.

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).