     1→=== /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md ===
     2→---
     3→name: 'step-06-complete'
     4→description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'
     5→
     6→# File References
     7→outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
     8→---
     9→
    10→# Step 6: Product Brief Completion
    11→
    12→## STEP GOAL:
    13→
    14→Complete the product brief workflow, update status files, and provide guidance on logical next steps for continued product development.
    15→
    16→## MANDATORY EXECUTION RULES (READ FIRST):
    17→
    18→### Universal Rules:
    19→
    20→- 🛑 NEVER generate content without user input
    21→- 📖 CRITICAL: Read the complete step file before taking any action
    22→- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
    23→- 📋 YOU ARE A FACILITATOR, not a content generator
    24→- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
    25→
    26→### Role Reinforcement:
    27→
    28→- ✅ You are a product-focused Business Analyst facilitator
    29→- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
    30→- ✅ We engage in collaborative dialogue, not command-response
    31→- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
    32→- ✅ Maintain collaborative completion tone throughout
    33→
    34→### Step-Specific Rules:
    35→
    36→- 🎯 Focus only on completion, next steps, and project guidance
    37→- 🚫 FORBIDDEN to generate new content for the product brief
    38→- 💬 Approach: Systematic completion with quality validation and next step recommendations
    39→- 📋 FINALIZE document and update workflow status appropriately
    40→
    41→## EXECUTION PROTOCOLS:
    42→
    43→- 🎯 Show your analysis before taking any action
    44→- 💾 Update the main workflow status file with completion information
    45→- 📖 Suggest potential next workflow steps for the user
    46→- 🚫 DO NOT load additional steps after this one (this is final)
    47→
    48→## CONTEXT BOUNDARIES:
    49→
    50→- Available context: Complete product brief document from all previous steps, workflow frontmatter shows all completed steps
    51→- Focus: Completion validation, status updates, and next step guidance
    52→- Limits: No new content generation, only completion and wrap-up activities
    53→- Dependencies: All previous steps must be completed with content saved to document
    54→
    55→## Sequence of Instructions (Do not deviate, skip, or optimize)
    56→
    57→### 1. Announce Workflow Completion
    58→
    59→**Completion Announcement:**
    60→"🎉 **Product Brief Complete, {{user_name}}!**
    61→
    62→I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
    63→
    64→**What we've accomplished:**
    65→
    66→- ✅ Executive Summary with clear vision and problem statement
    67→- ✅ Core Vision with solution definition and unique differentiators
    68→- ✅ Target Users with rich personas and user journeys
    69→- ✅ Success Metrics with measurable outcomes and business objectives
    70→- ✅ MVP Scope with focused feature set and clear boundaries
    71→- ✅ Future Vision that inspires while maintaining current focus
    72→
    73→**The complete Product Brief is now available at:** `{outputFile}`
    74→
    75→This brief serves as the foundation for all subsequent product development activities and strategic decisions."
    76→
    77→### 2. Document Quality Check
    78→
    79→**Completeness Validation:**
    80→Perform final validation of the product brief:
    81→
    82→- Does the executive summary clearly communicate the vision and problem?
    83→- Are target users well-defined with compelling personas?
    84→- Do success metrics connect user value to business objectives?
    85→- Is MVP scope focused and realistic?
    86→- Does the brief provide clear direction for next steps?
    87→
    88→**Consistency Validation:**
    89→
    90→- Do all sections align with the core problem statement?
    91→- Is user value consistently emphasized throughout?
    92→- Are success criteria traceable to user needs and business goals?
    93→- Does MVP scope align with the problem and solution?
    94→
    95→### 3. Suggest Next Steps
    96→
    97→**Recommended Next Workflow:**
    98→Provide guidance on logical next workflows:
    99→
   100→1. `create-prd` - Create detailed Product Requirements Document
   101→   - Brief provides foundation for detailed requirements
   102→   - User personas inform journey mapping
   103→   - Success metrics become specific acceptance criteria
   104→   - MVP scope becomes detailed feature specifications
   105→
   106→**Other Potential Next Steps:**
   107→
   108→1. `create-ux-design` - UX research and design (can run parallel with PRD)
   109→2. `domain-research` - Deep market or domain research (if needed)
   110→
   111→**Strategic Considerations:**
   112→
   113→- The PRD workflow builds directly on this brief for detailed planning
   114→- Consider team capacity and immediate priorities
   115→- Use brief to validate concept before committing to detailed work
   116→- Brief can guide early technical feasibility discussions
   117→
   118→### 4. Congrats to the user
   119→
   120→"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**"
   121→
   122→Recap that the brief captures everything needed to guide subsequent product development:
   123→
   124→- Clear vision and problem definition
   125→- Deep understanding of target users
   126→- Measurable success criteria
   127→- Focused MVP scope with realistic boundaries
   128→- Inspiring long-term vision
   129→
   130→### 5. Suggest next steps
   131→
   132→Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
   133→
   134→---
   135→
   136→## 🚨 SYSTEM SUCCESS/FAILURE METRICS
   137→
   138→### ✅ SUCCESS:
   139→
   140→- Product brief contains all essential sections with collaborative content
   141→- All collaborative content properly saved to document with proper frontmatter
   142→- Workflow status file updated with completion information and timestamp
   143→- Clear next step guidance provided to user with specific workflow recommendations
   144→- Document quality validation completed with completeness and consistency checks
   145→- User acknowledges completion and understands next available options
   146→- Workflow properly marked as complete in status tracking
   147→
   148→### ❌ SYSTEM FAILURE:
   149→
   150→- Not updating workflow status file with completion information
   151→- Missing clear next step guidance for user
   152→- Not confirming document completeness with user
   153→- Workflow not properly marked as complete in status tracking
   154→- User unclear about what happens next or available options
   155→- Document quality issues not identified or addressed
   156→
   157→**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
   158→
   159→## FINAL WORKFLOW COMPLETION
   160→
   161→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.
   162→
   163→**Congratulations on completing the Product Brief for {{project_name}}!** 🎉
   164→
   165→=== /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md ===
   166→---
   167→name: 'step-12-complete'
   168→description: 'Complete the PRD workflow, update status files, and suggest next steps including validation'
   169→
   170→# File References
   171→outputFile: '{planning_artifacts}/prd.md'
   172→validationFlow: '../steps-v/step-v-01-discovery.md'
   173→---
   174→
   175→# Step 12: Workflow Completion
   176→
   177→**Final Step - Complete the PRD**
   178→
   179→## MANDATORY EXECUTION RULES (READ FIRST):
   180→
   181→- ✅ THIS IS A FINAL STEP - Workflow completion required
   182→- 📖 CRITICAL: ALWAYS read the complete step file before taking any action
   183→- 🛑 NO content generation - this is a wrap-up step
   184→- 📋 FINALIZE document and update workflow status
   185→- 💬 FOCUS on completion, validation options, and next steps
   186→- 🎯 UPDATE workflow status files with completion information
   187→- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
   188→
   189→## EXECUTION PROTOCOLS:
   190→
   191→- 🎯 Show your analysis before taking any action
   192→- 💾 Update the main workflow status file with completion information (if exists)
   193→- 📖 Offer validation workflow options to user
   194→- 🚫 DO NOT load additional steps after this one
   195→
   196→## TERMINATION STEP PROTOCOLS:
   197→
   198→- This is a FINAL step - workflow completion required
   199→- Update workflow status file with finalized document
   200→- Suggest validation and next workflow steps
   201→- Mark workflow as complete in status tracking
   202→
   203→## CONTEXT BOUNDARIES:
   204→
   205→- Complete and polished PRD document is available from all previous steps
   206→- Workflow frontmatter shows all completed steps including polish
   207→- All collaborative content has been generated, saved, and optimized
   208→- Focus on completion, validation options, and next steps
   209→
   210→## YOUR TASK:
   211→
   212→Complete the PRD workflow, update status files, offer validation options, and suggest next steps for the project.
   213→
   214→## WORKFLOW COMPLETION SEQUENCE:
   215→
   216→### 1. Announce Workflow Completion
   217→
   218→Inform user that the PRD is complete and polished:
   219→- Celebrate successful completion of comprehensive PRD
   220→- Summarize all sections that were created
   221→- Highlight that document has been polished for flow and coherence
   222→- Emphasize document is ready for downstream work
   223→
   224→### 2. Workflow Status Update
   225→
   226→Update the main workflow status file if there is one:
   227→
   228→- Load `{status_file}` from workflow configuration (if exists)
   229→- Update workflow_status["prd"] = "{default_output_file}"
   230→- Save file, preserving all comments and structure
   231→- Mark current timestamp as completion time
   232→
   233→### 3. Validation Workflow Options
   234→
   235→Offer validation workflows to ensure PRD is ready for implementation:
   236→
   237→**Available Validation Workflows:**
   238→
   239→**Option 1: Check Implementation Readiness** (`{checkImplementationReadinessWorkflow}`)
   240→- Validates PRD has all information needed for development
   241→- Checks epic coverage completeness
   242→- Reviews UX alignment with requirements
   243→- Assesses epic quality and readiness
   244→- Identifies gaps before architecture/design work begins
   245→
   246→**When to use:** Before starting technical architecture or epic breakdown
   247→
   248→**Option 2: Skip for Now**
   249→- Proceed directly to next workflows (architecture, UX, epics)
   250→- Validation can be done later if needed
   251→- Some teams prefer to validate during architecture reviews
   252→
   253→### 4. Suggest Next Workflows
   254→
   255→PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
   256→
   257→### 5. Final Completion Confirmation
   258→
   259→- Confirm completion with user and summarize what has been accomplished
   260→- 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
   261→- Ask if they'd like to run validation workflow or proceed to next workflows
   262→
   263→## SUCCESS METRICS:
   264→
   265→✅ PRD document contains all required sections and has been polished
   266→✅ All collaborative content properly saved and optimized
   267→✅ Workflow status file updated with completion information (if exists)
   268→✅ Validation workflow options clearly presented
   269→✅ Clear next step guidance provided to user
   270→✅ Document quality validation completed
   271→✅ User acknowledges completion and understands next options
   272→
   273→## FAILURE MODES:
   274→
   275→❌ Not updating workflow status file with completion information (if exists)
   276→❌ Not offering validation workflow options
   277→❌ Missing clear next step guidance for user
   278→❌ Not confirming document completeness with user
   279→❌ Workflow not properly marked as complete in status tracking (if applicable)
   280→❌ User unclear about what happens next or what validation options exist
   281→
   282→❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
   283→❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
   284→
   285→## FINAL REMINDER to give the user:
   286→
   287→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.
   288→
   289→**Congratulations on completing the Product Requirements Document for {{project_name}}!** 🎉
   290→
   291→=== /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md ===
   292→---
   293→name: 'step-e-04-complete'
   294→description: 'Complete & Validate - Present options for next steps including full validation'
   295→
   296→# File references (ONLY variables used in this step)
   297→prdFile: '{prd_file_path}'
   298→validationWorkflow: '../steps-v/step-v-01-discovery.md'
   299→---
   300→
   301→# Step E-4: Complete & Validate
   302→
   303→## STEP GOAL:
   304→
   305→Present summary of completed edits and offer next steps including seamless integration with validation workflow.
   306→
   307→## MANDATORY EXECUTION RULES (READ FIRST):
   308→
   309→### Universal Rules:
   310→
   311→- 🛑 ALWAYS generate content WITH user input/approval
   312→- 📖 CRITICAL: Read the complete step file before taking any action
   313→- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
   314→- 📋 YOU ARE A FACILITATOR, not a content generator
   315→- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
   316→
   317→### Role Reinforcement:
   318→
   319→- ✅ You are a Validation Architect and PRD Improvement Specialist
   320→- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
   321→- ✅ We engage in collaborative dialogue, not command-response
   322→- ✅ You bring synthesis and summary expertise
   323→- ✅ User chooses next actions
   324→
   325→### Step-Specific Rules:
   326→
   327→- 🎯 Focus ONLY on presenting summary and options
   328→- 🚫 FORBIDDEN to make additional changes
   329→- 💬 Approach: Clear, concise summary with actionable options
   330→- 🚪 This is the final edit step - no more edits
   331→
   332→## EXECUTION PROTOCOLS:
   333→
   334→- 🎯 Compile summary of all changes made
   335→- 🎯 Present options clearly with expected outcomes
   336→- 📖 Route to validation if user chooses
   337→- 🚫 FORBIDDEN to proceed without user selection
   338→
   339→## CONTEXT BOUNDARIES:
   340→
   341→- Available context: Updated PRD file, edit history from step e-03
   342→- Focus: Summary and options only (no more editing)
   343→- Limits: Don't make changes, just present options
   344→- Dependencies: Step e-03 completed - all edits applied
   345→
   346→## MANDATORY SEQUENCE
   347→
   348→**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
   349→
   350→### 1. Compile Edit Summary
   351→
   352→From step e-03 change execution, compile:
   353→
   354→**Changes Made:**
   355→- Sections added: {list with names}
   356→- Sections updated: {list with names}
   357→- Content removed: {list}
   358→- Structure changes: {description}
   359→
   360→**Edit Details:**
   361→- Total sections affected: {count}
   362→- Mode: {restructure/targeted/both}
   363→- Priority addressed: {Critical/High/Medium/Low}
   364→
   365→**PRD Status:**
   366→- Format: {BMAD Standard / BMAD Variant / Legacy (converted)}
   367→- Completeness: {assessment}
   368→- Ready for: {downstream use cases}
   369→
   370→### 2. Present Completion Summary
   371→
   372→Display:
   373→
   374→"**✓ PRD Edit Complete**
   375→
   376→**Updated PRD:** {prd_file_path}
   377→
   378→**Changes Summary:**
   379→{Present bulleted list of major changes}
   380→
   381→**Edit Mode:** {mode}
   382→**Sections Modified:** {count}
   383→
   384→**PRD Format:** {format}
   385→
   386→**PRD is now ready for:**
   387→- Downstream workflows (UX Design, Architecture)
   388→- Validation to ensure quality
   389→- Production use
   390→
   391→**What would you like to do next?**"
   392→
   393→### 3. Present MENU OPTIONS
   394→
   395→Display:
   396→
   397→**[V] Run Full Validation** - Execute complete validation workflow (steps-v) to verify PRD quality
   398→**[E] Edit More** - Make additional edits to the PRD
   399→**[S] Summary** - End with detailed summary of changes
   400→**[X] Exit** - Exit edit workflow
   401→
   402→#### EXECUTION RULES:
   403→
   404→- ALWAYS halt and wait for user input
   405→- Only proceed based on user selection
   406→
   407→#### Menu Handling Logic:
   408→
   409→- **IF V (Run Full Validation):**
   410→  - Display: "**Starting Validation Workflow**"
   411→  - Display: "This will run all 13 validation checks on the updated PRD."
   412→  - Display: "Preparing to validate: {prd_file_path}"
   413→  - Display: "**Proceeding to validation...**"
   414→  - Read fully and follow: {validationWorkflow} (steps-v/step-v-01-discovery.md)
   415→  - Note: This hands off to the validation workflow which will run its complete 13-step process
   416→
   417→- **IF E (Edit More):**
   418→  - Display: "**Additional Edits**"
   419→  - Ask: "What additional edits would you like to make?"
   420→  - Accept input, then display: "**Returning to edit step...**"
   421→  - Read fully and follow: step-e-03-edit.md again
   422→
   423→- **IF S (Summary):**
   424→  - Display detailed summary including:
   425→    - Complete list of all changes made
   426→    - Before/after comparison (key improvements)
   427→    - Recommendations for next steps
   428→  - Display: "**Edit Workflow Complete**"
   429→  - Exit
   430→
   431→- **IF X (Exit):**
   432→  - Display summary
   433→  - Display: "**Edit Workflow Complete**"
   434→  - Exit
   435→
   436→- **IF Any other:** Help user, then redisplay menu
   437→
   438→---
   439→
   440→## 🚨 SYSTEM SUCCESS/FAILURE METRICS
   441→
   442→### ✅ SUCCESS:
   443→
   444→- Complete edit summary compiled accurately
   445→- All changes clearly documented
   446→- Options presented with clear expectations
   447→- Validation option seamlessly integrates with steps-v workflow
   448→- User can validate, edit more, or exit
   449→- Clean handoff to validation workflow (if chosen)
   450→- Edit workflow completes properly
   451→
   452→### ❌ SYSTEM FAILURE:
   453→
   454→- Missing changes in summary
   455→- Not offering validation option
   456→- Not documenting completion properly
   457→- No clear handoff to validation workflow
   458→
   459→**Master Rule:** Edit workflow seamlessly integrates with validation. User can edit → validate → edit again → validate again in iterative improvement cycle.
   460→
   461→=== /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md ===
   462→---
   463→name: 'step-v-13-report-complete'
   464→description: 'Validation Report Complete - Finalize report, summarize findings, present to user, offer next steps'
   465→
   466→# File references (ONLY variables used in this step)
   467→validationReportPath: '{validation_report_path}'
   468→prdFile: '{prd_file_path}'
   469→---
   470→
   471→# Step 13: Validation Report Complete
   472→
   473→## STEP GOAL:
   474→
   475→Finalize validation report, summarize all findings from steps 1-12, present summary to user conversationally, and offer actionable next steps.
   476→
   477→## MANDATORY EXECUTION RULES (READ FIRST):
   478→
   479→### Universal Rules:
   480→
   481→- 🛑 NEVER generate content without user input
   482→- 📖 CRITICAL: Read the complete step file before taking any action
   483→- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
   484→- 📋 YOU ARE A FACILITATOR, not a content generator
   485→- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
   486→
   487→### Role Reinforcement:
   488→
   489→- ✅ You are a Validation Architect and Quality Assurance Specialist
   490→- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
   491→- ✅ We engage in collaborative dialogue, not command-response
   492→- ✅ You bring synthesis and summary expertise
   493→- ✅ This is the FINAL step - requires user interaction
   494→
   495→### Step-Specific Rules:
   496→
   497→- 🎯 Focus ONLY on summarizing findings and presenting options
   498→- 🚫 FORBIDDEN to perform additional validation
   499→- 💬 Approach: Conversational summary with clear next steps
   500→- 🚪 This is the final step - no next step after this
   501→
   502→## EXECUTION PROTOCOLS:
   503→
   504→- 🎯 Load complete validation report
   505→- 🎯 Summarize all findings from steps 1-12
   506→- 🎯 Update report frontmatter with final status
   507→- 💬 Present summary to user conversationally
   508→- 💬 Offer menu options for next actions
   509→- 🚫 FORBIDDEN to proceed without user selection
   510→
   511→## CONTEXT BOUNDARIES:
   512→
   513→- Available context: Complete validation report with findings from all validation steps
   514→- Focus: Summary and presentation only (no new validation)
   515→- Limits: Don't add new findings, just synthesize existing
   516→- Dependencies: Steps 1-12 completed - all validation checks done
   517→
   518→## MANDATORY SEQUENCE
   519→
   520→**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
   521→
   522→### 1. Load Complete Validation Report
   523→
   524→Read the entire validation report from {validationReportPath}
   525→
   526→Extract all findings from:
   527→- Format Detection (Step 2)
   528→- Parity Analysis (Step 2B, if applicable)
   529→- Information Density (Step 3)
   530→- Product Brief Coverage (Step 4)
   531→- Measurability (Step 5)
   532→- Traceability (Step 6)
   533→- Implementation Leakage (Step 7)
   534→- Domain Compliance (Step 8)
   535→- Project-Type Compliance (Step 9)
   536→- SMART Requirements (Step 10)
   537→- Holistic Quality (Step 11)
   538→- Completeness (Step 12)
   539→
   540→### 2. Update Report Frontmatter with Final Status
   541→
   542→Update validation report frontmatter:
   543→
   544→```yaml
   545→---
   546→validationTarget: '{prd_path}'
   547→validationDate: '{current_date}'
   548→inputDocuments: [list of documents]
   549→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']
   550→validationStatus: COMPLETE
   551→holisticQualityRating: '{rating from step 11}'
   552→overallStatus: '{Pass/Warning/Critical based on all findings}'
   553→---
   554→```
   555→
   556→### 3. Create Summary of Findings
   557→
   558→**Overall Status:**
   559→- Determine from all validation findings
   560→- **Pass:** All critical checks pass, minor warnings acceptable
   561→- **Warning:** Some issues found but PRD is usable
   562→- **Critical:** Major issues that prevent PRD from being fit for purpose
   563→
   564→**Quick Results Table:**
   565→- Format: [classification]
   566→- Information Density: [severity]
   567→- Measurability: [severity]
   568→- Traceability: [severity]
   569→- Implementation Leakage: [severity]
   570→- Domain Compliance: [status]
   571→- Project-Type Compliance: [compliance score]
   572→- SMART Quality: [percentage]
   573→- Holistic Quality: [rating/5]
   574→- Completeness: [percentage]
   575→
   576→**Critical Issues:** List from all validation steps
   577→**Warnings:** List from all validation steps
   578→**Strengths:** List positives from all validation steps
   579→
   580→**Holistic Quality Rating:** From step 11
   581→**Top 3 Improvements:** From step 11
   582→
   583→**Recommendation:** Based on overall status
   584→
   585→### 4. Present Summary to User Conversationally
   586→
   587→Display:
   588→
   589→"**✓ PRD Validation Complete**
   590→
   591→**Overall Status:** {Pass/Warning/Critical}
   592→
   593→**Quick Results:**
   594→{Present quick results table with key findings}
   595→
   596→**Critical Issues:** {count or "None"}
   597→{If any, list briefly}
   598→
   599→**Warnings:** {count or "None"}
   600→{If any, list briefly}
   601→
   602→**Strengths:**
   603→{List key strengths}
   604→
   605→**Holistic Quality:** {rating}/5 - {label}
   606→
   607→**Top 3 Improvements:**
   608→1. {Improvement 1}
   609→2. {Improvement 2}
   610→3. {Improvement 3}
   611→
   612→**Recommendation:**
   613→{Based on overall status:
   614→- Pass: "PRD is in good shape. Address minor improvements to make it great."
   615→- Warning: "PRD is usable but has issues that should be addressed. Review warnings and improve where needed."
   616→- Critical: "PRD has significant issues that should be fixed before use. Focus on critical issues above."}
   617→
   618→**What would you like to do next?**"
   619→
   620→### 5. Present MENU OPTIONS
   621→
   622→Display:
   623→
   624→**[R] Review Detailed Findings** - Walk through validation report section by section
   625→**[E] Use Edit Workflow** - Use validation report with Edit workflow for systematic improvements
   626→**[F] Fix Simpler Items** - Immediate fixes for simple issues (anti-patterns, leakage, missing headers)
   627→**[X] Exit** - Exit and Suggest Next Steps.
   628→
   629→#### EXECUTION RULES:
   630→
   631→- ALWAYS halt and wait for user input after presenting menu
   632→- Only proceed based on user selection
   633→
   634→#### Menu Handling Logic:
   635→
   636→- **IF R (Review Detailed Findings):**
   637→  - Walk through validation report section by section
   638→  - Present findings from each validation step
   639→  - Allow user to ask questions
   640→  - After review, return to menu
   641→
   642→- **IF E (Use Edit Workflow):**
   643→  - 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."
   644→  - Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
   645→  - If yes: Read fully and follow: steps-e/step-e-01-discovery.md
   646→  - If no: Return to menu
   647→
   648→- **IF F (Fix Simpler Items):**
   649→  - Offer immediate fixes for:
   650→    - Template variables (fill in with appropriate content)
   651→    - Conversational filler (remove wordy phrases)
   652→    - Implementation leakage (remove technology names from FRs/NFRs)
   653→    - Missing section headers (add ## headers)
   654→  - Ask: "Which simple fixes would you like me to make?"
   655→  - If user specifies fixes, make them and update validation report
   656→  - Return to menu
   657→
   658→- **IF X (Exit):**
   659→  - Display: "**Validation Report Saved:** {validationReportPath}"
   660→  - Display: "**Summary:** {overall status} - {recommendation}"
   661→  - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
   662→
   663→- **IF Any other:** Help user, then redisplay menu
   664→
   665→---
   666→
   667→## 🚨 SYSTEM SUCCESS/FAILURE METRICS
   668→
   669→### ✅ SUCCESS:
   670→
   671→- Complete validation report loaded successfully
   672→- All findings from steps 1-12 summarized
   673→- Report frontmatter updated with final status
   674→- Overall status determined correctly (Pass/Warning/Critical)
   675→- Quick results table presented
   676→- Critical issues, warnings, and strengths listed
   677→- Holistic quality rating included
   678→- Top 3 improvements presented
   679→- Clear recommendation provided
   680→- Menu options presented with clear explanations
   681→- User can review findings, get help, or exit
   682→
   683→### ❌ SYSTEM FAILURE:
   684→
   685→- Not loading complete validation report
   686→- Missing summary of findings
   687→- Not updating report frontmatter
   688→- Not determining overall status
   689→- Missing menu options
   690→- Unclear next steps
   691→
   692→**Master Rule:** User needs clear summary and actionable next steps. Edit workflow is best for complex issues; immediate fixes available for simpler ones.
   693→
   694→=== /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md ===
   695→# Step 14: Workflow Completion
   696→
   697→## MANDATORY EXECUTION RULES (READ FIRST):
   698→
   699→- ✅ THIS IS A FINAL STEP - Workflow completion required
   700→
   701→- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
   702→- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
   703→- 🛑 NO content generation - this is a wrap-up step
   704→- 📋 FINALIZE document and update workflow status
   705→- 💬 FOCUS on completion, validation, and next steps
   706→- 🎯 UPDATE workflow status files with completion information
   707→- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
   708→
   709→## EXECUTION PROTOCOLS:
   710→
   711→- 🎯 Show your analysis before taking any action
   712→- 💾 Update the main workflow status file with completion information
   713→- 📖 Suggest potential next workflow steps for the user
   714→- 🚫 DO NOT load additional steps after this one
   715→
   716→## TERMINATION STEP PROTOCOLS:
   717→
   718→- This is a FINAL step - workflow completion required
   719→- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted to indicate all is finished..
   720→- Output completion summary and next step guidance
   721→- Update the main workflow status file with finalized document
   722→- Suggest potential next workflow steps for the user
   723→- Mark workflow as complete in status tracking
   724→
   725→## CONTEXT BOUNDARIES:
   726→
   727→- Complete UX design specification is available from all previous steps
   728→- Workflow frontmatter shows all completed steps
   729→- All collaborative content has been generated and saved
   730→- Focus on completion, validation, and next steps
   731→
   732→## YOUR TASK:
   733→
   734→Complete the UX design workflow, update status files, and suggest next steps for the project.
   735→
   736→## WORKFLOW COMPLETION SEQUENCE:
   737→
   738→### 1. Announce Workflow Completion
   739→
   740→Inform user that the UX design is complete:
   741→"🎉 **UX Design Complete, {{user_name}}!**
   742→
   743→I've successfully collaborated with you to create a comprehensive UX design specification for {{project_name}}.
   744→
   745→**What we've accomplished:**
   746→
   747→- ✅ Project understanding and user insights
   748→- ✅ Core experience and emotional response definition
   749→- ✅ UX pattern analysis and inspiration
   750→- ✅ Design system choice and implementation strategy
   751→- ✅ Core interaction definition and experience mechanics
   752→- ✅ Visual design foundation (colors, typography, spacing)
   753→- ✅ Design direction mockups and visual explorations
   754→- ✅ User journey flows and interaction design
   755→- ✅ Component strategy and custom component specifications
   756→- ✅ UX consistency patterns for common interactions
   757→- ✅ Responsive design and accessibility strategy
   758→
   759→**The complete UX design specification is now available at:** `{planning_artifacts}/ux-design-specification.md`
   760→
   761→**Supporting Visual Assets:**
   762→
   763→- Color themes visualizer: `{planning_artifacts}/ux-color-themes.html`
   764→- Design directions mockups: `{planning_artifacts}/ux-design-directions.html`
   765→
   766→This specification is now ready to guide visual design, implementation, and development."
   767→
   768→### 2. Workflow Status Update
   769→
   770→Update the main workflow status file:
   771→
   772→- Load `{status_file}` from workflow configuration (if exists)
   773→- Update workflow_status["create-ux-design"] = "{default_output_file}"
   774→- Save file, preserving all comments and structure
   775→- Mark current timestamp as completion time
   776→
   777→### 3. Suggest Next Steps
   778→
   779→UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
   780→
   781→### 5. Final Completion Confirmation
   782→
   783→Congratulate the user on the completion you both completed together of the UX.
   784→
   785→
   786→
   787→## SUCCESS METRICS:
   788→
   789→✅ UX design specification contains all required sections
   790→✅ All collaborative content properly saved to document
   791→✅ Workflow status file updated with completion information
   792→✅ Clear next step guidance provided to user
   793→✅ Document quality validation completed
   794→✅ User acknowledges completion and understands next options
   795→
   796→## FAILURE MODES:
   797→
   798→❌ Not updating workflow status file with completion information
   799→❌ Missing clear next step guidance for user
   800→❌ Not confirming document completeness with user
   801→❌ Workflow not properly marked as complete in status tracking
   802→❌ User unclear about what happens next
   803→
   804→❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
   805→❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
   806→❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
   807→
   808→## WORKFLOW COMPLETION CHECKLIST:
   809→
   810→### Design Specification Complete:
   811→
   812→- [ ] Executive summary and project understanding
   813→- [ ] Core experience and emotional response definition
   814→- [ ] UX pattern analysis and inspiration
   815→- [ ] Design system choice and strategy
   816→- [ ] Core interaction mechanics definition
   817→- [ ] Visual design foundation (colors, typography, spacing)
   818→- [ ] Design direction decisions and mockups
   819→- [ ] User journey flows and interaction design
   820→- [ ] Component strategy and specifications
   821→- [ ] UX consistency patterns documentation
   822→- [ ] Responsive design and accessibility strategy
   823→
   824→### Process Complete:
   825→
   826→- [ ] All steps completed with user confirmation
   827→- [ ] All content saved to specification document
   828→- [ ] Frontmatter properly updated with all steps
   829→- [ ] Workflow status file updated with completion
   830→- [ ] Next steps clearly communicated
   831→
   832→## NEXT STEPS GUIDANCE:
   833→
   834→**Immediate Options:**
   835→
   836→1. **Wireframe Generation** - Create low-fidelity layouts based on UX spec
   837→2. **Interactive Prototype** - Build clickable prototypes for testing
   838→3. **Solution Architecture** - Technical design with UX context
   839→4. **Figma Visual Design** - High-fidelity UI implementation
   840→5. **Epic Creation** - Break down UX requirements for development
   841→
   842→**Recommended Sequence:**
   843→For design-focused teams: Wireframes → Prototypes → Figma Design → Development
   844→For technical teams: Architecture → Epic Creation → Development
   845→
   846→Consider team capacity, timeline, and whether user validation is needed before implementation.
   847→
   848→## WORKFLOW FINALIZATION:
   849→
   850→- Set `lastStep = 14` in document frontmatter
   851→- Update workflow status file with completion timestamp
   852→- Provide completion summary to user
   853→- Do NOT load any additional steps
   854→
   855→## FINAL REMINDER:
   856→
   857→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.
   858→
   859→**Congratulations on completing the UX Design Specification for {{project_name}}!** 🎉
   860→
   861→**Core Deliverables:**
   862→
   863→- ✅ UX Design Specification: `{planning_artifacts}/ux-design-specification.md`
   864→- ✅ Color Themes Visualizer: `{planning_artifacts}/ux-color-themes.html`
   865→- ✅ Design Directions: `{planning_artifacts}/ux-design-directions.html`
   866→
   867→=== /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md ===
   868→---
   869→name: 'step-06-final-assessment'
   870→description: 'Compile final assessment and polish the readiness report'
   871→
   872→outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
   873→---
   874→
   875→# Step 6: Final Assessment
   876→
   877→## STEP GOAL:
   878→
   879→To provide a comprehensive summary of all findings and give the report a final polish, ensuring clear recommendations and overall readiness status.
   880→
   881→## MANDATORY EXECUTION RULES (READ FIRST):
   882→
   883→### Universal Rules:
   884→
   885→- 🛑 NEVER generate content without user input
   886→- 📖 CRITICAL: Read the complete step file before taking any action
   887→- 📖 You are at the final step - complete the assessment
   888→- 📋 YOU ARE A FACILITATOR, not a content generator
   889→- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
   890→
   891→### Role Reinforcement:
   892→
   893→- ✅ You are delivering the FINAL ASSESSMENT
   894→- ✅ Your findings are objective and backed by evidence
   895→- ✅ Provide clear, actionable recommendations
   896→- ✅ Success is measured by value of findings
   897→
   898→### Step-Specific Rules:
   899→
   900→- 🎯 Compile and summarize all findings
   901→- 🚫 Don't soften the message - be direct
   902→- 💬 Provide specific examples for problems
   903→- 🚪 Add final section to the report
   904→
   905→## EXECUTION PROTOCOLS:
   906→
   907→- 🎯 Review all findings from previous steps
   908→- 💾 Add summary and recommendations
   909→- 📖 Determine overall readiness status
   910→- 🚫 Complete and present final report
   911→
   912→## FINAL ASSESSMENT PROCESS:
   913→
   914→### 1. Initialize Final Assessment
   915→
   916→"Completing **Final Assessment**.
   917→
   918→I will now:
   919→
   920→1. Review all findings from previous steps
   921→2. Provide a comprehensive summary
   922→3. Add specific recommendations
   923→4. Determine overall readiness status"
   924→
   925→### 2. Review Previous Findings
   926→
   927→Check the {outputFile} for sections added by previous steps:
   928→
   929→- File and FR Validation findings
   930→- UX Alignment issues
   931→- Epic Quality violations
   932→
   933→### 3. Add Final Assessment Section
   934→
   935→Append to {outputFile}:
   936→
   937→```markdown
   938→## Summary and Recommendations
   939→
   940→### Overall Readiness Status
   941→
   942→[READY/NEEDS WORK/NOT READY]
   943→
   944→### Critical Issues Requiring Immediate Action
   945→
   946→[List most critical issues that must be addressed]
   947→
   948→### Recommended Next Steps
   949→
   950→1. [Specific action item 1]
   951→2. [Specific action item 2]
   952→3. [Specific action item 3]
   953→
   954→### Final Note
   955→
   956→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.
   957→```
   958→
   959→### 4. Complete the Report
   960→
   961→- Ensure all findings are clearly documented
   962→- Verify recommendations are actionable
   963→- Add date and assessor information
   964→- Save the final report
   965→
   966→### 5. Present Completion
   967→
   968→Display:
   969→"**Implementation Readiness Assessment Complete**
   970→
   971→Report generated: {outputFile}
   972→
   973→The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations."
   974→
   975→## WORKFLOW COMPLETE
   976→
   977→The implementation readiness workflow is now complete. The report contains all findings and recommendations for the user to consider.
   978→
   979→Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
   980→
   981→---
   982→
   983→## 🚨 SYSTEM SUCCESS/FAILURE METRICS
   984→
   985→### ✅ SUCCESS:
   986→
   987→- All findings compiled and summarized
   988→- Clear recommendations provided
   989→- Readiness status determined
   990→- Final report saved
   991→
   992→### ❌ SYSTEM FAILURE:
   993→
   994→- Not reviewing previous findings
   995→- Incomplete summary
   996→- No clear recommendations
   997→
   998→=== /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md ===
   999→# Step 8: Architecture Completion & Handoff
  1000→
  1001→## MANDATORY EXECUTION RULES (READ FIRST):
  1002→
  1003→- 🛑 NEVER generate content without user input
  1004→
  1005→- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
  1006→- ✅ ALWAYS treat this as collaborative completion between architectural peers
  1007→- 📋 YOU ARE A FACILITATOR, not a content generator
  1008→- 💬 FOCUS on successful workflow completion and implementation handoff
  1009→- 🎯 PROVIDE clear next steps for implementation phase
  1010→- ⚠ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
  1011→- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
  1012→
  1013→## EXECUTION PROTOCOLS:
  1014→
  1015→- 🎯 Show your analysis before taking any action
  1016→- 🎯 Present completion summary and implementation guidance
  1017→- 📖 Update frontmatter with final workflow state
  1018→- 🚫 THIS IS THE FINAL STEP IN THIS WORKFLOW
  1019→
  1020→## YOUR TASK:
  1021→
  1022→Complete the architecture workflow, provide a comprehensive completion summary, and guide the user to the next phase of their project development.
  1023→
  1024→## COMPLETION SEQUENCE:
  1025→
  1026→### 1. Congratulate the User on Completion
  1027→
  1028→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.
  1029→
  1030→### 2. Update the created document's frontmatter
  1031→
  1032→```yaml
  1033→stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]
  1034→workflowType: 'architecture'
  1035→lastStep: 8
  1036→status: 'complete'
  1037→completedAt: '{{current_date}}'
  1038→```
  1039→
  1040→### 3. Next Steps Guidance
  1041→
  1042→Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
  1043→
  1044→Upon Completion of task output: offer to answer any questions about the Architecture Document.
  1045→
  1046→
  1047→## SUCCESS METRICS:
  1048→
  1049→✅ Complete architecture document delivered with all sections
  1050→✅ All architectural decisions documented and validated
  1051→✅ Implementation patterns and consistency rules finalized
  1052→✅ Project structure complete with all files and directories
  1053→✅ User provided with clear next steps and implementation guidance
  1054→✅ Workflow status properly updated
  1055→✅ User collaboration maintained throughout completion process
  1056→
  1057→## FAILURE MODES:
  1058→
  1059→❌ Not providing clear implementation guidance
  1060→❌ Missing final validation of document completeness
  1061→❌ Not updating workflow status appropriately
  1062→❌ Failing to celebrate the successful completion
  1063→❌ Not providing specific next steps for the user
  1064→❌ Rushing completion without proper summary
  1065→
  1066→❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
  1067→❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
  1068→❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
  1069→
  1070→## WORKFLOW COMPLETE:
  1071→
  1072→This is the final step of the Architecture workflow. The user now has a complete, validated architecture document ready for AI agent implementation.
  1073→
  1074→The architecture will serve as the single source of truth for all technical decisions, ensuring consistent implementation across the entire project development lifecycle.
  1075→
  1076→=== /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md ===
  1077→---
  1078→name: 'step-04-final-validation'
  1079→description: 'Validate complete coverage of all requirements and ensure implementation readiness'
  1080→
  1081→# Path Definitions
  1082→workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
  1083→
  1084→# File References
  1085→thisStepFile: './step-04-final-validation.md'
  1086→workflowFile: '{workflow_path}/workflow.md'
  1087→outputFile: '{planning_artifacts}/epics.md'
  1088→
  1089→# Task References
  1090→advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
  1091→partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
  1092→
  1093→# Template References
  1094→epicsTemplate: '{workflow_path}/templates/epics-template.md'
  1095→---
  1096→
  1097→# Step 4: Final Validation
  1098→
  1099→## STEP GOAL:
  1100→
  1101→To validate complete coverage of all requirements and ensure stories are ready for development.
  1102→
  1103→## MANDATORY EXECUTION RULES (READ FIRST):
  1104→
  1105→### Universal Rules:
  1106→
  1107→- 🛑 NEVER generate content without user input
  1108→- 📖 CRITICAL: Read the complete step file before taking any action
  1109→- 🔄 CRITICAL: Process validation sequentially without skipping
  1110→- 📋 YOU ARE A FACILITATOR, not a content generator
  1111→- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
  1112→
  1113→### Role Reinforcement:
  1114→
  1115→- ✅ You are a product strategist and technical specifications writer
  1116→- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
  1117→- ✅ We engage in collaborative dialogue, not command-response
  1118→- ✅ You bring validation expertise and quality assurance
  1119→- ✅ User brings their implementation priorities and final review
  1120→
  1121→### Step-Specific Rules:
  1122→
  1123→- 🎯 Focus ONLY on validating complete requirements coverage
  1124→- 🚫 FORBIDDEN to skip any validation checks
  1125→- 💬 Validate FR coverage, story completeness, and dependencies
  1126→- 🚪 ENSURE all stories are ready for development
  1127→
  1128→## EXECUTION PROTOCOLS:
  1129→
  1130→- 🎯 Validate every requirement has story coverage
  1131→- 💾 Check story dependencies and flow
  1132→- 📖 Verify architecture compliance
  1133→- 🚫 FORBIDDEN to approve incomplete coverage
  1134→
  1135→## CONTEXT BOUNDARIES:
  1136→
  1137→- Available context: Complete epic and story breakdown from previous steps
  1138→- Focus: Final validation of requirements coverage and story readiness
  1139→- Limits: Validation only, no new content creation
  1140→- Dependencies: Completed story generation from Step 3
  1141→
  1142→## VALIDATION PROCESS:
  1143→
  1144→### 1. FR Coverage Validation
  1145→
  1146→Review the complete epic and story breakdown to ensure EVERY FR is covered:
  1147→
  1148→**CRITICAL CHECK:**
  1149→
  1150→- Go through each FR from the Requirements Inventory
  1151→- Verify it appears in at least one story
  1152→- Check that acceptance criteria fully address the FR
  1153→- No FRs should be left uncovered
  1154→
  1155→### 2. Architecture Implementation Validation
  1156→
  1157→**Check for Starter Template Setup:**
  1158→
  1159→- Does Architecture document specify a starter template?
  1160→- If YES: Epic 1 Story 1 must be "Set up initial project from starter template"
  1161→- This includes cloning, installing dependencies, initial configuration
  1162→
  1163→**Database/Entity Creation Validation:**
  1164→
  1165→- Are database tables/entities created ONLY when needed by stories?
  1166→- ❌ WRONG: Epic 1 creates all tables upfront
  1167→- ✅ RIGHT: Tables created as part of the first story that needs them
  1168→- Each story should create/modify ONLY what it needs
  1169→
  1170→### 3. Story Quality Validation
  1171→
  1172→**Each story must:**
  1173→
  1174→- Be completable by a single dev agent
  1175→- Have clear acceptance criteria
  1176→- Reference specific FRs it implements
  1177→- Include necessary technical details
  1178→- **Not have forward dependencies** (can only depend on PREVIOUS stories)
  1179→- Be implementable without waiting for future stories
  1180→
  1181→### 4. Epic Structure Validation
  1182→
  1183→**Check that:**
  1184→
  1185→- Epics deliver user value, not technical milestones
  1186→- Dependencies flow naturally
  1187→- Foundation stories only setup what's needed
  1188→- No big upfront technical work
  1189→
  1190→### 5. Dependency Validation (CRITICAL)
  1191→
  1192→**Epic Independence Check:**
  1193→
  1194→- Does each epic deliver COMPLETE functionality for its domain?
  1195→- Can Epic 2 function without Epic 3 being implemented?
  1196→- Can Epic 3 function standalone using Epic 1 & 2 outputs?
  1197→- ❌ WRONG: Epic 2 requires Epic 3 features to work
  1198→- ✅ RIGHT: Each epic is independently valuable
  1199→
  1200→**Within-Epic Story Dependency Check:**
  1201→For each epic, review stories in order:
  1202→
  1203→- Can Story N.1 be completed without Stories N.2, N.3, etc.?
  1204→- Can Story N.2 be completed using only Story N.1 output?
  1205→- Can Story N.3 be completed using only Stories N.1 & N.2 outputs?
  1206→- ❌ WRONG: "This story depends on a future story"
  1207→- ❌ WRONG: Story references features not yet implemented
  1208→- ✅ RIGHT: Each story builds only on previous stories
  1209→
  1210→### 6. Complete and Save
  1211→
  1212→If all validations pass:
  1213→
  1214→- Update any remaining placeholders in the document
  1215→- Ensure proper formatting
  1216→- Save the final epics.md
  1217→
  1218→**Present Final Menu:**
  1219→**All validations complete!** [C] Complete Workflow
  1220→
  1221→When C is selected, the workflow is complete and the epics.md is ready for development.
  1222→
  1223→Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
  1224→
  1225→Upon Completion of task output: offer to answer any questions about the Epics and Stories.
  1226→
  1227→=== /Users/alex/src/bmad/quick-flow-redesign/src/bmm/workflows/generate-project-context/steps/step-03-complete.md ===
  1228→# Step 3: Context Completion & Finalization
  1229→
  1230→## MANDATORY EXECUTION RULES (READ FIRST):
  1231→
  1232→- 🛑 NEVER generate content without user input
  1233→- ✅ ALWAYS treat this as collaborative completion between technical peers
  1234→- 📋 YOU ARE A FACILITATOR, not a content generator
  1235→- 💬 FOCUS on finalizing a lean, LLM-optimized project context
  1236→- 🎯 ENSURE all critical rules are captured and actionable
  1237→- ⚠ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
  1238→- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
  1239→
  1240→## EXECUTION PROTOCOLS:
  1241→
  1242→- 🎯 Show your analysis before taking any action
  1243→- 📝 Review and optimize content for LLM context efficiency
  1244→- 📖 Update frontmatter with completion status
  1245→- 🚫 NO MORE STEPS - this is the final step
  1246→
  1247→## CONTEXT BOUNDARIES:
  1248→
  1249→- All rule categories from step-2 are complete
  1250→- Technology stack and versions are documented
  1251→- Focus on final review, optimization, and completion
  1252→- Ensure the context file is ready for AI agent consumption
  1253→
  1254→## YOUR TASK:
  1255→
  1256→Complete the project context file, optimize it for LLM efficiency, and provide guidance for usage and maintenance.
  1257→
  1258→## COMPLETION SEQUENCE:
  1259→
  1260→### 1. Review Complete Context File
  1261→
  1262→Read the entire project context file and analyze:
  1263→
  1264→**Content Analysis:**
  1265→
  1266→- Total length and readability for LLMs
  1267→- Clarity and specificity of rules
  1268→- Coverage of all critical areas
  1269→- Actionability of each rule
  1270→
  1271→**Structure Analysis:**
  1272→
  1273→- Logical organization of sections
  1274→- Consistency of formatting
  1275→- Absence of redundant or obvious information
  1276→- Optimization for quick scanning
  1277→
  1278→### 2. Optimize for LLM Context
  1279→
  1280→Ensure the file is lean and efficient:
  1281→
  1282→**Content Optimization:**
  1283→
  1284→- Remove any redundant rules or obvious information
  1285→- Combine related rules into concise bullet points
  1286→- Use specific, actionable language
  1287→- Ensure each rule provides unique value
  1288→
  1289→**Formatting Optimization:**
  1290→
  1291→- Use consistent markdown formatting
  1292→- Implement clear section hierarchy
  1293→- Ensure scannability with strategic use of bolding
  1294→- Maintain readability while maximizing information density
  1295→
  1296→### 3. Final Content Structure
  1297→
  1298→Ensure the final structure follows this optimized format:
  1299→
  1300→```markdown
  1301→# Project Context for AI Agents
  1302→
  1303→_This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._
  1304→
  1305→---
  1306→
  1307→## Technology Stack & Versions
  1308→
  1309→{{concise_technology_list}}
  1310→
  1311→## Critical Implementation Rules
  1312→
  1313→### Language-Specific Rules
  1314→
  1315→{{specific_language_rules}}
  1316→
  1317→### Framework-Specific Rules
  1318→
  1319→{{framework_patterns}}
  1320→
  1321→### Testing Rules
  1322→
  1323→{{testing_requirements}}
  1324→
  1325→### Code Quality & Style Rules
  1326→
  1327→{{style_and_quality_patterns}}
  1328→
  1329→### Development Workflow Rules
  1330→
  1331→{{workflow_patterns}}
  1332→
  1333→### Critical Don't-Miss Rules
  1334→
  1335→{{anti_patterns_and_edge_cases}}
  1336→
  1337→---
  1338→
  1339→## Usage Guidelines
  1340→
  1341→**For AI Agents:**
  1342→
  1343→- Read this file before implementing any code
  1344→- Follow ALL rules exactly as documented
  1345→- When in doubt, prefer the more restrictive option
  1346→- Update this file if new patterns emerge
  1347→
  1348→**For Humans:**
  1349→
  1350→- Keep this file lean and focused on agent needs
  1351→- Update when technology stack changes
  1352→- Review quarterly for outdated rules
  1353→- Remove rules that become obvious over time
  1354→
  1355→Last Updated: {{date}}
  1356→```
  1357→
  1358→### 4. Present Completion Summary
  1359→
  1360→Based on user skill level, present the completion:
  1361→
  1362→**Expert Mode:**
  1363→"Project context complete. Optimized for LLM consumption with {{rule_count}} critical rules across {{section_count}} sections.
  1364→
  1365→File saved to: `{output_folder}/project-context.md`
  1366→
  1367→Ready for AI agent integration."
  1368→
  1369→**Intermediate Mode:**
  1370→"Your project context is complete and optimized for AI agents!
  1371→
  1372→**What we created:**
  1373→
  1374→- {{rule_count}} critical implementation rules
  1375→- Technology stack with exact versions
  1376→- Framework-specific patterns and conventions
  1377→- Testing and quality guidelines
  1378→- Workflow and anti-pattern rules
  1379→
  1380→**Key benefits:**
  1381→
  1382→- AI agents will implement consistently with your standards
  1383→- Reduced context switching and implementation errors
  1384→- Clear guidance for unobvious project requirements
  1385→
  1386→**Next steps:**
  1387→
  1388→- AI agents should read this file before implementing
  1389→- Update as your project evolves
  1390→- Review periodically for optimization"
  1391→
  1392→**Beginner Mode:**
  1393→"Excellent! Your project context guide is ready! 🎉
  1394→
  1395→**What this does:**
  1396→Think of this as a 'rules of the road' guide for AI agents working on your project. It ensures they all follow the same patterns and avoid common mistakes.
  1397→
  1398→**What's included:**
  1399→
  1400→- Exact technology versions to use
  1401→- Critical coding rules they might miss
  1402→- Testing and quality standards
  1403→- Workflow patterns to follow
  1404→
  1405→**How AI agents use it:**
  1406→They read this file before writing any code, ensuring everything they create follows your project's standards perfectly.
  1407→
  1408→Your project context is saved and ready to help agents implement consistently!"
  1409→
  1410→### 5. Final File Updates
  1411→
  1412→Update the project context file with completion information:
  1413→
  1414→**Frontmatter Update:**
  1415→
  1416→```yaml
  1417→---
  1418→project_name: '{{project_name}}'
  1419→user_name: '{{user_name}}'
  1420→date: '{{date}}'
  1421→sections_completed:
  1422→  ['technology_stack', 'language_rules', 'framework_rules', 'testing_rules', 'quality_rules', 'workflow_rules', 'anti_patterns']
  1423→status: 'complete'
  1424→rule_count: { { total_rules } }
  1425→optimized_for_llm: true
  1426→---
  1427→```
  1428→
  1429→**Add Usage Section:**
  1430→Append the usage guidelines from step 3 to complete the document.
  1431→
  1432→### 6. Completion Validation
  1433→
  1434→Final checks before completion:
  1435→
  1436→**Content Validation:**
  1437→✅ All critical technology versions documented
  1438→✅ Language-specific rules are specific and actionable
  1439→✅ Framework rules cover project conventions
  1440→✅ Testing rules ensure consistency
  1441→✅ Code quality rules maintain standards
  1442→✅ Workflow rules prevent conflicts
  1443→✅ Anti-pattern rules prevent common mistakes
  1444→
  1445→**Format Validation:**
  1446→✅ Content is lean and optimized for LLMs
  1447→✅ Structure is logical and scannable
  1448→✅ No redundant or obvious information
  1449→✅ Consistent formatting throughout
  1450→
  1451→### 7. Completion Message
  1452→
  1453→Present final completion to user:
  1454→
  1455→"✅ **Project Context Generation Complete!**
  1456→
  1457→Your optimized project context file is ready at:
  1458→`{output_folder}/project-context.md`
  1459→
  1460→**📊 Context Summary:**
  1461→
  1462→- {{rule_count}} critical rules for AI agents
  1463→- {{section_count}} comprehensive sections
  1464→- Optimized for LLM context efficiency
  1465→- Ready for immediate agent integration
  1466→
  1467→**🎯 Key Benefits:**
  1468→
  1469→- Consistent implementation across all AI agents
  1470→- Reduced common mistakes and edge cases
  1471→- Clear guidance for project-specific patterns
  1472→- Minimal LLM context usage
  1473→
  1474→**📋 Next Steps:**
  1475→
  1476→1. AI agents will automatically read this file when implementing
  1477→2. Update this file when your technology stack or patterns evolve
  1478→3. Review quarterly to optimize and remove outdated rules
  1479→
  1480→Your project context will help ensure high-quality, consistent implementation across all development work. Great work capturing your project's critical implementation requirements!"
  1481→
  1482→## SUCCESS METRICS:
  1483→
  1484→✅ Complete project context file with all critical rules
  1485→✅ Content optimized for LLM context efficiency
  1486→✅ All technology versions and patterns documented
  1487→✅ File structure is logical and scannable
  1488→✅ Usage guidelines included for agents and humans
  1489→✅ Frontmatter properly updated with completion status
  1490→✅ User provided with clear next steps and benefits
  1491→
  1492→## FAILURE MODES:
  1493→
  1494→❌ Final content is too verbose for LLM consumption
  1495→❌ Missing critical implementation rules or patterns
  1496→❌ Not optimizing content for agent readability
  1497→❌ Not providing clear usage guidelines
  1498→❌ Frontmatter not properly updated
  1499→❌ Not validating file completion before ending
  1500→
  1501→## WORKFLOW COMPLETE:
  1502→
  1503→This is the final step of the Generate Project Context workflow. The user now has a comprehensive, optimized project context file that will ensure consistent, high-quality implementation across all AI agents working on the project.
  1504→
  1505→The project context file serves as the critical "rules of the road" that agents need to implement code consistently with the project's standards and patterns.
  1506→
  1507→

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

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

## The Diff

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

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

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

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

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

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

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

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

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

```markdown
# Task: BMAD Help

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

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

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

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

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


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

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

## The Diff

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

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

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

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

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

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

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

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

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

```markdown
# Task: BMAD Help

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

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

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

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

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


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

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

## The Diff

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

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

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

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

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

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

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

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

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

```markdown
# Task: BMAD Help

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

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

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

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

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


No files found

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

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

## The Diff

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

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

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

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

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

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

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

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

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

```markdown
# Task: BMAD Help

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

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

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

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

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


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

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

## The Diff

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

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

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

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

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

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

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

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

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

```markdown
# Task: BMAD Help

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

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

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

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

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


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

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

## The Diff

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

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

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

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

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

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

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

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

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

```markdown
# Task: BMAD Help

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

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

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

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

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