diff --git a/README.md b/README.md index 476f102d..02e17742 100644 --- a/README.md +++ b/README.md @@ -23,6 +23,14 @@ BMad-CORE (**C**ollaboration **O**ptimized **R**eflection **E**ngine) is a revol --- +## 🚀 New to v6? Start Here! + +**[→ BMad Method V6 Quick Start Guide](./docs/BMad-Method-V6-Quick-Start.md)** - **NEW!** Get up and running with v6 in minutes + +Learn how to build your first greenfield project with BMad Method v6 using our brand new quick start guide! + +--- + ## 🔄 Upgrading from v4? **[→ v4 to v6 Upgrade Guide](./docs/v4-to-v6-upgrade.md)** - Complete migration instructions for existing v4 users diff --git a/src/modules/bmb/workflows/create-agent/instructions.md b/src/modules/bmb/workflows/create-agent/instructions.md index 1b15beff..745aab1a 100644 --- a/src/modules/bmb/workflows/create-agent/instructions.md +++ b/src/modules/bmb/workflows/create-agent/instructions.md @@ -20,8 +20,6 @@ Proceed directly to Step 0 - -brainstorming_results @@ -103,9 +101,24 @@ 7. Wise Sage/Yoda - Cryptic wisdom, inverted syntax 8. Game Show Host - Enthusiastic, game show tropes -**Professional Presets:** 9. Analytical Expert - Systematic, data-driven, hierarchical 10. Supportive Mentor - Patient guidance, celebrates wins 11. Direct Consultant - Straight to the point, efficient 12. Collaborative Partner - Team-oriented, inclusive +**Professional Presets:** -**Quirky Presets:** 13. Cooking Show Chef - Recipe metaphors, culinary terms 14. Sports Commentator - Play-by-play, excitement 15. Nature Documentarian - Wildlife documentary style 16. Time Traveler - Temporal references, timeline talk 17. Conspiracy Theorist - Everything is connected 18. Zen Master - Philosophical, paradoxical 19. Star Trek Captain - Space exploration protocols 20. Soap Opera Drama - Dramatic reveals, gasps 21. Reality TV Contestant - Confessionals, drama +9. Analytical Expert - Systematic, data-driven, hierarchical +10. Supportive Mentor - Patient guidance, celebrates wins +11. Direct Consultant - Straight to the point, efficient +12. Collaborative Partner - Team-oriented, inclusive + +**Quirky Presets:** + +13. Cooking Show Chef - Recipe metaphors, culinary terms +14. Sports Commentator - Play-by-play, excitement +15. Nature Documentarian - Wildlife documentary style +16. Time Traveler - Temporal references, timeline talk +17. Conspiracy Theorist - Everything is connected +18. Zen Master - Philosophical, paradoxical +19. Star Trek Captain - Space exploration protocols +20. Soap Opera Drama - Dramatic reveals, gasps +21. Reality TV Contestant - Confessionals, drama If user wants to see more examples or create custom styles, show relevant sections from {communication_styles} guide and help them craft their unique style @@ -352,16 +365,16 @@ Add domain-specific resources here. Build tools not detected in this project. Would you like me to: - 1. Generate the compiled agent (.md with XML) ready to use - 2. Keep the YAML and build it elsewhere - 3. Provide both formats +1. Generate the compiled agent (.md with XML) ready to use +2. Keep the YAML and build it elsewhere +3. Provide both formats - - Generate compiled agent XML with proper structure including activation rules, persona sections, and menu items - Save compiled version as {{agent_filename}}.md - Provide path for .claude/commands/ or similar - + + Generate compiled agent XML with proper structure including activation rules, persona sections, and menu items + Save compiled version as {{agent_filename}}.md + Provide path for .claude/commands/ or similar + diff --git a/src/modules/bmb/workflows/create-workflow/instructions.md b/src/modules/bmb/workflows/create-workflow/instructions.md index 46553ee1..0cfa0242 100644 --- a/src/modules/bmb/workflows/create-workflow/instructions.md +++ b/src/modules/bmb/workflows/create-workflow/instructions.md @@ -108,7 +108,8 @@ Most workflows should be `standalone: true` to give users direct access. 1. **Yes (Recommended)** - Users can run it directly (standalone: true) 2. **No** - Only called by other workflows/agents (standalone: false) -Most workflows choose option 1: +Most workflows choose option 1: + Store {{standalone_setting}} as true or false based on response @@ -150,7 +151,8 @@ The architecture workflow is an excellent example of intent-based with prescript 2. **Prescriptive** - Structured, consistent, controlled interactions 3. **Mixed/Balanced** - I'll help you decide step-by-step -What feels right for your workflow's purpose? +What feels right for your workflow's purpose? + Store {{instruction_style}} preference @@ -185,11 +187,12 @@ Beyond style, consider **how interactive** this workflow should be: What interactivity level suits this workflow? -1. **High** - Highly collaborative, user actively involved throughout -2. **Medium** - Guided with key decision points (most common) -3. **Low** - Autonomous with final review +1. **High** - Highly collaborative, user actively involved throughout (Recommended) +2. **Medium** - Guided with key decision points +3. **Low** - Mostly autonomous with final review -Select the level that matches your workflow's purpose: +Select the level that matches your workflow's purpose: + Store {{interactivity_level}} preference @@ -487,6 +490,7 @@ Generate the template.md file following guide conventions: # Document Title **Date:** {{date}} + **Author:** {{user_name}} ``` @@ -575,7 +579,9 @@ Review the created workflow: 4. Validate YAML syntax 5. Confirm all placeholders are replaced -**Standard Config Validation:** 6. Verify workflow.yaml contains standard config block: +**Standard Config Validation:** + +6. Verify workflow.yaml contains standard config block: - config_source defined - output_folder, user_name, communication_language pulled from config @@ -584,7 +590,9 @@ Review the created workflow: 7. Check instructions use config variables where appropriate 8. Verify template includes config variables in metadata (if document workflow) -**YAML/Instruction/Template Alignment:** 9. Cross-check all workflow.yaml variables against instruction usage: +**YAML/Instruction/Template Alignment:** + +9. Cross-check all workflow.yaml variables against instruction usage: - Are all yaml variables referenced in instructions.md OR template.md? - Are there hardcoded values that should be variables? diff --git a/src/modules/bmm/workflows/1-analysis/brainstorm-game/instructions.md b/src/modules/bmm/workflows/1-analysis/brainstorm-game/instructions.md index bd7f6f2a..e27f344c 100644 --- a/src/modules/bmm/workflows/1-analysis/brainstorm-game/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/brainstorm-game/instructions.md @@ -5,20 +5,20 @@ - - - mode: validate - calling_workflow: brainstorm-game - + + Check if {output_folder}/bmm-workflow-status.yaml exists - - {{suggestion}} - Note: Game brainstorming is optional. Continuing without progress tracking. + + No workflow status file found. Game brainstorming is optional - you can continue without status tracking. Set standalone_mode = true - - Store {{status_file_path}} for later updates + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "brainstorm-game" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) Note: This is a {{project_type}} project. Game brainstorming is designed for game projects. @@ -28,10 +28,25 @@ - - {{warning}} - Note: Game brainstorming can be valuable at any project stage. + + ⚠️ Game brainstorming session already completed: {{brainstorm-game status}} + Re-running will create a new session. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + ⚠️ Next expected workflow: {{next_workflow}}. Game brainstorming is out of sequence. + Continue with game brainstorming anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + + Set standalone_mode = false @@ -66,17 +81,16 @@ - + - - mode: update - action: complete_workflow - workflow_name: brainstorm-game - + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "brainstorm-game" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["brainstorm-game"] = "{output_folder}/bmm-brainstorming-session-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - Status updated! Next: {{next_workflow}} - + Find first non-completed workflow in workflow_status (next workflow to do) + Determine next agent from path file based on next workflow **✅ Game Brainstorming Session Complete, {user_name}!** @@ -88,16 +102,21 @@ {{#if standalone_mode != true}} **Status Updated:** -- Progress tracking updated +- Progress tracking updated: brainstorm-game marked complete +- Next workflow: {{next_workflow}} + {{else}} + **Note:** Running in standalone mode (no progress tracking) + {{/if}} **Next Steps:** -- **Next required:** {{next_workflow}} ({{next_agent}} agent) +{{#if standalone_mode != true}} + +- **Next workflow:** {{next_workflow}} ({{next_agent}} agent) - **Optional:** You can run other analysis workflows (research, game-brief) before proceeding Check status anytime with: `workflow-status` {{else}} -**Next Steps:** Since no workflow is in progress: - Refer to the BMM workflow guide if unsure what to do next diff --git a/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md b/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md index ceb0d0c8..af117e50 100644 --- a/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md @@ -8,25 +8,40 @@ - - - mode: validate - calling_workflow: brainstorm-project - + + Check if {output_folder}/bmm-workflow-status.yaml exists - - {{suggestion}} - Note: Brainstorming is optional. Continuing without progress tracking. + + No workflow status file found. Brainstorming is optional - you can continue without status tracking. Set standalone_mode = true - - Store {{status_file_path}} for later updates + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "brainstorm-project" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) - - {{warning}} - Note: Brainstorming can be valuable at any project stage. + + ⚠️ Brainstorming session already completed: {{brainstorm-project status}} + Re-running will create a new session. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + ⚠️ Next expected workflow: {{next_workflow}}. Brainstorming is out of sequence. + Continue with brainstorming anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + + Set standalone_mode = false @@ -51,36 +66,40 @@ - + - - mode: update - action: complete_workflow - workflow_name: brainstorm-project - + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "brainstorm-project" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["brainstorm-project"] = "{output_folder}/bmm-brainstorming-session-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - Status updated! Next: {{next_workflow}} - + Find first non-completed workflow in workflow_status (next workflow to do) + Determine next agent from path file based on next workflow **✅ Brainstorming Session Complete, {user_name}!** **Session Results:** + - Brainstorming results saved to: {output_folder}/bmm-brainstorming-session-{{date}}.md {{#if standalone_mode != true}} **Status Updated:** + - Progress tracking updated **Next Steps:** + - **Next required:** {{next_workflow}} ({{next_agent}} agent) - **Optional:** You can run other analysis workflows (research, product-brief) before proceeding Check status anytime with: `workflow-status` {{else}} **Next Steps:** + Since no workflow is in progress: + - Refer to the BMM workflow guide if unsure what to do next - Or run `workflow-init` to create a workflow path and get guided next steps {{/if}} diff --git a/src/modules/bmm/workflows/1-analysis/game-brief/instructions.md b/src/modules/bmm/workflows/1-analysis/game-brief/instructions.md index 6a0c715a..d6b675e7 100644 --- a/src/modules/bmm/workflows/1-analysis/game-brief/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/game-brief/instructions.md @@ -9,20 +9,20 @@ - - - mode: validate - calling_workflow: game-brief - + +Check if {output_folder}/bmm-workflow-status.yaml exists - - {{suggestion}} - Note: Game brief is optional. Continuing without progress tracking. + + No workflow status file found. Game brief is optional - you can continue without status tracking. Set standalone_mode = true - - Store {{status_file_path}} for later updates + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "game-brief" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) Note: This is a {{project_type}} project. Game brief is designed for game projects. @@ -32,10 +32,25 @@ - - {{warning}} - Note: Game brief can provide valuable vision clarity at any stage. + + ⚠️ Game Brief already completed: {{game-brief status}} + Re-running will overwrite the existing brief. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + ⚠️ Next expected workflow: {{next_workflow}}. Game Brief is out of sequence. + Continue with Game Brief anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + +Set standalone_mode = false @@ -309,17 +324,16 @@ This brief will serve as the primary input for creating the Game Design Document executive_brief - + - - mode: update - action: complete_workflow - workflow_name: game-brief - + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "game-brief" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["game-brief"] = "{output_folder}/bmm-game-brief-{{game_name}}-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - Status updated! Next: {{next_workflow}} - +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow **✅ Game Brief Complete, {user_name}!** @@ -331,17 +345,17 @@ This brief will serve as the primary input for creating the Game Design Document {{#if standalone_mode != true}} **Status Updated:** -- Progress tracking updated +- Progress tracking updated: game-brief marked complete +- Next workflow: {{next_workflow}} {{else}} - Note: Running in standalone mode (no status file). - To track progress across workflows, run `workflow-init` first. + **Note:** Running in standalone mode (no progress tracking) {{/if}} **Next Steps:** {{#if standalone_mode != true}} -- **Next required:** {{next_workflow}} ({{next_agent}} agent) +- **Next workflow:** {{next_workflow}} ({{next_agent}} agent) - **Optional:** Consider creating a prototype of core mechanic or validating assumptions with target players before proceeding Check status anytime with: `workflow-status` diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md b/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md index 524fdb5e..b0fafa4f 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md @@ -9,34 +9,45 @@ - - - mode: validate - calling_workflow: product-brief - + +Check if {output_folder}/bmm-workflow-status.yaml exists - - {{suggestion}} - Note: Product Brief is optional. You can continue without status tracking. + + No workflow status file found. Product Brief is optional - you can continue without status tracking. Set standalone_mode = true - - Store {{status_file_path}} for later updates + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "product-brief" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) Note: Product Brief is most valuable for Level 2+ projects. Your project is Level {{project_level}}. You may want to skip directly to technical planning instead. - - {{warning}} - Continue with Product Brief anyway? (y/n) + + ⚠️ Product Brief already completed: {{product-brief status}} + Re-running will overwrite the existing brief. Continue? (y/n) - Exiting. {{suggestion}} + Exiting. Use workflow-status to see your next step. Exit workflow + + + ⚠️ Next expected workflow: {{next_workflow}}. Product Brief is out of sequence. + Continue with Product Brief anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + +Set standalone_mode = false @@ -61,6 +72,7 @@ How would you like to work through the brief? **1. Interactive Mode** - We'll work through each section together, discussing and refining as we go + **2. YOLO Mode** - I'll generate a complete draft based on our conversation so far, then we'll refine it together Which approach works best for you? @@ -273,17 +285,16 @@ This brief will serve as the primary input for creating the Product Requirements executive_brief - + - - mode: update - action: complete_workflow - workflow_name: product-brief - + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "product-brief" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["product-brief"] = "{output_folder}/bmm-product-brief-{{project_name}}-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - Status updated! Next: {{next_workflow}} - +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow **✅ Product Brief Complete, {user_name}!** @@ -295,8 +306,8 @@ This brief will serve as the primary input for creating the Product Requirements {{#if standalone_mode != true}} **Status Updated:** -- Progress tracking updated -- Current workflow marked complete +- Progress tracking updated: product-brief marked complete +- Next workflow: {{next_workflow}} {{else}} **Note:** Running in standalone mode (no progress tracking) {{/if}} @@ -305,7 +316,7 @@ This brief will serve as the primary input for creating the Product Requirements {{#if standalone_mode != true}} -- **Next required:** {{next_workflow}} ({{next_agent}} agent) +- **Next workflow:** {{next_workflow}} ({{next_agent}} agent) - **Optional:** Gather additional stakeholder input or run research workflows before proceeding Check status anytime with: `workflow-status` diff --git a/src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md b/src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md index 9b0fbded..16ea092a 100644 --- a/src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md +++ b/src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md @@ -374,60 +374,50 @@ Select option (1-4): - -Search {output_folder}/ for files matching pattern: bmm-workflow-status.md -Find the most recent file (by date in filename) + + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "research" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["research"] = "{output_folder}/bmm-research-deep-prompt-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - - mode: update - action: complete_workflow - workflow_name: research - - - - Status updated! Next: {{next_workflow}} - +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow + **✅ Deep Research Prompt Generated** **Research Prompt:** -- Structured research prompt generated and saved +- Structured research prompt generated and saved to {output_folder}/bmm-research-deep-prompt-{{date}}.md - Ready to execute with ChatGPT, Claude, Gemini, or Grok -**Status file updated:** +{{#if standalone_mode != true}} +**Status Updated:** -- Current step: research (deep-prompt) ✓ -- Progress: {{new_progress_percentage}}% +- Progress tracking updated: research marked complete +- Next workflow: {{next_workflow}} + {{else}} + **Note:** Running in standalone mode (no progress tracking) + {{/if}} **Next Steps:** -- **Next required:** {{next_workflow}} ({{next_agent}} agent) +{{#if standalone_mode != true}} + +- **Next workflow:** {{next_workflow}} ({{next_agent}} agent) - **Optional:** Execute the research prompt with AI platform, gather findings, or run additional research workflows Check status anytime with: `workflow-status` - - - - - **✅ Deep Research Prompt Generated** - -**Research Prompt:** - -- Structured research prompt generated and saved - -Note: Running in standalone mode (no status file). - -**Next Steps:** - +{{else}} Since no workflow is in progress: - Execute the research prompt with AI platform and gather findings - Refer to the BMM workflow guide if unsure what to do next - Or run `workflow-init` to create a workflow path and get guided next steps + {{/if}} - diff --git a/src/modules/bmm/workflows/1-analysis/research/instructions-market.md b/src/modules/bmm/workflows/1-analysis/research/instructions-market.md index a34ded6f..fd255673 100644 --- a/src/modules/bmm/workflows/1-analysis/research/instructions-market.md +++ b/src/modules/bmm/workflows/1-analysis/research/instructions-market.md @@ -554,60 +554,49 @@ Create compelling executive summary with: - -Search {output_folder}/ for files matching pattern: bmm-workflow-status.md -Find the most recent file (by date in filename) + + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "research" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["research"] = "{output_folder}/bmm-research-{{research_mode}}-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - - mode: update - action: complete_workflow - workflow_name: research - - - - Status updated! Next: {{next_workflow}} - +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow **✅ Research Complete ({{research_mode}} mode)** **Research Report:** -- Research report generated and saved +- Research report generated and saved to {output_folder}/bmm-research-{{research_mode}}-{{date}}.md -**Status file updated:** +{{#if standalone_mode != true}} +**Status Updated:** -- Current step: research ({{research_mode}}) ✓ -- Progress: {{new_progress_percentage}}% +- Progress tracking updated: research marked complete +- Next workflow: {{next_workflow}} + {{else}} + **Note:** Running in standalone mode (no progress tracking) + {{/if}} **Next Steps:** -- **Next required:** {{next_workflow}} ({{next_agent}} agent) +{{#if standalone_mode != true}} + +- **Next workflow:** {{next_workflow}} ({{next_agent}} agent) - **Optional:** Review findings with stakeholders, or run additional analysis workflows (product-brief, game-brief, etc.) Check status anytime with: `workflow-status` - - - - - **✅ Research Complete ({{research_mode}} mode)** - -**Research Report:** - -- Research report generated and saved - -Note: Running in standalone mode (no status file). - -**Next Steps:** - +{{else}} Since no workflow is in progress: - Review research findings - Refer to the BMM workflow guide if unsure what to do next - Or run `workflow-init` to create a workflow path and get guided next steps + {{/if}} - diff --git a/src/modules/bmm/workflows/1-analysis/research/instructions-router.md b/src/modules/bmm/workflows/1-analysis/research/instructions-router.md index ddc05170..b8fc010e 100644 --- a/src/modules/bmm/workflows/1-analysis/research/instructions-router.md +++ b/src/modules/bmm/workflows/1-analysis/research/instructions-router.md @@ -10,26 +10,42 @@ This is a ROUTER that directs to specialized research instruction sets - - - mode: validate - calling_workflow: research - + +Check if {output_folder}/bmm-workflow-status.yaml exists - - {{suggestion}} - Note: Research is optional. Continuing without progress tracking. + + No workflow status file found. Research is optional - you can continue without status tracking. Set standalone_mode = true - - Store {{status_file_path}} for status updates in sub-workflows - Pass status_file_path to loaded instruction set + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "research" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) + Pass status context to loaded instruction set for final update - - {{warning}} - Note: Research can provide valuable insights at any project stage. + + ⚠️ Research already completed: {{research status}} + Re-running will create a new research report. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + ⚠️ Next expected workflow: {{next_workflow}}. Research is out of sequence. + Note: Research can provide valuable insights at any project stage. + Continue with Research anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + +Set standalone_mode = false diff --git a/src/modules/bmm/workflows/1-analysis/research/instructions-technical.md b/src/modules/bmm/workflows/1-analysis/research/instructions-technical.md index 273615ce..a4efb494 100644 --- a/src/modules/bmm/workflows/1-analysis/research/instructions-technical.md +++ b/src/modules/bmm/workflows/1-analysis/research/instructions-technical.md @@ -442,60 +442,49 @@ Select option (1-5): - -Search {output_folder}/ for files matching pattern: bmm-workflow-status.md -Find the most recent file (by date in filename) + + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "research" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["research"] = "{output_folder}/bmm-research-technical-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - - mode: update - action: complete_workflow - workflow_name: research - - - - Status updated! Next: {{next_workflow}} - +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow **✅ Technical Research Complete** **Research Report:** -- Technical research report generated and saved +- Technical research report generated and saved to {output_folder}/bmm-research-technical-{{date}}.md -**Status file updated:** +{{#if standalone_mode != true}} +**Status Updated:** -- Current step: research (technical) ✓ -- Progress: {{new_progress_percentage}}% +- Progress tracking updated: research marked complete +- Next workflow: {{next_workflow}} + {{else}} + **Note:** Running in standalone mode (no progress tracking) + {{/if}} **Next Steps:** -- **Next required:** {{next_workflow}} ({{next_agent}} agent) +{{#if standalone_mode != true}} + +- **Next workflow:** {{next_workflow}} ({{next_agent}} agent) - **Optional:** Review findings with architecture team, or run additional analysis workflows Check status anytime with: `workflow-status` - - - - - **✅ Technical Research Complete** - -**Research Report:** - -- Technical research report generated and saved - -Note: Running in standalone mode (no status file). - -**Next Steps:** - +{{else}} Since no workflow is in progress: - Review technical research findings - Refer to the BMM workflow guide if unsure what to do next - Or run `workflow-init` to create a workflow path and get guided next steps + {{/if}} - diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md index 7fc2519d..b4a061b9 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md @@ -12,28 +12,42 @@ DOCUMENT OUTPUT: Professional, specific, actionable UX design decisions WITH RATIONALE. User skill level ({user_skill_level}) affects conversation style ONLY, not document content. - + +Check if {output_folder}/bmm-workflow-status.yaml exists - - mode: data - data_request: project_config - - - - **Note: No Workflow Status File Found** - -Create UX Design can run standalone or as part of the BMM planning workflow. - -For standalone use, we'll gather requirements as we go. -For integrated use, run `workflow-init` first for better context. - -Set mode: standalone + + No workflow status file found. Create UX Design can run standalone or as part of BMM planning workflow. + For standalone use, we'll gather requirements as we go. For integrated use, run `workflow-init` first for better context. + Set standalone_mode = true - - Store {{status_file_path}} for later updates - Store {{project_level}} for scoping decisions - Set mode: integrated + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "create-design" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) + + + ⚠️ UX Design already completed: {{create-design status}} + Re-running will overwrite the existing UX design. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + + ⚠️ Next expected workflow: {{next_workflow}}. UX Design is out of sequence. + Continue with UX Design anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + +Set standalone_mode = false +Store {{project_level}} for scoping decisions @@ -1116,12 +1130,16 @@ Based on your deployment intent: {{recommendation}} Save final document to {default_output_file} - - - mode: update - action: complete_workflow - workflow_name: create-ux-design - + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "create-design" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["create-design"] = "{default_output_file}" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS + + Find first non-completed workflow in workflow_status (next workflow to do) + Determine next agent from path file based on next workflow + 🎨 **One more thing!** Want to see your design come to life? diff --git a/src/modules/bmm/workflows/2-plan-workflows/gdd/instructions-gdd.md b/src/modules/bmm/workflows/2-plan-workflows/gdd/instructions-gdd.md index 9e6ad4bf..bf2e7a1d 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/gdd/instructions-gdd.md +++ b/src/modules/bmm/workflows/2-plan-workflows/gdd/instructions-gdd.md @@ -67,19 +67,27 @@ Use: `prd` - + - - mode: validate - calling_workflow: gdd - + + Check status of "gdd" workflow in loaded status file - - {{warning}} - Continue with GDD anyway? (y/n) - - {{suggestion}} - Exit workflow + + ⚠️ GDD already completed: {{gdd status}} + Re-running will overwrite the existing GDD. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + + ⚠️ Next expected workflow: {{next_workflow}}. GDD is out of sequence. + Continue with GDD anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + @@ -328,18 +336,23 @@ For each {{placeholder}} in the fragment, elicit and capture that information. - + - - mode: update - action: complete_workflow - workflow_name: gdd - populate_stories_from: {epics_output_file} - + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "gdd" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["gdd"] = "{output_folder}/bmm-gdd-{{game_name}}-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - Status updated! Next: {{next_workflow}} ({{next_agent}} agent) - Loaded {{total_stories}} stories from epics. +Parse {epics_output_file} to extract all stories +Populate story_sequence section in status file with story IDs +Set each story status to "not-started" +Loaded {{total_stories}} stories from epics into story sequence. + +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow +Next workflow: {{next_workflow}} ({{next_agent}} agent) diff --git a/src/modules/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md b/src/modules/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md index 218e9627..070410e5 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md +++ b/src/modules/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md @@ -10,20 +10,40 @@ If users mention gameplay mechanics, note them but keep focus on narrative Facilitate good brainstorming techniques throughout with the user, pushing them to come up with much of the narrative you will help weave together. The goal is for the user to feel that they crafted the narrative and story arc unless they push you to do it all or indicate YOLO - + +Check if {output_folder}/bmm-workflow-status.yaml exists - - mode: init-check - - - - Store {{status_file_path}} for later updates - Set tracking_mode = true + + No workflow status file found. Narrative workflow is optional - you can continue without status tracking. + Set standalone_mode = true - - Set tracking_mode = false - Note: Running without workflow tracking. Run `workflow-init` to enable progress tracking. + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "narrative" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) + + + ⚠️ Narrative Design Document already completed: {{narrative status}} + Re-running will overwrite the existing narrative document. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + + ⚠️ Next expected workflow: {{next_workflow}}. Narrative is out of sequence. + Continue with Narrative Design anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + +Set standalone_mode = false @@ -539,19 +559,50 @@ Which would you like? - + - - - mode: update - action: complete_workflow - workflow_name: narrative - + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "narrative" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["narrative"] = "{output_folder}/bmm-narrative-{{game_name}}-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - ✅ Status updated! Next: {{next_workflow}} - +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow - + +**✅ Narrative Design Complete, {user_name}!** + +**Narrative Document:** + +- Narrative design saved to {output_folder}/bmm-narrative-{{game_name}}-{{date}}.md + +{{#if standalone_mode != true}} +**Status Updated:** + +- Progress tracking updated: narrative marked complete +- Next workflow: {{next_workflow}} + {{else}} + **Note:** Running in standalone mode (no progress tracking) + {{/if}} + +**Next Steps:** + +{{#if standalone_mode != true}} + +- **Next workflow:** {{next_workflow}} ({{next_agent}} agent) +- **Optional:** Review narrative with writing team or stakeholders + +Check status anytime with: `workflow-status` +{{else}} +Since no workflow is in progress: + +- Review narrative design with team +- Refer to the BMM workflow guide if unsure what to do next +- Or run `workflow-init` to create a workflow path and get guided next steps + {{/if}} + + diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md b/src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md index 6b70f182..0f37e366 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md @@ -12,37 +12,27 @@ - + +Check if {output_folder}/bmm-workflow-status.yaml exists - - mode: data - data_request: project_config - - - - **Note: No Workflow Status File Found** - -The PRD workflow can run standalone or as part of the BMM workflow path. - -**Recommended:** Run `workflow-init` first for: - -- Project context tracking -- Workflow sequencing guidance -- Progress monitoring across workflows - -**Or continue standalone** without progress tracking. - -Continue in standalone mode or exit to run workflow-init? (continue/exit) - -Set standalone_mode = true - - -Exit workflow - + + No workflow status file found. PRD workflow can run standalone or as part of BMM workflow path. + **Recommended:** Run `workflow-init` first for project context tracking and workflow sequencing. + Continue in standalone mode or exit to run workflow-init? (continue/exit) + + Set standalone_mode = true + + + Exit workflow + - - Store {{status_file_path}} for later updates + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "prd" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) **Incorrect Workflow for Level {{project_level}}** @@ -54,32 +44,25 @@ PRD is for Level 2-4 projects. Level 0-1 should use tech-spec directly. Exit and redirect to tech-spec - - **Incorrect Workflow for Game Projects** - -Game projects should use GDD workflow instead of PRD. - -**Correct workflow:** `gdd` (PM agent) - -Exit and redirect to gdd - - - - - - - - mode: validate - calling_workflow: prd - - - - {{warning}} - Continue with PRD anyway? (y/n) - - {{suggestion}} - Exit workflow + + ⚠️ PRD already completed: {{prd status}} + Re-running will overwrite the existing PRD. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + ⚠️ Next expected workflow: {{next_workflow}}. PRD is out of sequence. + Continue with PRD anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + +Set standalone_mode = false @@ -409,18 +392,17 @@ For each epic from the epic list, expand with full story details: - + - - mode: update - action: complete_workflow - workflow_name: prd - populate_stories_from: {epics_output_file} - + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "prd" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["prd"] = "{default_output_file}" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - Status updated! Next: {{next_workflow}} ({{next_agent}} agent) - Loaded {{total_stories}} stories from epics. +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow **✅ PRD Workflow Complete, {user_name}!** diff --git a/src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md b/src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md index 6f743a18..d18da1e8 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md +++ b/src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md @@ -13,37 +13,27 @@ DOCUMENT OUTPUT: Technical, precise, definitive. Specific versions only. User skill level ({user_skill_level}) affects conversation style ONLY, not document content. - + +Check if {output_folder}/bmm-workflow-status.yaml exists - - mode: data - data_request: project_config - - - - **Note: No Workflow Status File Found** - -The tech-spec workflow can run standalone or as part of the BMM workflow path. - -**Recommended:** Run `workflow-init` first for: - -- Project context tracking -- Workflow sequencing guidance -- Progress monitoring across workflows - -**Or continue standalone** without progress tracking. - -Continue in standalone mode or exit to run workflow-init? (continue/exit) - -Set standalone_mode = true - - -Exit workflow - + + No workflow status file found. Tech-spec workflow can run standalone or as part of BMM workflow path. + **Recommended:** Run `workflow-init` first for project context tracking and workflow sequencing. + Continue in standalone mode or exit to run workflow-init? (continue/exit) + + Set standalone_mode = true + + + Exit workflow + - - Store {{status_file_path}} for later updates + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "tech-spec" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) **Incorrect Workflow for Level {{project_level}}** @@ -55,32 +45,25 @@ Tech-spec is for Level 0-1 projects. Level 2-4 should use PRD workflow. Exit and redirect to prd - - **Incorrect Workflow for Game Projects** - -Game projects should use GDD workflow instead of tech-spec. - -**Correct workflow:** `gdd` (PM agent) - -Exit and redirect to gdd - - - - - - - - mode: validate - calling_workflow: tech-spec - - - - {{warning}} - Continue with tech-spec anyway? (y/n) - - {{suggestion}} - Exit workflow + + ⚠️ Tech-spec already completed: {{tech-spec status}} + Re-running will overwrite the existing tech-spec. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + ⚠️ Next expected workflow: {{next_workflow}}. Tech-spec is out of sequence. + Continue with tech-spec anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + +Set standalone_mode = false @@ -232,24 +215,25 @@ Run cohesion validation? (y/n) ## Next Steps - - mode: update - action: complete_workflow - workflow_name: tech-spec - + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "tech-spec" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["tech-spec"] = "{output_folder}/bmm-tech-spec-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - Status updated! +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow **✅ Tech-Spec Complete, {user_name}!** **Deliverables Created:** - + - ✅ tech-spec.md - Technical specification - ✅ user-story.md - Single user story - + - ✅ tech-spec.md - Technical specification diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/instructions.md b/src/modules/bmm/workflows/3-solutioning/architecture/instructions.md index 4712c4bd..bc75782f 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/instructions.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/instructions.md @@ -10,37 +10,27 @@ Generate all documents in {document_output_language} This workflow replaces architecture with a conversation-driven approach - + +Check if {output_folder}/bmm-workflow-status.yaml exists - - mode: data - data_request: project_config - - - - **Note: No Workflow Status File Found** - -The Decision Architecture workflow can run standalone or as part of the BMM workflow path. - -**Recommended:** Run `workflow-init` first for: - -- Project context tracking -- Workflow sequencing guidance -- Progress monitoring across workflows - -**Or continue standalone** without progress tracking. - -Continue in standalone mode or exit to run workflow-init? (continue/exit) - -Set standalone_mode = true - - -Exit workflow - + + No workflow status file found. Decision Architecture can run standalone or as part of BMM workflow path. + **Recommended:** Run `workflow-init` first for project context tracking and workflow sequencing. + Continue in standalone mode or exit to run workflow-init? (continue/exit) + + Set standalone_mode = true + + + Exit workflow + - - Store {{status_file_path}} for later updates + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "create-architecture" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) **Note: Level {{project_level}} Project** @@ -50,23 +40,26 @@ Decision Architecture is typically for Level 3-4 projects, but can be used for a For Level {{project_level}}, we'll keep the architecture appropriately scoped. - - - - - - mode: validate - calling_workflow: architecture - - - - {{warning}} - Continue with Decision Architecture anyway? (y/n) - - {{suggestion}} - Exit workflow + + ⚠️ Architecture already completed: {{create-architecture status}} + Re-running will overwrite the existing architecture. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + ⚠️ Next expected workflow: {{next_workflow}}. Architecture is out of sequence. + Continue with Architecture anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + +Set standalone_mode = false Check for existing PRD and epics files using fuzzy matching @@ -663,20 +656,20 @@ Enforcement: "All agents MUST follow this pattern" Save document to {output_folder}/architecture.md - - mode: update - action: complete_workflow - workflow_name: architecture - + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "create-architecture" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["create-architecture"] = "{output_folder}/bmm-architecture-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - ✅ Decision Architecture workflow complete! - -Status updated. - + Find first non-completed workflow in workflow_status (next workflow to do) + Determine next agent from path file based on next workflow +✅ Decision Architecture workflow complete! + **Deliverables Created:** - ✅ architecture.md - Complete architectural decisions document diff --git a/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md b/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md index 641422b2..8849abc2 100644 --- a/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md +++ b/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md @@ -6,47 +6,53 @@ - - - mode: data - data_request: project_config - + +Check if {output_folder}/bmm-workflow-status.yaml exists - - **Note: No Workflow Status File Found** - -The Implementation Ready Check can run standalone or as part of the BMM workflow path. - -**Recommended:** Run `workflow-init` first for: - -- Project context tracking -- Workflow sequencing guidance -- Progress monitoring across workflows - -**Or continue standalone** without progress tracking. - -Continue in standalone mode or exit to run workflow-init? (continue/exit) - -Set standalone_mode = true - - -Exit workflow - + + No workflow status file found. Implementation Ready Check can run standalone or as part of BMM workflow path. + **Recommended:** Run `workflow-init` first for project context tracking and workflow sequencing. + Continue in standalone mode or exit to run workflow-init? (continue/exit) + + Set standalone_mode = true + + + Exit workflow + - - Store {{status_file_path}} for later updates - Store {{project_level}}, {{active_path}}, and {{workflow_phase}} for validation context + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Parse workflow_status section + Check status of "solutioning-gate-check" workflow + Get project_level from YAML metadata + Find first non-completed workflow (next expected workflow) -Based on the project_level, understand what artifacts should exist: +Based on the project_level, understand what artifacts should exist: - Level 0-1: Tech spec and simple stories only (no PRD, minimal solutioning) - Level 2: PRD, tech spec, epics/stories (no separate architecture doc) - Level 3-4: Full suite - PRD, architecture document, epics/stories, possible UX artifacts + -- Level 0-1: Tech spec and simple stories only (no PRD, minimal solutioning) -- Level 2: PRD, tech spec, epics/stories (no separate architecture doc) -- Level 3-4: Full suite - PRD, architecture document, epics/stories, possible UX artifacts - + + ⚠️ Gate check already completed: {{solutioning-gate-check status}} + Re-running will create a new validation report. Continue? (y/n) + + Exiting. Use workflow-status to see your next step. + Exit workflow + + + + + ⚠️ Next expected workflow: {{next_workflow}}. Gate check is out of sequence. + Continue with gate check anyway? (y/n) + + Exiting. Run {{next_workflow}} instead. + Exit workflow + + + +Set standalone_mode = false + The validation approach must adapt to the project level - don't look for documents that shouldn't exist at lower levels - project_context @@ -249,23 +255,48 @@ The Implementation Ready Check can run standalone or as part of the BMM workflow readiness_assessment - -The readiness assessment is complete. Would you like to update the workflow status to proceed to the next phase? [yes/no] + + + Load the FULL file: {output_folder}/bmm-workflow-status.yaml + Find workflow_status key "solutioning-gate-check" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status["solutioning-gate-check"] = "{output_folder}/bmm-readiness-assessment-{{date}}.md" + Save file, preserving ALL comments and structure including STATUS DEFINITIONS -Note: This will advance the project workflow to the next phase in your current path. +Find first non-completed workflow in workflow_status (next workflow to do) +Determine next agent from path file based on next workflow + - -Determine the next workflow phase based on current status: -- If Level 0-1: Advance to implementation phase -- If Level 2-4 in solutioning: Advance to Phase 4 (Implementation) -- Update the workflow status configuration accordingly -- Confirm the update with the user - +**✅ Implementation Ready Check Complete!** - -Acknowledge that the workflow status remains unchanged. -Remind user they can manually update when ready. - +**Assessment Report:** + +- Readiness assessment saved to: {output_folder}/bmm-readiness-assessment-{{date}}.md + +{{#if standalone_mode != true}} +**Status Updated:** + +- Progress tracking updated: solutioning-gate-check marked complete +- Next workflow: {{next_workflow}} + {{else}} + **Note:** Running in standalone mode (no progress tracking) + {{/if}} + +**Next Steps:** + +{{#if standalone_mode != true}} + +- **Next workflow:** {{next_workflow}} ({{next_agent}} agent) +- Review the assessment report and address any critical issues before proceeding + +Check status anytime with: `workflow-status` +{{else}} +Since no workflow is in progress: + +- Refer to the BMM workflow guide if unsure what to do next +- Or run `workflow-init` to create a workflow path and get guided next steps + {{/if}} + status_update_result diff --git a/src/modules/bmm/workflows/4-implementation/create-story/instructions.md b/src/modules/bmm/workflows/4-implementation/create-story/instructions.md index 1e9182a8..a98bb2c0 100644 --- a/src/modules/bmm/workflows/4-implementation/create-story/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/create-story/instructions.md @@ -234,6 +234,7 @@ You may need to run sprint-planning to refresh tracking, or manually set the sto **✅ Story Created Successfully, {user_name}!** **Story Details:** + - Story ID: {{story_id}} - Story Key: {{story_key}} - File: {{story_file}} @@ -242,6 +243,7 @@ You may need to run sprint-planning to refresh tracking, or manually set the sto **⚠️ Important:** The following workflows are context-intensive. It's recommended to clear context and restart the SM agent before running the next command. **Next Steps:** + 1. Review the drafted story in {{story_file}} 2. **[RECOMMENDED]** Run `story-context` to generate technical context XML and mark story ready for development (combines context + ready in one step) 3. Or run `story-ready` to manually mark the story ready without generating technical context diff --git a/src/modules/bmm/workflows/4-implementation/story-context/instructions.md b/src/modules/bmm/workflows/4-implementation/story-context/instructions.md index d38ea30b..0d2a298f 100644 --- a/src/modules/bmm/workflows/4-implementation/story-context/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/story-context/instructions.md @@ -178,12 +178,14 @@ You may need to run sprint-planning to refresh tracking. ✅ Story context generated successfully, {user_name}! **Story Details:** + - Story: {{epic_id}}.{{story_id}} - {{story_title}} - Story Key: {{story_key}} - Context File: {default_output_file} - Status: drafted → ready-for-dev **Context Includes:** + - Documentation artifacts and references - Existing code and interfaces - Dependencies and frameworks @@ -191,6 +193,7 @@ You may need to run sprint-planning to refresh tracking. - Development constraints **Next Steps:** + 1. Review the context file: {default_output_file} 2. Run `dev-story` to implement the story 3. Generate context for more drafted stories if needed diff --git a/src/modules/bmm/workflows/workflow-status/README.md b/src/modules/bmm/workflows/workflow-status/README.md index 05735ecc..55d520bf 100644 --- a/src/modules/bmm/workflows/workflow-status/README.md +++ b/src/modules/bmm/workflows/workflow-status/README.md @@ -19,7 +19,7 @@ The workflow status system provides: workflow-status/ ├── workflow.yaml # Main configuration ├── instructions.md # Status checker (99 lines) -├── workflow-status-template.md # Clean key-value template +├── workflow-status-template.yaml # Clean YAML status template ├── project-levels.yaml # Source of truth for scale definitions └── paths/ # Modular workflow definitions ├── greenfield-level-0.yaml through level-4.yaml @@ -61,25 +61,44 @@ workflow-init/ ## Status File Format -Simple key-value pairs for instant parsing: +Clean YAML format with all workflows listed up front: -```markdown -PROJECT_NAME: MyProject -PROJECT_TYPE: software -PROJECT_LEVEL: 2 -FIELD_TYPE: greenfield -CURRENT_PHASE: 2-Planning -CURRENT_WORKFLOW: prd -NEXT_ACTION: Continue PRD -NEXT_COMMAND: prd -NEXT_AGENT: pm +```yaml +# generated: 2025-10-29 +# project: MyProject +# project_type: software +# project_level: 2 +# field_type: greenfield +# workflow_path: greenfield-level-2.yaml + +workflow_status: + # Phase 1: Analysis + brainstorm-project: optional + research: optional + product-brief: recommended + + # Phase 2: Planning + prd: docs/prd.md + validate-prd: optional + create-design: conditional + + # Phase 3: Solutioning + create-architecture: required + validate-architecture: optional + solutioning-gate-check: required ``` -Any agent can instantly grep what they need: +**Status Values:** -- Any: `grep 'NEXT_ACTION:' status.md` -- Any: `grep 'CURRENT_PHASE:' status.md` -- Any: `grep 'NEXT_COMMAND:' status.md` +- `required` / `optional` / `recommended` / `conditional` - Not yet started +- `{file-path}` - Completed (e.g., `docs/prd.md`) +- `skipped` - Optional workflow that was skipped + +Any agent can instantly parse what they need: + +- Read YAML to see all workflows and their status +- Check which workflows are completed vs pending +- Auto-detect existing work by scanning for output files ## Project Levels @@ -213,10 +232,10 @@ Other workflows read the status to coordinate: **Phase 4 (Implementation):** - workflow-status only tracks sprint-planning completion -- After sprint-planning, all story/epic tracking happens in the sprint plan output file +- After sprint-planning, all story/epic tracking happens in sprint-status.yaml - Phase 4 workflows do NOT read/write workflow-status (except sprint-planning for prerequisite verification) -The status file is the single source of truth for Phases 1-3 and the hub that keeps all agents synchronized. +The workflow-status.yaml file is the single source of truth for Phases 1-3, and sprint-status.yaml takes over for Phase 4 implementation tracking. ## Benefits diff --git a/src/modules/bmm/workflows/workflow-status/init/instructions.md b/src/modules/bmm/workflows/workflow-status/init/instructions.md index 4bd7837d..26b7c66d 100644 --- a/src/modules/bmm/workflows/workflow-status/init/instructions.md +++ b/src/modules/bmm/workflows/workflow-status/init/instructions.md @@ -261,36 +261,129 @@ Here's the complexity scale for reference: workflow_path_file - -Build workflow from loaded path file -Display phases and workflows -Set initial values for status file + +Parse the loaded workflow path file and extract all workflows -current_phase -current_workflow -current_agent -next_action -next_command -next_agent +For each phase in the path file: + +- Extract phase number and name +- Extract all workflows in that phase +- For each workflow, determine its status type: + - required: true → status = "required" + - recommended: true → status = "recommended" + - conditional: "if_has_ui" → status = "conditional" + - optional: true → status = "optional" + - Default if not specified → status = "required" + + +Build the workflow_items list in this format: + +For each phase: + +1. Add comment header: ` # Phase {n}: {Phase Name}` +2. For each workflow in phase: + - Add entry: ` {workflow-id}: {status}` +3. Add blank line between phases + +Example structure: + +``` + # Phase 1: Analysis + brainstorm-project: optional + research: optional + product-brief: recommended + + # Phase 2: Planning + prd: required + validate-prd: optional + create-design: conditional +``` + + + +Scan for existing workflow output files to auto-detect completion: + +For each workflow in the list, check common output locations: + +- {output_folder}/brainstorm-\*.md for brainstorm-project +- {output_folder}/research-\*.md for research +- {output_folder}/product-brief.md for product-brief +- {output_folder}/prd.md for prd +- {output_folder}/ux-design.md for create-design +- {output_folder}/architecture.md for create-architecture +- {output_folder}/tech-spec.md for tech-spec +- {output_folder}/sprint-status.yaml for sprint-planning + +CRITICAL: If file exists, replace status with ONLY the file path - nothing else. +Example: product-brief: docs/product-brief.md +NOT: product-brief: "completed - docs/product-brief.md" or any other text. + + +workflow_items - -Initialize all status values -start_date -last_updated -phase_1_complete -phase_2_complete -phase_3_complete -phase_4_complete + +Set generated date to current date +generated + +Prepare all template variables for workflow-status-template.yaml: + +- generated: {current_date} +- project_name: {project_name} +- project_type: {project_type} +- project_level: {project_level} +- field_type: {field_type} +- workflow_path_file: {workflow_path_file} +- workflow_items: {workflow_items from step 5} + + +Display a preview of what will be created: + +Show the first workflow in each phase and total count: + +"Ready to create workflow status tracking: + +- Phase 1 ({phase_1_workflow_count} workflows): Starting with {first_workflow_phase_1} +- Phase 2 ({phase_2_workflow_count} workflows): Starting with {first_workflow_phase_2} +- Phase 3 ({phase_3_workflow_count} workflows): Starting with {first_workflow_phase_3} +- Phase 4 (Implementation tracked separately in sprint-status.yaml) + +{{#if detected_completed_workflows}} +Found existing work: +{{#each detected_files}} + +- {{workflow_name}}: {{file_path}} + {{/each}} + {{/if}}" + Ready to create your workflow status file? (y/n) - Save status file to {output_folder}/bmm-workflow-status.md - ✅ Status file created! Next up: {{next_agent}} agent, run `{{next_command}}` - - It is strongly recommended to clear the context or start a new chat and load the next agent to execute the next command from that agents help menu, unless there is something else I can do for you first. - + Generate YAML from workflow-status-template.yaml with all variables + Save status file to {output_folder}/bmm-workflow-status.yaml + +Identify the first non-completed workflow in the list +Look up that workflow's agent and command from the path file + +✅ Workflow status file created at {output_folder}/bmm-workflow-status.yaml + +**Next Steps:** + +{{#if detected_completed_workflows}} +You have {{detected_count}} workflow(s) already completed. Great progress! +{{/if}} + +**Next Workflow:** {{next_workflow_name}} + +**Agent:** {{next_agent}} + +**Command:** /bmad:bmm:workflows:{{next_workflow_id}} + +{{#if next_agent !== 'pm'}} +It is recommended to start a new chat and load the {{next_agent}} agent before running the next workflow. +{{/if}} + diff --git a/src/modules/bmm/workflows/workflow-status/init/workflow.yaml b/src/modules/bmm/workflows/workflow-status/init/workflow.yaml index 0db36cc5..f28e5216 100644 --- a/src/modules/bmm/workflows/workflow-status/init/workflow.yaml +++ b/src/modules/bmm/workflows/workflow-status/init/workflow.yaml @@ -16,13 +16,13 @@ date: system-generated # Workflow components installed_path: "{project-root}/bmad/bmm/workflows/workflow-status/init" instructions: "{installed_path}/instructions.md" -template: "{project-root}/bmad/bmm/workflows/workflow-status/workflow-status-template.md" +template: "{project-root}/bmad/bmm/workflows/workflow-status/workflow-status-template.yaml" # Path data files path_files: "{project-root}/bmad/bmm/workflows/workflow-status/paths/" # Output configuration -default_output_file: "{output_folder}/bmm-workflow-status.md" +default_output_file: "{output_folder}/bmm-workflow-status.yaml" standalone: true web_bundle: false diff --git a/src/modules/bmm/workflows/workflow-status/instructions.md b/src/modules/bmm/workflows/workflow-status/instructions.md index 99a569d4..45fe762c 100644 --- a/src/modules/bmm/workflows/workflow-status/instructions.md +++ b/src/modules/bmm/workflows/workflow-status/instructions.md @@ -33,7 +33,7 @@ -Search {output_folder}/ for file: bmm-workflow-status.md +Search {output_folder}/ for file: bmm-workflow-status.yaml No workflow status found. To get started: @@ -50,51 +50,66 @@ This will guide you through project setup and create your workflow path. -Read bmm-workflow-status.md -Extract key-value pairs from status file: +Read bmm-workflow-status.yaml +Parse YAML file and extract metadata from comments and fields: -Parse these fields: +Parse these fields from YAML comments and metadata: -- PROJECT_NAME -- PROJECT_TYPE -- PROJECT_LEVEL -- FIELD_TYPE -- CURRENT_PHASE -- CURRENT_WORKFLOW -- NEXT_ACTION -- NEXT_COMMAND -- NEXT_AGENT +- project (from YAML field) +- project_type (from YAML field) +- project_level (from YAML field) +- field_type (from YAML field) +- workflow_path (from YAML field) + +Parse workflow_status section: + +- Extract all workflow entries with their statuses +- Identify completed workflows (status = file path) +- Identify pending workflows (status = required/optional/recommended/conditional) +- Identify skipped workflows (status = skipped) + +Determine current state: + +- Find first workflow with status != file path and != skipped +- This is the NEXT workflow to work on +- Look up agent and command from workflow path file -Load workflow path file to check for optional steps -Check if current workflow is in progress or complete +Load workflow path file based on workflow_path field +Identify current phase from next workflow to be done +Build list of completed, pending, and optional workflows ## 📊 Current Status -**Project:** {{PROJECT_NAME}} (Level {{PROJECT_LEVEL}} {{PROJECT_TYPE}}) -**Phase:** {{CURRENT_PHASE}} -**Current Workflow:** {{CURRENT_WORKFLOW}} +**Project:** {{project}} (Level {{project_level}} {{project_type}}) -## 🎯 Your Options +**Path:** {{workflow_path}} -{{#if CURRENT_WORKFLOW != "complete"}} -**Continue in progress:** +**Progress:** -- {{CURRENT_WORKFLOW}} ({{CURRENT_AGENT}} agent) - {{/if}} +{{#each phases}} +{{phase_name}}: +{{#each workflows_in_phase}} -**Next required step:** +- {{workflow_name}}: {{status_display}} + {{/each}} + {{/each}} -- Command: `{{NEXT_COMMAND}}` -- Agent: {{NEXT_AGENT}} +## 🎯 Next Steps + +**Next Workflow:** {{next_workflow_name}} + +**Agent:** {{next_agent}} + +**Command:** /bmad:bmm:workflows:{{next_workflow_id}} {{#if optional_workflows_available}} -**Optional workflows available:** +**Optional Workflows Available:** {{#each optional_workflows}} -- {{workflow_name}} ({{agent}}) +- {{workflow_name}} ({{agent}}) - {{status}} {{/each}} {{/if}} @@ -103,20 +118,69 @@ Parse these fields: What would you like to do? -{{#if CURRENT_WORKFLOW != "complete"}} - -1. **Continue current** - Resume {{CURRENT_WORKFLOW}} - {{/if}} -2. **Next required** - {{NEXT_COMMAND}} +1. **Start next workflow** - {{next_workflow_name}} ({{next_agent}} agent) {{#if optional_workflows_available}} -3. **Optional workflow** - Choose from available options +2. **Run optional workflow** - Choose from available options {{/if}} -4. **View full status** - See complete status file +3. **View full status YAML** - See complete status file +4. **Update workflow status** - Mark a workflow as completed or skipped 5. **Exit** - Return to agent Your choice: Handle user selection based on available options + + + Ready to run {{next_workflow_name}}! + +**Command:** /bmad:bmm:workflows:{{next_workflow_id}} + +**Agent:** Load {{next_agent}} agent first + +{{#if next_agent !== current_agent}} +Tip: Start a new chat and load the {{next_agent}} agent before running this workflow. +{{/if}} + + + + + Which optional workflow? +{{#each optional_workflows numbered}} +{{number}}. {{workflow_name}} ({{agent}}) +{{/each}} + +Your choice: +Display selected workflow command and agent + + + + Display complete bmm-workflow-status.yaml file contents + + + + What would you like to update? + +1. Mark a workflow as **completed** (provide file path) +2. Mark a workflow as **skipped** + +Your choice: + + + Which workflow? (Enter workflow ID like 'prd' or 'create-architecture') + File path created? (e.g., docs/prd.md) + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow_status in YAML file: {{workflow_id}}: {{file_path}} + Save updated YAML file preserving ALL structure and comments + ✅ Updated {{workflow_id}} to completed: {{file_path}} + + + + Which workflow to skip? (Enter workflow ID) + Update workflow_status in YAML file: {{workflow_id}}: skipped + Save updated YAML file + ✅ Marked {{workflow_id}} as skipped + + @@ -124,7 +188,7 @@ Your choice: -Read {output_folder}/bmm-workflow-status.md if exists +Read {output_folder}/bmm-workflow-status.yaml if exists status_exists = false @@ -135,23 +199,16 @@ Your choice: - Parse status file fields - Load workflow path file from WORKFLOW_PATH field - Check if {{calling_workflow}} matches CURRENT_WORKFLOW or NEXT_COMMAND + Parse YAML file to extract project metadata and workflow_status + Load workflow path file from workflow_path field + Find first non-completed workflow in workflow_status (next workflow) + Check if {{calling_workflow}} matches next workflow or is in the workflow list status_exists = true -current_phase = {{CURRENT_PHASE}} -current_workflow = {{CURRENT_WORKFLOW}} -next_workflow = {{NEXT_COMMAND}} -project_level = {{PROJECT_LEVEL}} -project_type = {{PROJECT_TYPE}} -field_type = {{FIELD_TYPE}} - - - should_proceed = true - warning = "" - suggestion = "Resuming {{current_workflow}}" - +project_level = {{project_level}} +project_type = {{project_type}} +field_type = {{field_type}} +next_workflow = {{next_workflow_id}} should_proceed = true @@ -159,16 +216,22 @@ Your choice: suggestion = "Proceeding with planned next step" - - Check if calling_workflow is in optional workflows list + + Check the status of calling_workflow in YAML - + + should_proceed = true + warning = "⚠️ Workflow already completed: {{calling_workflow}}" + suggestion = "This workflow was already completed. Re-running will overwrite: {{status}}" + + + should_proceed = true warning = "Running optional workflow {{calling_workflow}}" suggestion = "This is optional. Expected next: {{next_workflow}}" - + should_proceed = true warning = "⚠️ Out of sequence: Expected {{next_workflow}}, running {{calling_workflow}}" suggestion = "Consider running {{next_workflow}} instead, or continue if intentional" @@ -176,14 +239,20 @@ Your choice: -status_file_path = {{path to bmm-workflow-status.md}} + + should_proceed = true + warning = "⚠️ Unknown workflow: {{calling_workflow}} not in workflow path" + suggestion = "This workflow is not part of the defined path for this project" + + +status_file_path = {{path to bmm-workflow-status.yaml}} Return control to calling workflow with all template outputs -Read {output_folder}/bmm-workflow-status.md if exists +Read {output_folder}/bmm-workflow-status.yaml if exists status_exists = false @@ -192,37 +261,46 @@ Your choice: - Parse status file completely + Parse YAML file completely status_exists = true - project_name = {{PROJECT_NAME}} - project_type = {{PROJECT_TYPE}} - project_level = {{PROJECT_LEVEL}} - field_type = {{FIELD_TYPE}} - workflow_path = {{WORKFLOW_PATH}} + project_name = {{project}} + project_type = {{project_type}} + project_level = {{project_level}} + field_type = {{field_type}} + workflow_path = {{workflow_path}} - - current_phase = {{CURRENT_PHASE}} - phase_1_complete = {{PHASE_1_COMPLETE}} - phase_2_complete = {{PHASE_2_COMPLETE}} - phase_3_complete = {{PHASE_3_COMPLETE}} - phase_4_complete = {{PHASE_4_COMPLETE}} + + Parse workflow_status section and return all workflow: status pairs + workflow_status = {{workflow_status_object}} + Calculate completion stats: + total_workflows = {{count all workflows}} + completed_workflows = {{count file path statuses}} + pending_workflows = {{count required/optional/etc}} + skipped_workflows = {{count skipped}} Return all parsed fields as template outputs + project = {{project}} + project_type = {{project_type}} + project_level = {{project_level}} + field_type = {{field_type}} + workflow_path = {{workflow_path}} + workflow_status = {{workflow_status_object}} + generated = {{generated}} -status_file_path = {{path to bmm-workflow-status.md}} +status_file_path = {{path to bmm-workflow-status.yaml}} Return control to calling workflow with requested data -Check if {output_folder}/bmm-workflow-status.md exists +Check if {output_folder}/bmm-workflow-status.yaml exists status_exists = true @@ -238,7 +316,7 @@ Your choice: -Read {output_folder}/bmm-workflow-status.md +Read {output_folder}/bmm-workflow-status.yaml success = false @@ -247,64 +325,48 @@ Your choice: - Parse all current values from status file - Load workflow path file from WORKFLOW_PATH field + Parse YAML file completely + Load workflow path file from workflow_path field Check {{action}} parameter to determine update type - Get {{workflow_name}} parameter (required) + Get {{workflow_id}} parameter (required) + Get {{output_file}} parameter (required - path to created file) - Mark workflow complete: - - Update CURRENT_WORKFLOW to "{{workflow_name}} - Complete" + ONLY write the file path as the status value - no other text, notes, or metadata + Update workflow status in YAML: + - In workflow_status section, update: {{workflow_id}}: {{output_file}} - Find {{workflow_name}} in loaded path YAML + Find {{workflow_id}} in loaded path YAML Determine next workflow from path sequence + Find first workflow in workflow_status with status != file path and != skipped - Update Next Action fields: - - NEXT_ACTION: Description from next workflow in path - - NEXT_COMMAND: Command for next workflow - - NEXT_AGENT: Agent for next workflow - - CURRENT_WORKFLOW: Set to next workflow name (or "Complete" if no more) - - CURRENT_AGENT: Set to next agent - - Check if phase complete: - - If {{workflow_name}} is last required workflow in current phase - - Update PHASE_X_COMPLETE to true - - Update CURRENT_PHASE to next phase (if applicable) - - Update LAST_UPDATED to {{date}} - Save status file + Save updated YAML file preserving ALL structure and comments success = true next_workflow = {{determined next workflow}} - next_agent = {{determined next agent}} - phase_complete = {{true/false}} + next_agent = {{determined next agent from path file}} + completed_workflow = {{workflow_id}} + output_file = {{output_file}} - + - - Get {{workflow_name}} parameter (required) - Get {{agent_name}} parameter (optional) + + Get {{workflow_id}} parameter (required) - Update current workflow: - - CURRENT_WORKFLOW: {{workflow_name}} - - CURRENT_AGENT: {{agent_name or infer from path}} + Update workflow status in YAML: + - In workflow_status section, update: {{workflow_id}}: skipped - Find {{workflow_name}} in path to determine next: - - NEXT_ACTION: Next workflow description - - NEXT_COMMAND: Next workflow command - - NEXT_AGENT: Next workflow agent - - Update LAST_UPDATED to {{date}} - Save status file + Save updated YAML file success = true + skipped_workflow = {{workflow_id}} @@ -313,7 +375,7 @@ Your choice: success = false - error = "Unknown action: {{action}}. Valid actions: complete_workflow, set_current_workflow" + error = "Unknown action: {{action}}. Valid actions: complete_workflow, skip_workflow" diff --git a/src/modules/bmm/workflows/workflow-status/sample-level-3-workflow.yaml b/src/modules/bmm/workflows/workflow-status/sample-level-3-workflow.yaml new file mode 100644 index 00000000..2f91ad31 --- /dev/null +++ b/src/modules/bmm/workflows/workflow-status/sample-level-3-workflow.yaml @@ -0,0 +1,49 @@ +# Workflow Status Template +# This tracks progress through phases 1-3 of the BMM methodology +# Phase 4 (Implementation) is tracked separately in sprint-status.yaml + +# generated: 2025-10-29 +# project: Enterprise Customer Portal +# project_type: software +# project_level: 3 +# field_type: greenfield +# workflow_path: greenfield-level-3.yaml + +# STATUS DEFINITIONS: +# ================== +# Initial Status (before completion): +# - required: Must be completed to progress +# - optional: Can be completed but not required +# - recommended: Strongly suggested but not required +# - conditional: Required only if certain conditions met (e.g., if_has_ui) +# +# Completion Status: +# - {file-path}: File created/found (e.g., "docs/product-brief.md") +# - skipped: Optional/conditional workflow that was skipped + +generated: 2025-10-29 +project: Enterprise Customer Portal +project_type: software +project_level: 3 +field_type: greenfield +workflow_path: greenfield-level-3.yaml + +workflow_status: + # Phase 1: Analysis + brainstorm-project: docs/brainstorm-session-2025-10-15.md + research: docs/research-api-patterns.md + product-brief: docs/product-brief.md + + # Phase 2: Planning + prd: docs/prd.md + validate-prd: skipped + create-design: docs/ux-design.md + + # Phase 3: Solutioning + create-architecture: required + validate-architecture: optional + solutioning-gate-check: recommended + + # Phase 4: Implementation + sprint-planning: required + # Note: Subsequent implementation workflows tracked in sprint-status.yaml diff --git a/src/modules/bmm/workflows/workflow-status/workflow-status-template.md b/src/modules/bmm/workflows/workflow-status/workflow-status-template.md deleted file mode 100644 index d7384008..00000000 --- a/src/modules/bmm/workflows/workflow-status/workflow-status-template.md +++ /dev/null @@ -1,30 +0,0 @@ -# BMM Workflow Status - -## Project Configuration - -PROJECT_NAME: {{project_name}} -PROJECT_TYPE: {{project_type}} -PROJECT_LEVEL: {{project_level}} -FIELD_TYPE: {{field_type}} -START_DATE: {{start_date}} -WORKFLOW_PATH: {{workflow_path_file}} - -## Current State - -CURRENT_PHASE: {{current_phase}} -CURRENT_WORKFLOW: {{current_workflow}} -CURRENT_AGENT: {{current_agent}} -PHASE_1_COMPLETE: {{phase_1_complete}} -PHASE_2_COMPLETE: {{phase_2_complete}} -PHASE_3_COMPLETE: {{phase_3_complete}} -PHASE_4_COMPLETE: {{phase_4_complete}} - -## Next Action - -NEXT_ACTION: {{next_action}} -NEXT_COMMAND: {{next_command}} -NEXT_AGENT: {{next_agent}} - ---- - -_Last Updated: {{last_updated}}_ diff --git a/src/modules/bmm/workflows/workflow-status/workflow-status-template.yaml b/src/modules/bmm/workflows/workflow-status/workflow-status-template.yaml new file mode 100644 index 00000000..d9ab4d69 --- /dev/null +++ b/src/modules/bmm/workflows/workflow-status/workflow-status-template.yaml @@ -0,0 +1,31 @@ +# Workflow Status Template +# This tracks progress through phases 1-3 of the BMM methodology +# Phase 4 (Implementation) is tracked separately in sprint-status.yaml + +# generated: {{generated}} +# project: {{project_name}} +# project_type: {{project_type}} +# project_level: {{project_level}} +# field_type: {{field_type}} +# workflow_path: {{workflow_path_file}} + +# STATUS DEFINITIONS: +# ================== +# Initial Status (before completion): +# - required: Must be completed to progress +# - optional: Can be completed but not required +# - recommended: Strongly suggested but not required +# - conditional: Required only if certain conditions met (e.g., if_has_ui) +# +# Completion Status: +# - {file-path}: File created/found (e.g., "docs/product-brief.md") +# - skipped: Optional/conditional workflow that was skipped + +generated: "{{generated}}" +project: "{{project_name}}" +project_type: "{{project_type}}" +project_level: "{{project_level}}" +field_type: "{{field_type}}" +workflow_path: "{{workflow_path_file}}" + +workflow_status: "{{workflow_items}}" diff --git a/src/modules/bmm/workflows/workflow-status/workflow.yaml b/src/modules/bmm/workflows/workflow-status/workflow.yaml index 8a912b81..6773233e 100644 --- a/src/modules/bmm/workflows/workflow-status/workflow.yaml +++ b/src/modules/bmm/workflows/workflow-status/workflow.yaml @@ -1,6 +1,6 @@ # Workflow Status - Master Router and Status Tracker name: workflow-status -description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads simple key-value status file for instant parsing. Use workflow-init for new projects.' +description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.' author: "BMad" # Critical variables from config @@ -17,13 +17,13 @@ installed_path: "{project-root}/bmad/bmm/workflows/workflow-status" instructions: "{installed_path}/instructions.md" # Template for status file creation (used by workflow-init) -template: "{installed_path}/workflow-status-template.md" +template: "{installed_path}/workflow-status-template.yaml" # Path definitions for project types path_files: "{installed_path}/paths/" # Output configuration - reads existing status -default_output_file: "{output_folder}/bmm-workflow-status.md" +default_output_file: "{output_folder}/bmm-workflow-status.yaml" standalone: true diff --git a/src/modules/cis/workflows/storytelling/instructions.md b/src/modules/cis/workflows/storytelling/instructions.md index 85148d18..ed8f703b 100644 --- a/src/modules/cis/workflows/storytelling/instructions.md +++ b/src/modules/cis/workflows/storytelling/instructions.md @@ -50,9 +50,17 @@ I can help craft your story using these proven narrative frameworks: 3. **Customer Journey Story** - Before/after transformation narrative 4. **Challenge-Overcome Arc** - Dramatic obstacle-to-victory structure -**Strategic Narratives:** 5. **Brand Story** - Values, mission, and unique positioning 6. **Pitch Narrative** - Persuasive problem-to-solution structure 7. **Vision Narrative** - Future-focused aspirational story 8. **Origin Story** - Foundational narrative of how it began +**Strategic Narratives:** -**Specialized Narratives:** 9. **Data Storytelling** - Transform insights into compelling narrative 10. **Emotional Hooks** - Craft powerful opening and touchpoints +5. **Brand Story** - Values, mission, and unique positioning +6. **Pitch Narrative** - Persuasive problem-to-solution structure +7. **Vision Narrative** - Future-focused aspirational story +8. **Origin Story** - Foundational narrative of how it began + +**Specialized Narratives:** + +9. **Data Storytelling** - Transform insights into compelling narrative +10. **Emotional Hooks** - Craft powerful opening and touchpoints Which framework best fits your purpose? (Enter 1-10, or ask for my recommendation)