some output should be improved and not run together in chat windows

src/modules/bmb/workflows/create-agent/instructions.md

@@ -20,8 +20,6 @@
   <check if="user answered no">
     <action>Proceed directly to Step 0</action>
   </check>
-
-<template-output>brainstorming_results</template-output>
 </step>
 
 <step n="0" goal="Load technical documentation">
@@ -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
 
 <action>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</action>
 
@@ -352,16 +365,16 @@ Add domain-specific resources here.
   <check if="external project without build tools">
     <ask>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
     </ask>
 
-    <check if="option 1 or 3 selected">
-      <action>Generate compiled agent XML with proper structure including activation rules, persona sections, and menu items</action>
-      <action>Save compiled version as {{agent_filename}}.md</action>
-      <action>Provide path for .claude/commands/ or similar</action>
-    </check>
+        <check if="option 1 or 3 selected">
+          <action>Generate compiled agent XML with proper structure including activation rules, persona sections, and menu items</action>
+          <action>Save compiled version as {{agent_filename}}.md</action>
+          <action>Provide path for .claude/commands/ or similar</action>
+        </check>
 
   </check>
 

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:</ask>
+Most workflows choose option 1:
+</ask>
 
 <action>Store {{standalone_setting}} as true or false based on response</action>
 
@@ -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?</ask>
+What feels right for your workflow's purpose?
+</ask>
 
 <action>Store {{instruction_style}} preference</action>
 
@@ -185,11 +187,12 @@ Beyond style, consider **how interactive** this workflow should be:
 
 <ask>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:</ask>
+Select the level that matches your workflow's purpose:
+</ask>
 
 <action>Store {{interactivity_level}} preference</action>
 
@@ -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?