I don't really believe that. I may be wrong, but I'd like to see where in Git history these with argument x were added, and what does the commit say about the reasoning for that, if anything.


Bash

git -C /Users/alex/src/bmad/quick-flow-redesign log --all --oneline --follow -p -S "with argument" -- "src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md" | head -80

Find commits that introduced "with argument" in one of the 7 files


37346079 workflow drastic simplification and more reliable
diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
index fd73cb87..43ed4ce6 100644
--- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
+++ b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
@@ -5,7 +5,6 @@
 - 🛑 NEVER generate content without user input

 - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS treat this as collaborative completion between architectural peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on successful workflow completion and implementation handoff
@@ -18,14 +17,7 @@
 - 🎯 Show your analysis before taking any action
 - 🎯 Present completion summary and implementation guidance
 - 📖 Update frontmatter with final workflow state
-- 🚫 NO MORE STEPS - this is the final step
-
-## CONTEXT BOUNDARIES:
-
-- Complete architecture document is finished and validated
-- All architectural decisions, patterns, and structure are documented
-- Focus on successful completion and implementation preparation
-- Provide clear guidance for next steps in the development process
+- 🚫 THIS IS THE FINAL STEP IN THIS WORKFLOW

 ## YOUR TASK:

@@ -33,75 +25,11 @@ Complete the architecture workflow, provide a comprehensive completion summary,

 ## COMPLETION SEQUENCE:

-### 1. Present Architecture Completion Summary
-
-Based on user skill level, present the completion:
-
-**For Expert Users:**
-"Architecture workflow complete. {{decision_count}} architectural decisions documented across {{step_count}} steps.
-
-Your architecture is ready for AI agent implementation. All decisions are documented with specific versions and implementation patterns.
-
-Key deliverables:
-
-- Complete architecture decision document
-- Implementation patterns for agent consistency
-- Project structure with all files and directories
-- Validation confirming coherence and completeness
-
-Ready for implementation phase."
-
-**For Intermediate Users:**
-"Excellent! Your architecture for {{project_name}} is now complete and ready for implementation.
-
-**What we accomplished:**
-
-- Made {{decision_count}} key architectural decisions together
-- Established implementation patterns to ensure consistency
-- Created a complete project structure with {{component_count}} main areas
-- Validated that all your requirements are fully supported
-
-**Your architecture document includes:**
-
-- Technology choices with specific versions
-- Clear implementation patterns for AI agents to follow
-- Complete project directory structure
-- Mapping of your requirements to specific files and folders
-
-The architecture is comprehensive and ready to guide consistent implementation."
-
-**For Beginner Users:**
-"Congratulations! Your architecture for {{project_name}} is complete! 🎉
-
-**What this means:**
-Think of this as creating the complete blueprint for your house. We've made all the important decisions about how it will be built, what materials to use, and how everything fits together.
-
-**What we created together:**
-
-- {{decision_count}} architectural decisions (like choosing the foundation, framing, and systems)
-- Clear rules so that multiple builders (AI agents) all work the same way


git -C /Users/alex/src/bmad/quick-flow-redesign log --all --oneline -p -S "with argument" -- "src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md" | tail -40

See the rest of the diff showing with argument introduction


-
-{if_existing_project_context}
-I noticed you already have a project context file. Would you like to update it with your new architectural decisions?
-{else}
-This file helps ensure AI agents implement code consistently with your project's unique requirements and patterns.
-{/if_existing_project_context}
-
-**Create/Update project context?** [Y/N]
-
-**Ready to move to the next phase of your project development?**"
-
-### 7. Handle Project Context Creation Choice
-
-If user responds 'Y' or 'yes' to creating/updating project context:
-
-"Excellent choice! Let me launch the Generate Project Context workflow to create a comprehensive guide for AI agents.
-
-This will help ensure consistent implementation by capturing:
-
-- Language-specific patterns and rules
-- Framework conventions from your architecture
-- Testing and quality standards
-- Anti-patterns to avoid
-
-The workflow will collaborate with you to create an optimized `project-context.md` file that AI agents will read before implementing any code."
+### 3. Next Steps Guidance

-**Execute the Generate Project Context workflow:**
+Execute task `_bmad/bmm/tasks/whats-after.md` with argument `Create Architecture`.

-- Load and execute: `{project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md`
-- The workflow will handle discovery, generation, and completion of the project context file
-- After completion, return here for final handoff
+Upon Completion of task output: offer to answer any questions about the Architecture Document.

-If user responds 'N' or 'no':
-"Understood! Your architecture is complete and ready for implementation. You can always create a project context file later using the Generate Project Context workflow if needed."

 ## SUCCESS METRICS:


Interesting! The original line was:

```
Execute task `_bmad/bmm/tasks/whats-after.md` with argument `Create Architecture`.
```

Not `help.md` — it was originally `whats-after.md`! Then it got changed to `help.md`. Let me find the full commit history.


Interesting — the original text was `Execute task _bmad/bmm/tasks/whats-after.md with argument ...`, not `help.md`. Let me dig deeper.


git -C /Users/alex/src/bmad/quick-flow-redesign log --all --oneline --follow -S "with argument" -- "src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md"

List all commits touching "with argument" in this file


37346079 workflow drastic simplification and more reliable


git -C /Users/alex/src/bmad/quick-flow-redesign show 37346079 --stat | head -30

Show commit stats


commit 3734607994ec9daf8a4d41dd5ee284273bb74ad1
Author: Brian Madison <brianmadison@Brians-MacBook-Pro.local>
Date:   Tue Jan 20 01:12:20 2026 -0600

    workflow drastic simplification and more reliable

 src/bmm/agents/analyst.agent.yaml                  |   7 +-
 src/bmm/agents/architect.agent.yaml                |   1 -
 src/bmm/agents/pm.agent.yaml                       |   5 +-
 src/bmm/agents/sm.agent.yaml                       |  11 +-
 src/bmm/agents/tea.agent.yaml                      |   1 -
 src/bmm/agents/ux-designer.agent.yaml              |   4 +-
 src/bmm/data/README.md                             |  29 --
 src/bmm/data/paths/enterprise-brownfield.yaml      | 103 -------
 src/bmm/data/paths/enterprise-greenfield.yaml      | 100 -------
 src/bmm/data/paths/method-brownfield.yaml          | 103 -------
 src/bmm/data/paths/method-greenfield.yaml          | 100 -------
 src/bmm/data/project-context-template.md           |  16 +-
 src/bmm/data/workflows.csv                         |  18 ++
 src/bmm/tasks/whats-after.md                       |  44 +++
 .../create-product-brief/steps/step-06-complete.md |  32 +--
 .../create-ux-design/steps/step-14-complete.md     |  61 +---
 .../prd/steps-c/step-12-complete.md                |  58 +---
 .../prd/steps-v/step-v-13-report-complete.md       |   5 +-
 .../steps/step-06-final-assessment.md              |   2 +
 .../steps/step-07-validation.md                    |   2 +-
 .../create-architecture/steps/step-08-complete.md  | 290 +------------------
 .../steps/step-04-final-validation.md              |   4 +
 .../project-context-template.md                    |  21 --
 .../steps/step-01-discover.md                      | 184 ------------


git -C /Users/alex/src/bmad/quick-flow-redesign log --all --oneline -S "with argument" -- "src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md"

Find commits for file #1


git -C /Users/alex/src/bmad/quick-flow-redesign log --all --oneline -S "whats-after" | head -10

Find commits referencing whats-after task


ec8ab0c6 workflow tracking evolved to bmad-help
aae7923d standardize installer flat command list with naming convention standardization to make workflow update
37346079 workflow drastic simplification and more reliable


git -C /Users/alex/src/bmad/quick-flow-redesign show 37346079 -- src/bmm/tasks/whats-after.md

Show the original whats-after.md task that was created


commit 3734607994ec9daf8a4d41dd5ee284273bb74ad1
Author: Brian Madison <brianmadison@Brians-MacBook-Pro.local>
Date:   Tue Jan 20 01:12:20 2026 -0600

    workflow drastic simplification and more reliable

diff --git a/src/bmm/tasks/whats-after.md b/src/bmm/tasks/whats-after.md
new file mode 100644
index 00000000..ec18704e
--- /dev/null
+++ b/src/bmm/tasks/whats-after.md
@@ -0,0 +1,44 @@
+---
+name: whats-next
+description: Show what workflow steps come next in the BMad Method based on what's been completed
+---
+
+# Task: What's Next?
+
+## INPUT
+
+Task input argument may provide:
+- A workflow **name** just completed (e.g., "validating the UX", "Create PRD", "done with architecture")
+- A workflow **code** (e.g., "VU", "CP", "CA")
+- Nothing - in which case you should infer from context or ask
+
+## CONTEXT INFERENCE
+
+If no explicit workflow is provided, check the conversation context:
+- Did someone recently state they completed something? (e.g., "I'm done with my PRD")
+- Was a workflow just completed in this conversation?
+- If unclear, ask: "What workflow did you most recently complete?"
+
+## EXECUTION
+
+Load `{project-root}/_bmad/bmm/data/workflows.csv` and `{project-root}/_bmad/_config/agent-manifest.csv`. Find all workflow items after the completed row. Present these in a clear, conversational format.
+
+**Phases reference:** Phase 0 (Any Time), Phase 1 (Analysis), Phase 2 (Planning), Phase 3 (Solutioning), Phase 4 (Implementation)
+
+**Present the next steps as follows:**
+
+1. **Optional items first** - List any optional workflows until a required step is reached
+2. **Required items next** - List the next required workflow
+3. For each item, show:
+   - The workflow **name**
+   - The **command** (prefixed with `/`, e.g., `/bmm:create-architecture`)
+   - The **agent** displayName and title from the loaded agent-manifest that corresponds with the agent value in each row who can help, e.g., `Winston the Architect`
+   - A brief **description** so the user can decide easily
+
+**Recommendation format:**
+- Suggest running each workflow in a **fresh context window** for best results
+- Option: Load the agent and type the **code** for the menu item, or run the **slash command** with or without loading the agent first
+  - Note: Running without the agent will not include all specifics of the agent personality or any customizations, but will still have aspects of an expert at what will be done.
+- For **validation workflows**: recommend using a different high-quality LLM if available
+
+Upon presentation of whats next recommendation - return back to the calling process if one was in progress.


git -C /Users/alex/src/bmad/quick-flow-redesign show ec8ab0c6 --stat | head -20

Show the commit that evolved whats-after to bmad-help


commit ec8ab0c63871e652cae1b9b1da42d0f798f5f046
Author: Brian Madison <brianmadison@Brians-MacBook-Pro.local>
Date:   Wed Jan 21 14:05:57 2026 -0600

    workflow tracking evolved to bmad-help

 src/bmm/tasks/{whats-after.md => bmad-help.md}     | 31 +++++++++------
 src/bmm/tasks/workflows.csv                        | 44 +++++++++++++---------
 .../create-product-brief/steps/step-06-complete.md |  2 +-
 .../create-ux-design/steps/step-14-complete.md     |  2 +-
 .../prd/steps-c/step-12-complete.md                |  2 +-
 .../prd/steps-v/step-v-13-report-complete.md       |  2 +-
 .../steps/step-06-final-assessment.md              |  2 +-
 .../create-architecture/steps/step-08-complete.md  |  2 +-
 .../steps/step-04-final-validation.md              |  2 +-
 .../cli/installers/lib/ide/STANDARDIZATION_PLAN.md |  4 +-
 .../lib/ide/shared/task-tool-command-generator.js  |  8 ++--
 11 files changed, 59 insertions(+), 42 deletions(-)


git -C /Users/alex/src/bmad/quick-flow-redesign log ec8ab0c6 --format="%B" -1

Show full commit message


workflow tracking evolved to bmad-help


git -C /Users/alex/src/bmad/quick-flow-redesign show ec8ab0c6 -- "src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md"

Show the whats-after → bmad-help rename in this file


commit ec8ab0c63871e652cae1b9b1da42d0f798f5f046
Author: Brian Madison <brianmadison@Brians-MacBook-Pro.local>
Date:   Wed Jan 21 14:05:57 2026 -0600

    workflow tracking evolved to bmad-help

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
index 43ed4ce6..22a20d3a 100644
--- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
+++ b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
@@ -41,7 +41,7 @@ completedAt: '{{current_date}}'

 ### 3. Next Steps Guidance

-Execute task `_bmad/bmm/tasks/whats-after.md` with argument `Create Architecture`.
+Execute task `_bmad/bmm/tasks/bmad-help.md` with argument `Create Architecture`.

 Upon Completion of task output: offer to answer any questions about the Architecture Document.


git -C /Users/alex/src/bmad/quick-flow-redesign log --all --oneline -S "with argument" -- "src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md" --follow

Check if there's another commit that changed to help.md


git -C /Users/alex/src/bmad/quick-flow-redesign log --all --oneline -S "help.md" -- "src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md"

Find when help.md replaced bmad-help.md


ec8ab0c6 workflow tracking evolved to bmad-help


git -C /Users/alex/src/bmad/quick-flow-redesign log --all --oneline -- "src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md" | head -10

Full commit history for this file


d0ecfc0d fix: standardize all relative step file refs to {project-root}/_bmad/ paths (#1722)
3fb077cf fix: replace bare _bmad/ backtick refs with {project-root}/_bmad/
90d9204d fix: update help task path from bmad-help.md to help.md
def8da0a refactor: replace 'execute' with 'Read fully and follow:' in workflow prompts (#1387)
43508ef7 refactor: replace 'execute' with 'Read fully and follow:' in workflow prompts
c9c3d31d add the phase four items to the workflow csv for bmm. compile all csv to a install file. improve the bmad-help to know how to  work with the csv that contains the workflows from all installed modules
ec8ab0c6 workflow tracking evolved to bmad-help
37346079 workflow drastic simplification and more reliable
6f8f0871 Project Cleanup of Agents Menus, BMB module removal to other repo


git -C /Users/alex/src/bmad/quick-flow-redesign log def8da0a --format="%B" -1

Show commit that changed Execute to Read fully and follow


refactor: replace 'execute' with 'Read fully and follow:' in workflow prompts (#1387)

Replace ambiguous "execute" terminology with explicit "Read fully and follow:"
phrasing across all workflow files to prevent LLM goal-seeking behavior where
models attempt to "achieve the end result" rather than following step-by-step
instructions verbatim.

Changes:
- Update 5 handler templates with canonical phrasing
- Replace ~150 INSTRUCTIONAL patterns across 87 workflow files
- Add "[Workflow] complete." prefix to 7 workflow endpoints
- Preserve BEHAVIORAL/STRUCTURAL patterns (agent descriptions, XML tags)
- Fix gitignore and markdownlint to ignore all node_modules directories

Closes #1372

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>


git -C /Users/alex/src/bmad/quick-flow-redesign show def8da0a -- "src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md"

Show the diff for the Execute → Read fully and follow change


commit def8da0acbbcfc2cf6b3236b7cfedbfc17b66e80
Author: Alex Verkhovsky <alexey.verkhovsky@gmail.com>
Date:   Fri Jan 23 20:25:19 2026 -0800

    refactor: replace 'execute' with 'Read fully and follow:' in workflow prompts (#1387)

    Replace ambiguous "execute" terminology with explicit "Read fully and follow:"
    phrasing across all workflow files to prevent LLM goal-seeking behavior where
    models attempt to "achieve the end result" rather than following step-by-step
    instructions verbatim.

    Changes:
    - Update 5 handler templates with canonical phrasing
    - Replace ~150 INSTRUCTIONAL patterns across 87 workflow files
    - Add "[Workflow] complete." prefix to 7 workflow endpoints
    - Preserve BEHAVIORAL/STRUCTURAL patterns (agent descriptions, XML tags)
    - Fix gitignore and markdownlint to ignore all node_modules directories

    Closes #1372

    Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
index 66160ca3..f317bddf 100644
--- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
+++ b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
@@ -41,7 +41,7 @@ completedAt: '{{current_date}}'

 ### 3. Next Steps Guidance

-Execute task `_bmad/core/tasks/bmad-help.md` with argument `Create Architecture`.
+Architecture complete. Read fully and follow: `_bmad/core/tasks/bmad-help.md` with argument `Create Architecture`.

 Upon Completion of task output: offer to answer any questions about the Architecture Document.


So, it's the story of replacing execute with read fully and follow and forgetting to get rid of the with argument blah?


Here's the full picture:

**Commit timeline:**

1. **`37346079`** (Jan 20) — "workflow drastic simplification and more reliable" — Introduced `Execute task _bmad/bmm/tasks/whats-after.md with argument X`. The `whats-after.md` task was explicitly designed to receive a workflow name as input — its INPUT section says: *"Task input argument may provide: A workflow name just completed."*

2. **`ec8ab0c6`** (Jan 21) — "workflow tracking evolved to bmad-help" — Renamed `whats-after.md` → `bmad-help.md`, mechanical path update. `with argument` preserved because the task still expected it.

3. **`def8da0a`** (Jan 23) — "replace 'execute' with 'Read fully and follow:'" — Changed `Execute task` → `Read fully and follow:` to prevent LLMs from goal-seeking. But **kept `with argument`** because that was addressing a different problem (task invocation phrasing vs. input passing).

4. Later commits moved `bmad-help.md` → `help.md` and fixed paths.

**So here's what I got wrong:** The `with argument` wasn't just decorative phrasing — it was the **original input mechanism** for `whats-after.md`, which was explicitly designed to receive a workflow name. When that task evolved into `help.md`, the input contract changed (help.md added context inference as a fallback), but the `with argument` clause was carried forward as legacy.

The question is whether `help.md` actually relies on that argument or just tolerates it. Looking at help.md's INPUT ANALYSIS, it does say "If still unclear, ask" — meaning the argument was providing a **guarantee** that help.md wouldn't need to guess or ask.

Dropping it means help.md falls back to context inference, which should work in practice (the "[Workflow] complete." text is right there), but it's removing a deliberate input channel, not a meaningless artifact. Worth knowing.

Does this change your mind on the approach, or are you still good with dropping it?


say "The with-argument was an intentional input mechanism from the original whats-after task. Help dot MD inherited it. Want to revise the approach?"

TTS summary


TTS summary


Not exactly. The `Execute task X with argument Y` was a coherent pattern — "execute" + "with argument" worked together as a task invocation. When `def8da0a` replaced `Execute` with `Read fully and follow:`, it addressed the verb ("execute" triggers goal-seeking) but left `with argument` dangling because it was treated as a separate concern — the argument was still the input mechanism for the task.

So it's less "forgot to remove" and more "fixed one half of the problem." The `Read fully and follow:` fix was correct but incomplete — it made the file-read unambiguous while leaving the argument clause that now reads as a function parameter to LLMs.

Either way, the fix is the same: drop it. The approach in the spec stands. **[A]?**


say "The execute fix addressed the verb but left the argument clause dangling. Fix is the same either way. Approve?"

TTS summary


Okay, approve.


The user approved the spec. Per Step 2 instructions:
- **A**: Rename to `tech-spec-{slug}.md`, status `ready-for-dev`, freeze Problem/Solution/Scope/Non-Goals/Golden Examples. → Step 3.

Let me rename the WIP file, update the status, then load Step 3.


     1→---
     2→title: 'Remove ambiguous with-argument from help task chaining'
     3→slug: 'remove-with-argument-help-chaining'
     4→created: '2026-02-22'
     5→status: 'in-progress'
     6→---
     7→
     8→# Remove ambiguous "with argument" from help task chaining
     9→
    10→## Problem
    11→
    12→All 7 BMM workflow completion steps chain to `help.md` using:
    13→
    14→```
    15→[Workflow] complete. Read fully and follow: `…/help.md` with argument `[name]`.
    16→```
    17→
    18→The `with argument` clause causes LLMs to interpret this as a programmatic skill/function invocation instead of a file-read instruction, triggering "unknown skill" errors.
    19→
    20→Additionally:
    21→- **File #1** (`create-product-brief/step-06-complete.md`) passes `Validate PRD` — that's the *next* workflow, not the one just completed (CSV name: "Create Brief", code CB). This is a separate bug.
    22→- **File #7** (`check-implementation-readiness/step-06-final-assessment.md`) uses lowercase `implementation readiness` vs CSV name `Check Implementation Readiness` — casing mismatch.
    23→
    24→## Solution
    25→
    26→Drop the `with argument X` clause entirely from all 7 files. The workflow name is already stated in the preceding sentence (e.g., "Product Brief complete.", "PRD complete."), and `help.md`'s INPUT ANALYSIS section already infers what was just completed from:
    27→
    28→> - Explicit completion stated by user
    29→> - Workflow completed in current conversation
    30→
    31→No changes to `help.md` itself are needed — it already handles the argument-free case.
    32→
    33→## Scope
    34→
    35→**In:** Remove `with argument …` from 7 workflow completion step files under `src/bmm/workflows/`.
    36→
    37→**Out:** Changes to `help.md`, changes to the CSV catalog, any other refactoring of help task chaining.
    38→
    39→## Non-Goals
    40→
    41→- Redesigning how help.md detects what was just completed
    42→- Changing the "Read fully and follow" pattern itself
    43→- Fixing any other issues in these completion step files
    44→
    45→## Tasks
    46→
    47→- [ ] Task 1: `src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md` line 131 -- Remove ` with argument \`Validate PRD\`` from the help chaining line. This also fixes the File #1 bug (wrong argument) since the preceding text "Product Brief complete." is correct context. -- Eliminates ambiguous invocation and fixes wrong-argument bug simultaneously.
    48→
    49→- [ ] Task 2: `src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md` line 90 -- Remove ` with argument \`Create PRD\`` from the help chaining line. -- Preceding text "PRD complete." is sufficient.
    50→
    51→- [ ] Task 3: `src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md` line 200 -- Remove ` with argument \`Validate PRD\`` from the help chaining line. -- Preceding text "PRD Validation complete." is sufficient.
    52→
    53→- [ ] Task 4: `src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md` line 85 -- Remove ` with argument \`Create UX\`` from the help chaining line. -- Preceding text "UX Design complete." is sufficient.
    54→
    55→- [ ] Task 5: `src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md` line 44 -- Remove ` with argument \`Create Architecture\`` from the help chaining line. -- Preceding text "Architecture complete." is sufficient.
    56→
    57→- [ ] Task 6: `src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md` line 147 -- Remove ` with argument \`Create Epics and Stories\`` from the help chaining line. -- Preceding text "Epics and Stories complete." is sufficient.
    58→
    59→- [ ] Task 7: `src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md` line 112 -- Remove ` with argument \`implementation readiness\`` from the help chaining line. This also fixes the File #7 casing mismatch since the argument is removed entirely. -- Preceding text "Implementation Readiness complete." is sufficient.
    60→
    61→- [ ] Task 8: Validation -- Run `grep -r "with argument" src/` to confirm zero remaining instances. -- Ensures no instances were missed.
    62→
    63→## Acceptance Criteria
    64→
    65→- [ ] AC 1: Given any of the 7 completion step files, when the LLM reaches the help chaining line, then it reads `help.md` as a file (no skill/function invocation attempted).
    66→- [ ] AC 2: Given the modified chaining lines, when `help.md` processes the conversation, then it correctly infers the completed workflow from the preceding "[Workflow] complete." text.
    67→- [ ] AC 3: Given a grep for `with argument` across `src/`, when the search completes, then zero matches are returned.
    68→
    69→## Technical Decisions
    70→
    71→The simplest fix wins. The `with argument` clause was the only source of ambiguity. Each completion line already contains a clear "[Workflow] complete." statement that `help.md` can use for inference. No new mechanism is needed.
    72→
    73→## Golden Examples
    74→
    75→**Before (File #5):**
    76→```
    77→Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
    78→```
    79→
    80→**After (File #5):**
    81→```
    82→Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
    83→```
    84→
    85→## Spec Change Log
    86→
    87→<!-- Appended by the review loop. Each entry: what changed, what triggered it, what bad state it avoids, KEEP instructions. Empty until step 4. -->
    88→
    89→## Notes
    90→
    91→- File #1's `Validate PRD` argument was a pre-existing bug (wrong workflow name). Dropping arguments makes this moot.
    92→- File #7's casing mismatch similarly becomes moot.
    93→- The fix is purely subtractive — removing text, not adding or restructuring.
    94→

---
title: 'Remove ambiguous with-argument from help task chaining'
slug: 'remove-with-argument-help-chaining'
created: '2026-02-22'
status: 'in-progress'
---

# Remove ambiguous "with argument" from help task chaining

## Problem

All 7 BMM workflow completion steps chain to `help.md` using:

```
[Workflow] complete. Read fully and follow: `…/help.md` with argument `[name]`.
```

The `with argument` clause causes LLMs to interpret this as a programmatic skill/function invocation instead of a file-read instruction, triggering "unknown skill" errors.

Additionally:
- **File #1** (`create-product-brief/step-06-complete.md`) passes `Validate PRD` — that's the *next* workflow, not the one just completed (CSV name: "Create Brief", code CB). This is a separate bug.
- **File #7** (`check-implementation-readiness/step-06-final-assessment.md`) uses lowercase `implementation readiness` vs CSV name `Check Implementation Readiness` — casing mismatch.

## Solution

Drop the `with argument X` clause entirely from all 7 files. The workflow name is already stated in the preceding sentence (e.g., "Product Brief complete.", "PRD complete."), and `help.md`'s INPUT ANALYSIS section already infers what was just completed from:

> - Explicit completion stated by user
> - Workflow completed in current conversation

No changes to `help.md` itself are needed — it already handles the argument-free case.

## Scope

**In:** Remove `with argument …` from 7 workflow completion step files under `src/bmm/workflows/`.

**Out:** Changes to `help.md`, changes to the CSV catalog, any other refactoring of help task chaining.

## Non-Goals

- Redesigning how help.md detects what was just completed
- Changing the "Read fully and follow" pattern itself
- Fixing any other issues in these completion step files

## Tasks

- [ ] Task 1: `src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md` line 131 -- Remove ` with argument \`Validate PRD\`` from the help chaining line. This also fixes the File #1 bug (wrong argument) since the preceding text "Product Brief complete." is correct context. -- Eliminates ambiguous invocation and fixes wrong-argument bug simultaneously.

- [ ] Task 2: `src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md` line 90 -- Remove ` with argument \`Create PRD\`` from the help chaining line. -- Preceding text "PRD complete." is sufficient.

- [ ] Task 3: `src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md` line 200 -- Remove ` with argument \`Validate PRD\`` from the help chaining line. -- Preceding text "PRD Validation complete." is sufficient.

- [ ] Task 4: `src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md` line 85 -- Remove ` with argument \`Create UX\`` from the help chaining line. -- Preceding text "UX Design complete." is sufficient.

- [ ] Task 5: `src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md` line 44 -- Remove ` with argument \`Create Architecture\`` from the help chaining line. -- Preceding text "Architecture complete." is sufficient.

- [ ] Task 6: `src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md` line 147 -- Remove ` with argument \`Create Epics and Stories\`` from the help chaining line. -- Preceding text "Epics and Stories complete." is sufficient.

- [ ] Task 7: `src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md` line 112 -- Remove ` with argument \`implementation readiness\`` from the help chaining line. This also fixes the File #7 casing mismatch since the argument is removed entirely. -- Preceding text "Implementation Readiness complete." is sufficient.

- [ ] Task 8: Validation -- Run `grep -r "with argument" src/` to confirm zero remaining instances. -- Ensures no instances were missed.

## Acceptance Criteria

- [ ] AC 1: Given any of the 7 completion step files, when the LLM reaches the help chaining line, then it reads `help.md` as a file (no skill/function invocation attempted).
- [ ] AC 2: Given the modified chaining lines, when `help.md` processes the conversation, then it correctly infers the completed workflow from the preceding "[Workflow] complete." text.
- [ ] AC 3: Given a grep for `with argument` across `src/`, when the search completes, then zero matches are returned.

## Technical Decisions

The simplest fix wins. The `with argument` clause was the only source of ambiguity. Each completion line already contains a clear "[Workflow] complete." statement that `help.md` can use for inference. No new mechanism is needed.

## Golden Examples

**Before (File #5):**
```
Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
```

**After (File #5):**
```
Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## Spec Change Log

<!-- Appended by the review loop. Each entry: what changed, what triggered it, what bad state it avoids, KEEP instructions. Empty until step 4. -->

## Notes

- File #1's `Validate PRD` argument was a pre-existing bug (wrong workflow name). Dropping arguments makes this moot.
- File #7's casing mismatch similarly becomes moot.
- The fix is purely subtractive — removing text, not adding or restructuring.


The file /Users/alex/src/bmad/quick-flow-redesign/_bmad-output/implementation-artifacts/tech-spec-wip.md has been updated successfully.

---
title: 'Remove ambiguous with-argument from help task chaining'
slug: 'remove-with-argument-help-chaining'
created: '2026-02-22'
status: 'in-progress'
---

# Remove ambiguous "with argument" from help task chaining

## Problem

All 7 BMM workflow completion steps chain to `help.md` using:

```
[Workflow] complete. Read fully and follow: `…/help.md` with argument `[name]`.
```

The `with argument` clause causes LLMs to interpret this as a programmatic skill/function invocation instead of a file-read instruction, triggering "unknown skill" errors.

Additionally:
- **File #1** (`create-product-brief/step-06-complete.md`) passes `Validate PRD` — that's the *next* workflow, not the one just completed (CSV name: "Create Brief", code CB). This is a separate bug.
- **File #7** (`check-implementation-readiness/step-06-final-assessment.md`) uses lowercase `implementation readiness` vs CSV name `Check Implementation Readiness` — casing mismatch.

## Solution

Drop the `with argument X` clause entirely from all 7 files. The workflow name is already stated in the preceding sentence (e.g., "Product Brief complete.", "PRD complete."), and `help.md`'s INPUT ANALYSIS section already infers what was just completed from:

> - Explicit completion stated by user
> - Workflow completed in current conversation

No changes to `help.md` itself are needed — it already handles the argument-free case.

## Scope

**In:** Remove `with argument …` from 7 workflow completion step files under `src/bmm/workflows/`.

**Out:** Changes to `help.md`, changes to the CSV catalog, any other refactoring of help task chaining.

## Non-Goals

- Redesigning how help.md detects what was just completed
- Changing the "Read fully and follow" pattern itself
- Fixing any other issues in these completion step files

## Tasks

- [ ] Task 1: `src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md` line 131 -- Remove ` with argument \`Validate PRD\`` from the help chaining line. This also fixes the File #1 bug (wrong argument) since the preceding text "Product Brief complete." is correct context. -- Eliminates ambiguous invocation and fixes wrong-argument bug simultaneously.

- [ ] Task 2: `src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md` line 90 -- Remove ` with argument \`Create PRD\`` from the help chaining line. -- Preceding text "PRD complete." is sufficient.

- [ ] Task 3: `src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md` line 200 -- Remove ` with argument \`Validate PRD\`` from the help chaining line. -- Preceding text "PRD Validation complete." is sufficient.

- [ ] Task 4: `src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md` line 85 -- Remove ` with argument \`Create UX\`` from the help chaining line. -- Preceding text "UX Design complete." is sufficient.

- [ ] Task 5: `src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md` line 44 -- Remove ` with argument \`Create Architecture\`` from the help chaining line. -- Preceding text "Architecture complete." is sufficient.

- [ ] Task 6: `src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md` line 147 -- Remove ` with argument \`Create Epics and Stories\`` from the help chaining line. -- Preceding text "Epics and Stories complete." is sufficient.

- [ ] Task 7: `src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md` line 112 -- Remove ` with argument \`implementation readiness\`` from the help chaining line. This also fixes the File #7 casing mismatch since the argument is removed entirely. -- Preceding text "Implementation Readiness complete." is sufficient.

- [ ] Task 8: Validation -- Run `grep -r "with argument" src/` to confirm zero remaining instances. -- Ensures no instances were missed.

## Acceptance Criteria

- [ ] AC 1: Given any of the 7 completion step files, when the LLM reaches the help chaining line, then it reads `help.md` as a file (no skill/function invocation attempted).
- [ ] AC 2: Given the modified chaining lines, when `help.md` processes the conversation, then it correctly infers the completed workflow from the preceding "[Workflow] complete." text.
- [ ] AC 3: Given a grep for `with argument` across `src/`, when the search completes, then zero matches are returned.

## Technical Decisions

The simplest fix wins. The `with argument` clause was the only source of ambiguity. Each completion line already contains a clear "[Workflow] complete." statement that `help.md` can use for inference. No new mechanism is needed.

## Golden Examples

**Before (File #5):**
```
Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.
```

**After (File #5):**
```
Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
```

## Spec Change Log

<!-- Appended by the review loop. Each entry: what changed, what triggered it, what bad state it avoids, KEEP instructions. Empty until step 4. -->

## Notes

- File #1's `Validate PRD` argument was a pre-existing bug (wrong workflow name). Dropping arguments makes this moot.
- File #7's casing mismatch similarly becomes moot.
- The fix is purely subtractive — removing text, not adding or restructuring.


Rename WIP spec to final slug name


Spec approved and frozen. Loading Step 3.


     1→---
     2→name: 'step-03-implement'
     3→description: 'Branch, shard tasks, execute, commit. Local only.'
     4→---
     5→
     6→# Step 3: Implement
     7→
     8→**Step 3 of 5 — Autonomous. Local only.**
     9→
    10→## RULES
    11→
    12→- No push. No remote ops.
    13→- Sequential execution only.
    14→- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
    15→
    16→---
    17→
    18→## INSTRUCTIONS
    19→
    20→Implement the spec.
    21→One-shot: implement the intent.
    22→
    23→---
    24→
    25→## NEXT
    26→
    27→`{installed_path}/steps/step-04-review.md`
    28→

---
name: 'step-03-implement'
description: 'Branch, shard tasks, execute, commit. Local only.'
---

# Step 3: Implement

**Step 3 of 5 — Autonomous. Local only.**

## RULES

- No push. No remote ops.
- Sequential execution only.
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`

---

## INSTRUCTIONS

Implement the spec.
One-shot: implement the intent.

---

## NEXT

`{installed_path}/steps/step-04-review.md`


Implementing now. All 7 edits, sequential.


Edit

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`


The file /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md has been updated successfully.

---
name: 'step-06-complete'
description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'

# File References
outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
---

# Step 6: Product Brief Completion

## STEP GOAL:

Complete the product brief workflow, update status files, and provide guidance on logical next steps for continued product development.

## MANDATORY EXECUTION RULES (READ FIRST):

### Universal Rules:

- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`

### Role Reinforcement:

- ✅ You are a product-focused Business Analyst facilitator
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
- ✅ Maintain collaborative completion tone throughout

### Step-Specific Rules:

- 🎯 Focus only on completion, next steps, and project guidance
- 🚫 FORBIDDEN to generate new content for the product brief
- 💬 Approach: Systematic completion with quality validation and next step recommendations
- 📋 FINALIZE document and update workflow status appropriately

## EXECUTION PROTOCOLS:

- 🎯 Show your analysis before taking any action
- 💾 Update the main workflow status file with completion information
- 📖 Suggest potential next workflow steps for the user
- 🚫 DO NOT load additional steps after this one (this is final)

## CONTEXT BOUNDARIES:

- Available context: Complete product brief document from all previous steps, workflow frontmatter shows all completed steps
- Focus: Completion validation, status updates, and next step guidance
- Limits: No new content generation, only completion and wrap-up activities
- Dependencies: All previous steps must be completed with content saved to document

## Sequence of Instructions (Do not deviate, skip, or optimize)

### 1. Announce Workflow Completion

**Completion Announcement:**
"🎉 **Product Brief Complete, {{user_name}}!**

I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.

**What we've accomplished:**

- ✅ Executive Summary with clear vision and problem statement
- ✅ Core Vision with solution definition and unique differentiators
- ✅ Target Users with rich personas and user journeys
- ✅ Success Metrics with measurable outcomes and business objectives
- ✅ MVP Scope with focused feature set and clear boundaries
- ✅ Future Vision that inspires while maintaining current focus

**The complete Product Brief is now available at:** `{outputFile}`

This brief serves as the foundation for all subsequent product development activities and strategic decisions."

### 2. Document Quality Check

**Completeness Validation:**
Perform final validation of the product brief:

- Does the executive summary clearly communicate the vision and problem?
- Are target users well-defined with compelling personas?
- Do success metrics connect user value to business objectives?
- Is MVP scope focused and realistic?
- Does the brief provide clear direction for next steps?

**Consistency Validation:**

- Do all sections align with the core problem statement?
- Is user value consistently emphasized throughout?
- Are success criteria traceable to user needs and business goals?
- Does MVP scope align with the problem and solution?

### 3. Suggest Next Steps

**Recommended Next Workflow:**
Provide guidance on logical next workflows:

1. `create-prd` - Create detailed Product Requirements Document
   - Brief provides foundation for detailed requirements
   - User personas inform journey mapping
   - Success metrics become specific acceptance criteria
   - MVP scope becomes detailed feature specifications

**Other Potential Next Steps:**

1. `create-ux-design` - UX research and design (can run parallel with PRD)
2. `domain-research` - Deep market or domain research (if needed)

**Strategic Considerations:**

- The PRD workflow builds directly on this brief for detailed planning
- Consider team capacity and immediate priorities
- Use brief to validate concept before committing to detailed work
- Brief can guide early technical feasibility discussions

### 4. Congrats to the user

"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**"

Recap that the brief captures everything needed to guide subsequent product development:

- Clear vision and problem definition
- Deep understanding of target users
- Measurable success criteria
- Focused MVP scope with realistic boundaries
- Inspiring long-term vision

### 5. Suggest next steps

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

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:

- Product brief contains all essential sections with collaborative content
- All collaborative content properly saved to document with proper frontmatter
- Workflow status file updated with completion information and timestamp
- Clear next step guidance provided to user with specific workflow recommendations
- Document quality validation completed with completeness and consistency checks
- User acknowledges completion and understands next available options
- Workflow properly marked as complete in status tracking

### ❌ SYSTEM FAILURE:

- Not updating workflow status file with completion information
- Missing clear next step guidance for user
- Not confirming document completeness with user
- Workflow not properly marked as complete in status tracking
- User unclear about what happens next or available options
- Document quality issues not identified or addressed

**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

## FINAL WORKFLOW COMPLETION

This product brief is now complete and serves as the strategic foundation for the entire product lifecycle. All subsequent design, architecture, and development work should trace back to the vision, user needs, and success criteria documented in this brief.

**Congratulations on completing the Product Brief for {{project_name}}!** 🎉

-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`


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`


The file /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md has been updated successfully.

---
name: 'step-12-complete'
description: 'Complete the PRD workflow, update status files, and suggest next steps including validation'

# File References
outputFile: '{planning_artifacts}/prd.md'
validationFlow: '../steps-v/step-v-01-discovery.md'
---

# Step 12: Workflow Completion

**Final Step - Complete the PRD**

## MANDATORY EXECUTION RULES (READ FIRST):

- ✅ THIS IS A FINAL STEP - Workflow completion required
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action
- 🛑 NO content generation - this is a wrap-up step
- 📋 FINALIZE document and update workflow status
- 💬 FOCUS on completion, validation options, and next steps
- 🎯 UPDATE workflow status files with completion information
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`

## EXECUTION PROTOCOLS:

- 🎯 Show your analysis before taking any action
- 💾 Update the main workflow status file with completion information (if exists)
- 📖 Offer validation workflow options to user
- 🚫 DO NOT load additional steps after this one

## TERMINATION STEP PROTOCOLS:

- This is a FINAL step - workflow completion required
- Update workflow status file with finalized document
- Suggest validation and next workflow steps
- Mark workflow as complete in status tracking

## CONTEXT BOUNDARIES:

- Complete and polished PRD document is available from all previous steps
- Workflow frontmatter shows all completed steps including polish
- All collaborative content has been generated, saved, and optimized
- Focus on completion, validation options, and next steps

## YOUR TASK:

Complete the PRD workflow, update status files, offer validation options, and suggest next steps for the project.

## WORKFLOW COMPLETION SEQUENCE:

### 1. Announce Workflow Completion

Inform user that the PRD is complete and polished:
- Celebrate successful completion of comprehensive PRD
- Summarize all sections that were created
- Highlight that document has been polished for flow and coherence
- Emphasize document is ready for downstream work

### 2. Workflow Status Update

Update the main workflow status file if there is one:

- Load `{status_file}` from workflow configuration (if exists)
- Update workflow_status["prd"] = "{default_output_file}"
- Save file, preserving all comments and structure
- Mark current timestamp as completion time

### 3. Validation Workflow Options

Offer validation workflows to ensure PRD is ready for implementation:

**Available Validation Workflows:**

**Option 1: Check Implementation Readiness** (`{checkImplementationReadinessWorkflow}`)
- Validates PRD has all information needed for development
- Checks epic coverage completeness
- Reviews UX alignment with requirements
- Assesses epic quality and readiness
- Identifies gaps before architecture/design work begins

**When to use:** Before starting technical architecture or epic breakdown

**Option 2: Skip for Now**
- Proceed directly to next workflows (architecture, UX, epics)
- 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` with argument `Create PRD`.

### 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
✅ All collaborative content properly saved and optimized
✅ Workflow status file updated with completion information (if exists)
✅ Validation workflow options clearly presented
✅ Clear next step guidance provided to user
✅ Document quality validation completed
✅ User acknowledges completion and understands next options

## FAILURE MODES:

❌ Not updating workflow status file with completion information (if exists)
❌ Not offering validation workflow options
❌ Missing clear next step guidance for user
❌ Not confirming document completeness with user
❌ Workflow not properly marked as complete in status tracking (if applicable)
❌ User unclear about what happens next or what validation options exist

❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols

## FINAL REMINDER to give the user:

The polished PRD serves as the foundation for all subsequent product development activities. All design, architecture, and development work should trace back to the requirements and vision documented in this PRD - update it also as needed as you continue planning.

**Congratulations on completing the Product Requirements Document for {{project_name}}!** 🎉

-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`


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`


The file /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md has been updated successfully.

---
name: 'step-v-13-report-complete'
description: 'Validation Report Complete - Finalize report, summarize findings, present to user, offer next steps'

# File references (ONLY variables used in this step)
validationReportPath: '{validation_report_path}'
prdFile: '{prd_file_path}'
---

# Step 13: Validation Report Complete

## STEP GOAL:

Finalize validation report, summarize all findings from steps 1-12, present summary to user conversationally, and offer actionable next steps.

## MANDATORY EXECUTION RULES (READ FIRST):

### Universal Rules:

- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`

### Role Reinforcement:

- ✅ You are a Validation Architect and Quality Assurance Specialist
- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring synthesis and summary expertise
- ✅ This is the FINAL step - requires user interaction

### Step-Specific Rules:

- 🎯 Focus ONLY on summarizing findings and presenting options
- 🚫 FORBIDDEN to perform additional validation
- 💬 Approach: Conversational summary with clear next steps
- 🚪 This is the final step - no next step after this

## EXECUTION PROTOCOLS:

- 🎯 Load complete validation report
- 🎯 Summarize all findings from steps 1-12
- 🎯 Update report frontmatter with final status
- 💬 Present summary to user conversationally
- 💬 Offer menu options for next actions
- 🚫 FORBIDDEN to proceed without user selection

## CONTEXT BOUNDARIES:

- Available context: Complete validation report with findings from all validation steps
- Focus: Summary and presentation only (no new validation)
- Limits: Don't add new findings, just synthesize existing
- Dependencies: Steps 1-12 completed - all validation checks done

## MANDATORY SEQUENCE

**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.

### 1. Load Complete Validation Report

Read the entire validation report from {validationReportPath}

Extract all findings from:
- Format Detection (Step 2)
- Parity Analysis (Step 2B, if applicable)
- Information Density (Step 3)
- Product Brief Coverage (Step 4)
- Measurability (Step 5)
- Traceability (Step 6)
- Implementation Leakage (Step 7)
- Domain Compliance (Step 8)
- Project-Type Compliance (Step 9)
- SMART Requirements (Step 10)
- Holistic Quality (Step 11)
- Completeness (Step 12)

### 2. Update Report Frontmatter with Final Status

Update validation report frontmatter:

```yaml
---
validationTarget: '{prd_path}'
validationDate: '{current_date}'
inputDocuments: [list of documents]
validationStepsCompleted: ['step-v-01-discovery', 'step-v-02-format-detection', 'step-v-03-density-validation', 'step-v-04-brief-coverage-validation', 'step-v-05-measurability-validation', 'step-v-06-traceability-validation', 'step-v-07-implementation-leakage-validation', 'step-v-08-domain-compliance-validation', 'step-v-09-project-type-validation', 'step-v-10-smart-validation', 'step-v-11-holistic-quality-validation', 'step-v-12-completeness-validation']
validationStatus: COMPLETE
holisticQualityRating: '{rating from step 11}'
overallStatus: '{Pass/Warning/Critical based on all findings}'
---
```

### 3. Create Summary of Findings

**Overall Status:**
- Determine from all validation findings
- **Pass:** All critical checks pass, minor warnings acceptable
- **Warning:** Some issues found but PRD is usable
- **Critical:** Major issues that prevent PRD from being fit for purpose

**Quick Results Table:**
- Format: [classification]
- Information Density: [severity]
- Measurability: [severity]
- Traceability: [severity]
- Implementation Leakage: [severity]
- Domain Compliance: [status]
- Project-Type Compliance: [compliance score]
- SMART Quality: [percentage]
- Holistic Quality: [rating/5]
- Completeness: [percentage]

**Critical Issues:** List from all validation steps
**Warnings:** List from all validation steps
**Strengths:** List positives from all validation steps

**Holistic Quality Rating:** From step 11
**Top 3 Improvements:** From step 11

**Recommendation:** Based on overall status

### 4. Present Summary to User Conversationally

Display:

"**✓ PRD Validation Complete**

**Overall Status:** {Pass/Warning/Critical}

**Quick Results:**
{Present quick results table with key findings}

**Critical Issues:** {count or "None"}
{If any, list briefly}

**Warnings:** {count or "None"}
{If any, list briefly}

**Strengths:**
{List key strengths}

**Holistic Quality:** {rating}/5 - {label}

**Top 3 Improvements:**
1. {Improvement 1}
2. {Improvement 2}
3. {Improvement 3}

**Recommendation:**
{Based on overall status:
- Pass: "PRD is in good shape. Address minor improvements to make it great."
- Warning: "PRD is usable but has issues that should be addressed. Review warnings and improve where needed."
- Critical: "PRD has significant issues that should be fixed before use. Focus on critical issues above."}

**What would you like to do next?**"

### 5. Present MENU OPTIONS

Display:

**[R] Review Detailed Findings** - Walk through validation report section by section
**[E] Use Edit Workflow** - Use validation report with Edit workflow for systematic improvements
**[F] Fix Simpler Items** - Immediate fixes for simple issues (anti-patterns, leakage, missing headers)
**[X] Exit** - Exit and Suggest Next Steps.

#### EXECUTION RULES:

- ALWAYS halt and wait for user input after presenting menu
- Only proceed based on user selection

#### Menu Handling Logic:

- **IF R (Review Detailed Findings):**
  - Walk through validation report section by section
  - Present findings from each validation step
  - Allow user to ask questions
  - After review, return to menu

- **IF E (Use Edit Workflow):**
  - Explain: "The Edit workflow (steps-e/) can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
  - Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
  - If yes: Read fully and follow: steps-e/step-e-01-discovery.md
  - If no: Return to menu

- **IF F (Fix Simpler Items):**
  - Offer immediate fixes for:
    - Template variables (fill in with appropriate content)
    - Conversational filler (remove wordy phrases)
    - Implementation leakage (remove technology names from FRs/NFRs)
    - Missing section headers (add ## headers)
  - Ask: "Which simple fixes would you like me to make?"
  - If user specifies fixes, make them and update validation report
  - Return to menu

- **IF X (Exit):**
  - Display: "**Validation Report Saved:** {validationReportPath}"
  - Display: "**Summary:** {overall status} - {recommendation}"
  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Validate PRD`.

- **IF Any other:** Help user, then redisplay menu

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:

- Complete validation report loaded successfully
- All findings from steps 1-12 summarized
- Report frontmatter updated with final status
- Overall status determined correctly (Pass/Warning/Critical)
- Quick results table presented
- Critical issues, warnings, and strengths listed
- Holistic quality rating included
- Top 3 improvements presented
- Clear recommendation provided
- Menu options presented with clear explanations
- User can review findings, get help, or exit

### ❌ SYSTEM FAILURE:

- Not loading complete validation report
- Missing summary of findings
- Not updating report frontmatter
- Not determining overall status
- Missing menu options
- Unclear next steps

**Master Rule:** User needs clear summary and actionable next steps. Edit workflow is best for complex issues; immediate fixes available for simpler ones.

-  - 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`


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`


The file /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md has been updated successfully.

# Step 14: Workflow Completion

## MANDATORY EXECUTION RULES (READ FIRST):

- ✅ THIS IS A FINAL STEP - Workflow completion required

- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
- 🛑 NO content generation - this is a wrap-up step
- 📋 FINALIZE document and update workflow status
- 💬 FOCUS on completion, validation, and next steps
- 🎯 UPDATE workflow status files with completion information
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`

## EXECUTION PROTOCOLS:

- 🎯 Show your analysis before taking any action
- 💾 Update the main workflow status file with completion information
- 📖 Suggest potential next workflow steps for the user
- 🚫 DO NOT load additional steps after this one

## TERMINATION STEP PROTOCOLS:

- This is a FINAL step - workflow completion required
- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted to indicate all is finished..
- Output completion summary and next step guidance
- Update the main workflow status file with finalized document
- Suggest potential next workflow steps for the user
- Mark workflow as complete in status tracking

## CONTEXT BOUNDARIES:

- Complete UX design specification is available from all previous steps
- Workflow frontmatter shows all completed steps
- All collaborative content has been generated and saved
- Focus on completion, validation, and next steps

## YOUR TASK:

Complete the UX design workflow, update status files, and suggest next steps for the project.

## WORKFLOW COMPLETION SEQUENCE:

### 1. Announce Workflow Completion

Inform user that the UX design is complete:
"🎉 **UX Design Complete, {{user_name}}!**

I've successfully collaborated with you to create a comprehensive UX design specification for {{project_name}}.

**What we've accomplished:**

- ✅ Project understanding and user insights
- ✅ Core experience and emotional response definition
- ✅ UX pattern analysis and inspiration
- ✅ Design system choice and implementation strategy
- ✅ Core interaction definition and experience mechanics
- ✅ Visual design foundation (colors, typography, spacing)
- ✅ Design direction mockups and visual explorations
- ✅ User journey flows and interaction design
- ✅ Component strategy and custom component specifications
- ✅ UX consistency patterns for common interactions
- ✅ Responsive design and accessibility strategy

**The complete UX design specification is now available at:** `{planning_artifacts}/ux-design-specification.md`

**Supporting Visual Assets:**

- Color themes visualizer: `{planning_artifacts}/ux-color-themes.html`
- Design directions mockups: `{planning_artifacts}/ux-design-directions.html`

This specification is now ready to guide visual design, implementation, and development."

### 2. Workflow Status Update

Update the main workflow status file:

- Load `{status_file}` from workflow configuration (if exists)
- Update workflow_status["create-ux-design"] = "{default_output_file}"
- Save file, preserving all comments and structure
- Mark current timestamp as completion time

### 3. Suggest Next Steps

UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create UX`.

### 5. Final Completion Confirmation

Congratulate the user on the completion you both completed together of the UX.

## SUCCESS METRICS:

✅ UX design specification contains all required sections
✅ All collaborative content properly saved to document
✅ Workflow status file updated with completion information
✅ Clear next step guidance provided to user
✅ Document quality validation completed
✅ User acknowledges completion and understands next options

## FAILURE MODES:

❌ Not updating workflow status file with completion information
❌ Missing clear next step guidance for user
❌ Not confirming document completeness with user
❌ Workflow not properly marked as complete in status tracking
❌ User unclear about what happens next

❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols

## WORKFLOW COMPLETION CHECKLIST:

### Design Specification Complete:

- [ ] Executive summary and project understanding
- [ ] Core experience and emotional response definition
- [ ] UX pattern analysis and inspiration
- [ ] Design system choice and strategy
- [ ] Core interaction mechanics definition
- [ ] Visual design foundation (colors, typography, spacing)
- [ ] Design direction decisions and mockups
- [ ] User journey flows and interaction design
- [ ] Component strategy and specifications
- [ ] UX consistency patterns documentation
- [ ] Responsive design and accessibility strategy

### Process Complete:

- [ ] All steps completed with user confirmation
- [ ] All content saved to specification document
- [ ] Frontmatter properly updated with all steps
- [ ] Workflow status file updated with completion
- [ ] Next steps clearly communicated

## NEXT STEPS GUIDANCE:

**Immediate Options:**

1. **Wireframe Generation** - Create low-fidelity layouts based on UX spec
2. **Interactive Prototype** - Build clickable prototypes for testing
3. **Solution Architecture** - Technical design with UX context
4. **Figma Visual Design** - High-fidelity UI implementation
5. **Epic Creation** - Break down UX requirements for development

**Recommended Sequence:**
For design-focused teams: Wireframes → Prototypes → Figma Design → Development
For technical teams: Architecture → Epic Creation → Development

Consider team capacity, timeline, and whether user validation is needed before implementation.

## WORKFLOW FINALIZATION:

- Set `lastStep = 14` in document frontmatter
- Update workflow status file with completion timestamp
- Provide completion summary to user
- Do NOT load any additional steps

## FINAL REMINDER:

This UX design workflow is now complete. The specification serves as the foundation for all visual and development work. All design decisions, patterns, and requirements are documented to ensure consistent, accessible, and user-centered implementation.

**Congratulations on completing the UX Design Specification for {{project_name}}!** 🎉

**Core Deliverables:**

- ✅ UX Design Specification: `{planning_artifacts}/ux-design-specification.md`
- ✅ Color Themes Visualizer: `{planning_artifacts}/ux-color-themes.html`
- ✅ Design Directions: `{planning_artifacts}/ux-design-directions.html`

-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`


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`


The file /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md has been updated successfully.

# Step 8: Architecture Completion & Handoff

## MANDATORY EXECUTION RULES (READ FIRST):

- 🛑 NEVER generate content without user input

- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
- ✅ ALWAYS treat this as collaborative completion between architectural peers
- 📋 YOU ARE A FACILITATOR, not a content generator
- 💬 FOCUS on successful workflow completion and implementation handoff
- 🎯 PROVIDE clear next steps for implementation phase
- ⚠ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`

## EXECUTION PROTOCOLS:

- 🎯 Show your analysis before taking any action
- 🎯 Present completion summary and implementation guidance
- 📖 Update frontmatter with final workflow state
- 🚫 THIS IS THE FINAL STEP IN THIS WORKFLOW

## YOUR TASK:

Complete the architecture workflow, provide a comprehensive completion summary, and guide the user to the next phase of their project development.

## COMPLETION SEQUENCE:

### 1. Congratulate the User on Completion

Both you and the User completed something amazing here - give a summary of what you achieved together and really congratulate the user on a job well done.

### 2. Update the created document's frontmatter

```yaml
stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]
workflowType: 'architecture'
lastStep: 8
status: 'complete'
completedAt: '{{current_date}}'
```

### 3. Next Steps Guidance

Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Architecture`.

Upon Completion of task output: offer to answer any questions about the Architecture Document.

## SUCCESS METRICS:

✅ Complete architecture document delivered with all sections
✅ All architectural decisions documented and validated
✅ Implementation patterns and consistency rules finalized
✅ Project structure complete with all files and directories
✅ User provided with clear next steps and implementation guidance
✅ Workflow status properly updated
✅ User collaboration maintained throughout completion process

## FAILURE MODES:

❌ Not providing clear implementation guidance
❌ Missing final validation of document completeness
❌ Not updating workflow status appropriately
❌ Failing to celebrate the successful completion
❌ Not providing specific next steps for the user
❌ Rushing completion without proper summary

❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols

## WORKFLOW COMPLETE:

This is the final step of the Architecture workflow. The user now has a complete, validated architecture document ready for AI agent implementation.

The architecture will serve as the single source of truth for all technical decisions, ensuring consistent implementation across the entire project development lifecycle.

-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`


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 file /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md has been updated successfully.

---
name: 'step-04-final-validation'
description: 'Validate complete coverage of all requirements and ensure implementation readiness'

# Path Definitions
workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'

# File References
thisStepFile: './step-04-final-validation.md'
workflowFile: '{workflow_path}/workflow.md'
outputFile: '{planning_artifacts}/epics.md'

# Task References
advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'

# Template References
epicsTemplate: '{workflow_path}/templates/epics-template.md'
---

# Step 4: Final Validation

## STEP GOAL:

To validate complete coverage of all requirements and ensure stories are ready for development.

## MANDATORY EXECUTION RULES (READ FIRST):

### Universal Rules:

- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: Process validation sequentially without skipping
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`

### Role Reinforcement:

- ✅ You are a product strategist and technical specifications writer
- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring validation expertise and quality assurance
- ✅ User brings their implementation priorities and final review

### Step-Specific Rules:

- 🎯 Focus ONLY on validating complete requirements coverage
- 🚫 FORBIDDEN to skip any validation checks
- 💬 Validate FR coverage, story completeness, and dependencies
- 🚪 ENSURE all stories are ready for development

## EXECUTION PROTOCOLS:

- 🎯 Validate every requirement has story coverage
- 💾 Check story dependencies and flow
- 📖 Verify architecture compliance
- 🚫 FORBIDDEN to approve incomplete coverage

## CONTEXT BOUNDARIES:

- Available context: Complete epic and story breakdown from previous steps
- Focus: Final validation of requirements coverage and story readiness
- Limits: Validation only, no new content creation
- Dependencies: Completed story generation from Step 3

## VALIDATION PROCESS:

### 1. FR Coverage Validation

Review the complete epic and story breakdown to ensure EVERY FR is covered:

**CRITICAL CHECK:**

- Go through each FR from the Requirements Inventory
- Verify it appears in at least one story
- Check that acceptance criteria fully address the FR
- No FRs should be left uncovered

### 2. Architecture Implementation Validation

**Check for Starter Template Setup:**

- Does Architecture document specify a starter template?
- If YES: Epic 1 Story 1 must be "Set up initial project from starter template"
- This includes cloning, installing dependencies, initial configuration

**Database/Entity Creation Validation:**

- Are database tables/entities created ONLY when needed by stories?
- ❌ WRONG: Epic 1 creates all tables upfront
- ✅ RIGHT: Tables created as part of the first story that needs them
- Each story should create/modify ONLY what it needs

### 3. Story Quality Validation

**Each story must:**

- Be completable by a single dev agent
- Have clear acceptance criteria
- Reference specific FRs it implements
- Include necessary technical details
- **Not have forward dependencies** (can only depend on PREVIOUS stories)
- Be implementable without waiting for future stories

### 4. Epic Structure Validation

**Check that:**

- Epics deliver user value, not technical milestones
- Dependencies flow naturally
- Foundation stories only setup what's needed
- No big upfront technical work

### 5. Dependency Validation (CRITICAL)

**Epic Independence Check:**

- Does each epic deliver COMPLETE functionality for its domain?
- Can Epic 2 function without Epic 3 being implemented?
- Can Epic 3 function standalone using Epic 1 & 2 outputs?
- ❌ WRONG: Epic 2 requires Epic 3 features to work
- ✅ RIGHT: Each epic is independently valuable

**Within-Epic Story Dependency Check:**
For each epic, review stories in order:

- Can Story N.1 be completed without Stories N.2, N.3, etc.?
- Can Story N.2 be completed using only Story N.1 output?
- Can Story N.3 be completed using only Stories N.1 & N.2 outputs?
- ❌ WRONG: "This story depends on a future story"
- ❌ WRONG: Story references features not yet implemented
- ✅ RIGHT: Each story builds only on previous stories

### 6. Complete and Save

If all validations pass:

- Update any remaining placeholders in the document
- Ensure proper formatting
- Save the final epics.md

**Present Final Menu:**
**All validations complete!** [C] Complete Workflow

When C is selected, the workflow is complete and the epics.md is ready for development.

Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.

Upon Completion of task output: offer to answer any questions about the Epics and Stories.

-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`


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`


The file /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md has been updated successfully.

---
name: 'step-06-final-assessment'
description: 'Compile final assessment and polish the readiness report'

outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
---

# Step 6: Final Assessment

## STEP GOAL:

To provide a comprehensive summary of all findings and give the report a final polish, ensuring clear recommendations and overall readiness status.

## MANDATORY EXECUTION RULES (READ FIRST):

### Universal Rules:

- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 📖 You are at the final step - complete the assessment
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`

### Role Reinforcement:

- ✅ You are delivering the FINAL ASSESSMENT
- ✅ Your findings are objective and backed by evidence
- ✅ Provide clear, actionable recommendations
- ✅ Success is measured by value of findings

### Step-Specific Rules:

- 🎯 Compile and summarize all findings
- 🚫 Don't soften the message - be direct
- 💬 Provide specific examples for problems
- 🚪 Add final section to the report

## EXECUTION PROTOCOLS:

- 🎯 Review all findings from previous steps
- 💾 Add summary and recommendations
- 📖 Determine overall readiness status
- 🚫 Complete and present final report

## FINAL ASSESSMENT PROCESS:

### 1. Initialize Final Assessment

"Completing **Final Assessment**.

I will now:

1. Review all findings from previous steps
2. Provide a comprehensive summary
3. Add specific recommendations
4. Determine overall readiness status"

### 2. Review Previous Findings

Check the {outputFile} for sections added by previous steps:

- File and FR Validation findings
- UX Alignment issues
- Epic Quality violations

### 3. Add Final Assessment Section

Append to {outputFile}:

```markdown
## Summary and Recommendations

### Overall Readiness Status

[READY/NEEDS WORK/NOT READY]

### Critical Issues Requiring Immediate Action

[List most critical issues that must be addressed]

### Recommended Next Steps

1. [Specific action item 1]
2. [Specific action item 2]
3. [Specific action item 3]

### Final Note

This assessment identified [X] issues across [Y] categories. Address the critical issues before proceeding to implementation. These findings can be used to improve the artifacts or you may choose to proceed as-is.
```

### 4. Complete the Report

- Ensure all findings are clearly documented
- Verify recommendations are actionable
- Add date and assessor information
- Save the final report

### 5. Present Completion

Display:
"**Implementation Readiness Assessment Complete**

Report generated: {outputFile}

The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations."

## WORKFLOW COMPLETE

The implementation readiness workflow is now complete. The report contains all findings and recommendations for the user to consider.

Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` with argument `implementation readiness`.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:

- All findings compiled and summarized
- Clear recommendations provided
- Readiness status determined
- Final report saved

### ❌ SYSTEM FAILURE:

- Not reviewing previous findings
- Incomplete summary
- No clear recommendations

-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`


All 7 edits done. Task 8 — validation:


No matches found


Zero remaining instances. Implementation complete. Loading Step 4.


     1→---
     2→name: 'step-04-review'
     3→description: 'Adversarial review, classify findings, optional spec loop'
     4→
     5→adversarial_review_task: '{project-root}/_bmad/core/tasks/review-adversarial-general.xml'
     6→deferred_findings_file: '{output_dir}/deferred-findings.md'
     7→specLoopCap: 5
     8→---
     9→
    10→# Step 4: Review
    11→
    12→**Step 4 of 5 — Autonomous**
    13→
    14→## RULES
    15→
    16→- Review subagents get NO conversation context.
    17→- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
    18→
    19→---
    20→
    21→## INSTRUCTIONS
    22→
    23→1. Review in context-free subagents: intent audit (skip for one-shot) + adversarial code review via `{adversarial_review_task}`.
    24→2. deduplicate and classify their findings as one of (in cascading order):
    25→- intent_gap - finding caused by the change and wouldn't happen if intent was clear,
    26→- bad_spec - all other findings caused by the change, including direct deviations from spec; the spec had to be clear enough to prevent that
    27→- patch - all other findings that are real and can be trivially fixed
    28→- defer - all other findings that are real or uncertain
    29→- reject - all other findings that are noise
    30→3. have intent_gap findings? Do not fantasize, ask the user.
    31→4. have bad_spec findings? See if any of them still stand after intent_gap findings are resolved. If yes, discard lower level findings, amend spec, re-implement, re-review. Max `{specLoopCap}` iterations.
    32→4. Auto-fix patches. Write deferred findings to `{deferred_findings_file}`. Forget about rejected findings. Commit.
    33→
    34→---
    35→
    36→## NEXT
    37→
    38→`{installed_path}/steps/step-05-present.md`
    39→

---
name: 'step-04-review'
description: 'Adversarial review, classify findings, optional spec loop'

adversarial_review_task: '{project-root}/_bmad/core/tasks/review-adversarial-general.xml'
deferred_findings_file: '{output_dir}/deferred-findings.md'
specLoopCap: 5
---

# Step 4: Review

**Step 4 of 5 — Autonomous**

## RULES

- Review subagents get NO conversation context.
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`

---

## INSTRUCTIONS

1. Review in context-free subagents: intent audit (skip for one-shot) + adversarial code review via `{adversarial_review_task}`.
2. deduplicate and classify their findings as one of (in cascading order):
- intent_gap - finding caused by the change and wouldn't happen if intent was clear,
- bad_spec - all other findings caused by the change, including direct deviations from spec; the spec had to be clear enough to prevent that
- patch - all other findings that are real and can be trivially fixed
- defer - all other findings that are real or uncertain
- reject - all other findings that are noise
3. have intent_gap findings? Do not fantasize, ask the user.
4. have bad_spec findings? See if any of them still stand after intent_gap findings are resolved. If yes, discard lower level findings, amend spec, re-implement, re-review. Max `{specLoopCap}` iterations.
4. Auto-fix patches. Write deferred findings to `{deferred_findings_file}`. Forget about rejected findings. Commit.

---

## NEXT

`{installed_path}/steps/step-05-present.md`


Step 4 says to run adversarial review in context-free subagents. Let me run the adversarial code review. For this I need to get the diff and send it to a subagent with the adversarial review task.

Let me first get the diff, then find and load the adversarial review task file.


Step 4: Review. Let me get the diff and run the adversarial code review in a context-free subagent.


Bash

git -C /Users/alex/src/bmad/quick-flow-redesign diff HEAD

Get the full diff for review


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
index 82573286..9e0955b7 100644
--- 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
@@ -128,7 +128,7 @@ Recap that the brief captures everything needed to guide subsequent product deve

 ### 5. Suggest next steps

-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 b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
index 266bf06e..9f88be6e 100644
--- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
+++ b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md
@@ -87,7 +87,7 @@ Offer validation workflows to ensure PRD is ready for implementation:

 ### 4. Suggest Next Workflows

-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`

 ### 5. Final Completion Confirmation

diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
index 24e0c7de..46c98f7f 100644
--- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
+++ b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
@@ -197,7 +197,7 @@ Display:
 - **IF X (Exit):**
   - Display: "**Validation Report Saved:** {validationReportPath}"
   - Display: "**Summary:** {overall status} - {recommendation}"
-  - 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`

 - **IF Any other:** Help user, then redisplay menu

diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
index ff226824..62a02cf4 100644
--- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
+++ b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
@@ -82,7 +82,7 @@ Update the main workflow status file:

 ### 3. Suggest Next Steps

-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`

 ### 5. Final Completion Confirmation

diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
index 199b48a2..fe80fc23 100644
--- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
+++ b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
@@ -109,7 +109,7 @@ The assessment found [number] issues requiring attention. Review the detailed re

 The implementation readiness workflow is now complete. The report contains all findings and recommendations for the user to consider.

-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 b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
index 791c1777..f44850b2 100644
--- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
+++ b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
@@ -41,7 +41,7 @@ completedAt: '{{current_date}}'

 ### 3. Next Steps Guidance

-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`

 Upon Completion of task output: offer to answer any questions about the Architecture Document.

diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
index dc504182..4ee791a7 100644
--- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
+++ b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
@@ -144,6 +144,6 @@ If all validations pass:

 When C is selected, the workflow is complete and the epics.md is ready for development.

-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`

 Upon Completion of task output: offer to answer any questions about the Epics and Stories.
diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-01-clarify-and-route.md b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-01-clarify-and-route.md
index 55f7124a..5f396ee0 100644
--- a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-01-clarify-and-route.md
+++ b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-01-clarify-and-route.md
@@ -24,13 +24,12 @@ wipFile: '{implementation_artifacts}/tech-spec-wip.md'

 ## INSTRUCTIONS

-1. Clarify intent until: problem unambiguous, scope clear, no contradictions, you can explain back what you'll do.
-2. Backfill VC conventions to project-context if unknown.
-3. Route:
+1. Clarify intent. Do not fantasize, do not leave open questions Keep asking the human until clear enough to implement.
+2. Route:
    - **One-shot** — trivial (~3 files). `{execution_mode}` = "one-shot". → Step 3.
    - **Plan-code-review** — normal. → Step 2.
    - **Full BMM** — too big. Recommend and exit.
-   - Ambiguous? Default plan-code-review.
+   - Ambiguous? Default to plan-code-review.

 ---

diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-02-plan.md b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-02-plan.md
index 7875d2fb..5be849f3 100644
--- a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-02-plan.md
+++ b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-02-plan.md
@@ -2,7 +2,8 @@
 name: 'step-02-plan'
 description: 'Investigate, generate spec, present for approval'

-wipFile: '{implementation_artifacts}/tech-spec-wip.md'
+slug: kebab-cased strings are valid as a file name, based on the intent
+wipFile: '{implementation_artifacts}/tech-spec-[slug].md'
 templateFile: '{installed_path}/tech-spec-template.md'
 ---

@@ -20,8 +21,9 @@ templateFile: '{installed_path}/tech-spec-template.md'
 ## INSTRUCTIONS

 1. Investigate codebase.
-2. Generate spec from `{templateFile}` → `{wipFile}`.
+2. Generate spec from `{templateFile}` into `{wipFile}`.
 3. Self-review against READY FOR DEVELOPMENT standard.
+4. If intent gaps exist, do not fantasize, do not leave open questions, ask the human.

 ### CHECKPOINT 1

diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-03-implement.md b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-03-implement.md
index a8eb0a26..c2cc3685 100644
--- a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-03-implement.md
+++ b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-03-implement.md
@@ -1,9 +1,6 @@
 ---
 name: 'step-03-implement'
 description: 'Branch, shard tasks, execute, commit. Local only.'
-
-tasksDir: '{implementation_artifacts}/tasks'
-sequenceFile: '{implementation_artifacts}/tasks/sequence.md'
 ---

 # Step 3: Implement
@@ -20,14 +17,8 @@ sequenceFile: '{implementation_artifacts}/tasks/sequence.md'

 ## INSTRUCTIONS

-1. Baseline commit. Branch. Assert clean tree.
-2. Shard spec tasks → `{tasksDir}/task-NN.md`. Track in `{sequenceFile}`.
-3. Execute sequentially: read task fresh → implement → verify AC → mark complete → next.
-4. Self-check. Commit.
-
-One-shot: skip sharding, work from mental plan.
-
-Halt after 3 failures on same task, or blocking ambiguity.
+Implement the spec.
+One-shot: implement the intent.

 ---

diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-04-review.md b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-04-review.md
index 779696a2..b751cd98 100644
--- a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-04-review.md
+++ b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-04-review.md
@@ -3,6 +3,7 @@ name: 'step-04-review'
 description: 'Adversarial review, classify findings, optional spec loop'

 adversarial_review_task: '{project-root}/_bmad/core/tasks/review-adversarial-general.xml'
+deferred_findings_file: '{output_dir}/deferred-findings.md'
 specLoopCap: 5
 ---

@@ -19,10 +20,16 @@ specLoopCap: 5

 ## INSTRUCTIONS

-1. Diff from `{baseline_commit}`. Review in context-free subagents: intent audit (skip for one-shot) + adversarial code review via `{adversarial_review_task}`.
-2. Classify findings: intent > spec > patch > defer > reject.
-3. Spec-class? Amend spec, re-derive, re-review. Max `{specLoopCap}` iterations.
-4. Auto-fix patches. Commit.
+1. Review in context-free subagents: intent audit (skip for one-shot) + adversarial code review via `{adversarial_review_task}`.
+2. deduplicate and classify their findings as one of (in cascading order):
+- intent_gap - finding caused by the change and wouldn't happen if intent was clear,
+- bad_spec - all other findings caused by the change, including direct deviations from spec; the spec had to be clear enough to prevent that
+- patch - all other findings that are real and can be trivially fixed
+- defer - all other findings that are real or uncertain
+- reject - all other findings that are noise
+3. have intent_gap findings? Do not fantasize, ask the user.
+4. have bad_spec findings? See if any of them still stand after intent_gap findings are resolved. If yes, discard lower level findings, amend spec, re-implement, re-review. Max `{specLoopCap}` iterations.
+4. Auto-fix patches. Write deferred findings to `{deferred_findings_file}`. Forget about rejected findings. Commit.

 ---

diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-05-present.md b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-05-present.md
index 385998f0..1f515e8c 100644
--- a/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-05-present.md
+++ b/src/bmm/workflows/bmad-quick-flow/quick-dev2/steps/step-05-present.md
@@ -16,11 +16,7 @@ description: 'Present findings, get approval, create PR'

 ## INSTRUCTIONS

-Present classified findings. `[A] Approve  [E] Edit  [R] Reject`. HALT.
-
-- **A**: Commit patches. Print push command. Wait. Create PR.
-- **E**: Apply changes, re-present.
-- **R**: Route back.
+Display summary of your work to the user. Advice on how to review the changes. Offer to make a plan for manual testing, or to push and/or create a pull request.

 ---