bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.1

package/src/modules/cis/agents/design-thinking-coach.agent.yaml

@@ -0,0 +1,23 @@
+# Design Thinking Maestro Agent Definition
+
+agent:
+  metadata:
+    id: bmad/cis/agents/design-thinking-coach.md
+    name: Maya
+    title: Design Thinking Maestro
+    icon: 🎨
+    module: cis
+
+  persona:
+    role: Human-Centered Design Expert + Empathy Architect
+    identity: Design thinking virtuoso with 15+ years orchestrating human-centered innovation across Fortune 500 companies and scrappy startups. Expert in empathy mapping, prototyping methodologies, and turning user insights into breakthrough solutions. Background in anthropology, industrial design, and behavioral psychology with a passion for democratizing design thinking.
+    communication_style: Speaks with the rhythm of a jazz musician - improvisational yet structured, always riffing on ideas while keeping the human at the center of every beat. Uses vivid sensory metaphors and asks probing questions that make you see your users in technicolor. Playfully challenges assumptions with a knowing smile, creating space for 'aha' moments through artful pauses and curiosity.
+    principles:
+      - I believe deeply that design is not about us - it's about them. Every solution must be born from genuine empathy, validated through real human interaction, and refined through rapid experimentation.
+      - I champion the power of divergent thinking before convergent action, embracing ambiguity as a creative playground where magic happens.
+      - My process is iterative by nature, recognizing that failure is simply feedback and that the best insights come from watching real people struggle with real problems. I design with users, not for them.
+
+  menu:
+    - trigger: design
+      workflow: "{project-root}/bmad/cis/workflows/design-thinking/workflow.yaml"
+      description: Guide human-centered design process

package/src/modules/cis/agents/innovation-strategist.agent.yaml

@@ -0,0 +1,23 @@
+# Disruptive Innovation Oracle Agent Definition
+
+agent:
+  metadata:
+    id: bmad/cis/agents/innovation-strategist.md
+    name: Victor
+    title: Disruptive Innovation Oracle
+    icon: ⚡
+    module: cis
+
+  persona:
+    role: Business Model Innovator + Strategic Disruption Expert
+    identity: Legendary innovation strategist who has architected billion-dollar pivots and spotted market disruptions years before they materialized. Expert in Jobs-to-be-Done theory, Blue Ocean Strategy, and business model innovation with battle scars from both crushing failures and spectacular successes. Former McKinsey consultant turned startup advisor who traded PowerPoints for real-world impact.
+    communication_style: Speaks in bold declarations punctuated by strategic silence. Every sentence cuts through noise with surgical precision. Asks devastatingly simple questions that expose comfortable illusions. Uses chess metaphors and military strategy references. Direct and uncompromising about market realities, yet genuinely excited when spotting true innovation potential. Never sugarcoats - would rather lose a client than watch them waste years on a doomed strategy.
+    principles:
+      - I believe markets reward only those who create genuine new value or deliver existing value in radically better ways - everything else is theater. Innovation without business model thinking is just expensive entertainment.
+      - I hunt for disruption by identifying where customer jobs are poorly served, where value chains are ripe for unbundling, and where technology enablers create sudden strategic openings.
+      - My lens is ruthlessly pragmatic - I care about sustainable competitive advantage, not clever features. I push teams to question their entire business logic because incremental thinking produces incremental results, and in fast-moving markets, incremental means obsolete.
+
+  menu:
+    - trigger: innovate
+      workflow: "{project-root}/bmad/cis/workflows/innovation-strategy/workflow.yaml"
+      description: Identify disruption opportunities and business model innovation

package/src/modules/cis/agents/storyteller.agent.yaml

@@ -0,0 +1,23 @@
+# Master Storyteller Agent Definition
+
+agent:
+  metadata:
+    id: bmad/cis/agents/storyteller.md
+    name: Sophia
+    title: Master Storyteller
+    icon: 📖
+    module: cis
+
+  persona:
+    role: Expert Storytelling Guide + Narrative Strategist
+    identity: Master storyteller with 50+ years crafting compelling narratives across multiple mediums. Expert in narrative frameworks, emotional psychology, and audience engagement. Background in journalism, screenwriting, and brand storytelling with deep understanding of universal human themes.
+    communication_style: Speaks in a flowery whimsical manner, every communication is like being enraptured by the master story teller. Insightful and engaging with natural storytelling ability. Articulate and empathetic approach that connects emotionally with audiences. Strategic in narrative construction while maintaining creative flexibility and authenticity.
+    principles:
+      - I believe that powerful narratives connect with audiences on deep emotional levels by leveraging timeless human truths that transcend context while being carefully tailored to platform and audience needs.
+      - My approach centers on finding and amplifying the authentic story within any subject, applying proven frameworks flexibly to showcase change and growth through vivid details that make the abstract concrete.
+      - I craft stories designed to stick in hearts and minds, building and resolving tension in ways that create lasting engagement and meaningful impact.
+
+  menu:
+    - trigger: story
+      exec: "{project-root}/bmad/cis/workflows/storytelling/workflow.yaml"
+      description: Craft compelling narrative using proven frameworks

package/src/modules/cis/workflows/design-thinking/design-methods.csv

@@ -1,4 +1,4 @@
-phase,method_name,description,facilitation_prompts,best_for,complexity,typical_duration
+phase,method_name,description,facilitation_prompts
 empathize,User Interviews,Conduct deep conversations to understand user needs experiences and pain points through active listening,What brings you here today?|Walk me through a recent experience|What frustrates you most?|What would make this easier?|Tell me more about that
 empathize,Empathy Mapping,Create visual representation of what users say think do and feel to build deep understanding,What did they say?|What might they be thinking?|What actions did they take?|What emotions surfaced?
 empathize,Shadowing,Observe users in their natural environment to see unspoken behaviors and contextual factors,Watch without interrupting|Note their workarounds|What patterns emerge?|What do they not say?

package/src/modules/cis/workflows/design-thinking/instructions.md

@@ -1,6 +1,6 @@
 # Design Thinking Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {project_root}/bmad/cis/workflows/design-thinking/workflow.yaml</critical>
 <critical>Load and understand design methods from: {design_methods}</critical>
 

package/src/modules/cis/workflows/design-thinking/workflow.yaml

@@ -7,6 +7,7 @@ author: "BMad"
 config_source: "{project-root}/bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
 date: system-generated
 
 # Optional inputs for context
@@ -27,3 +28,16 @@ design_methods: "{installed_path}/design-methods.csv"
 
 # Output configuration
 default_output_file: "{output_folder}/design-thinking-{{date}}.md"
+
+standalone: true
+
+web_bundle:
+  name: "design-thinking"
+  description: "Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs."
+  author: "BMad"
+  instructions: "bmad/cis/workflows/design-thinking/instructions.md"
+  template: "bmad/cis/workflows/design-thinking/template.md"
+  web_bundle_files:
+    - "bmad/cis/workflows/design-thinking/instructions.md"
+    - "bmad/cis/workflows/design-thinking/template.md"
+    - "bmad/cis/workflows/design-thinking/design-methods.csv"

package/src/modules/cis/workflows/innovation-strategy/innovation-frameworks.csv

@@ -1,4 +1,4 @@
-category,framework_name,description,key_questions,best_for,complexity,typical_duration
+category,framework_name,description,key_questions
 disruption,Disruptive Innovation Theory,Identify how new entrants use simpler cheaper solutions to overtake incumbents by serving overlooked segments,Who are non-consumers?|What's good enough for them?|What incumbent weakness exists?|How could simple beat sophisticated?|What market entry point exists?
 disruption,Jobs to be Done,Uncover customer jobs and the solutions they hire to make progress - reveals unmet needs competitors miss,What job are customers hiring this for?|What progress do they seek?|What alternatives do they use?|What frustrations exist?|What would fire this solution?
 disruption,Blue Ocean Strategy,Create uncontested market space by making competition irrelevant through value innovation,What factors can we eliminate?|What should we reduce?|What can we raise?|What should we create?|Where is the blue ocean?
@@ -27,5 +27,5 @@ value_chain,Partnership Strategy,Design strategic partnerships and ecosystem pla
 technology,Technology Adoption Lifecycle,Understand how innovations diffuse through society from innovators to laggards to time market entry,Who are the innovators?|Who are early adopters?|What's our adoption strategy?|How do we cross chasms?|What's our current stage?
 technology,S-Curve Analysis,Identify inflection points in technology maturity and market adoption to time innovation investments,Where are we on the S-curve?|What's the next curve?|When should we jump curves?|What's the tipping point?|What should we invest in now?
 technology,Technology Roadmapping,Plan evolution of technology capabilities aligned with strategic goals and market timing,What capabilities do we need?|What's the sequence?|What dependencies exist?|What's the timeline?|Where do we invest first?
-technology,Open Innovation Strategy,Leverage external ideas technologies and paths to market to accelerate innovation beyond internal R&D,What could we source externally?|Who has relevant innovation?|How do we collaborate?|What IP strategy?|How do we integrate external innovation?
+technology,Open Innovation Strategy,Leverage external ideas technologies and paths to market to accelerate innovation beyond internal R and D,What could we source externally?|Who has relevant innovation?|How do we collaborate?|What IP strategy?|How do we integrate external innovation?
 technology,Digital Transformation Framework,Reimagine business models operations and customer experiences through digital technology enablers,What digital capabilities exist?|How could they transform our model?|What customer experience improvements?|What operational efficiencies?|What new business models?

package/src/modules/cis/workflows/innovation-strategy/instructions.md

@@ -1,6 +1,6 @@
 # Innovation Strategy Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {project_root}/bmad/cis/workflows/innovation-strategy/workflow.yaml</critical>
 <critical>Load and understand innovation frameworks from: {innovation_frameworks}</critical>
 

package/src/modules/cis/workflows/innovation-strategy/template.md

@@ -48,7 +48,7 @@
 
 {{value_proposition}}
 
-### Revenue & Cost Structure
+### Revenue and Cost Structure
 
 {{revenue_cost_structure}}
 
@@ -92,7 +92,7 @@
 
 {{value_chain_opportunities}}
 
-### Partnership & Ecosystem Plays
+### Partnership and Ecosystem Plays
 
 {{partnership_opportunities}}
 
@@ -152,7 +152,7 @@
 
 {{phase_2}}
 
-### Phase 3: Scale & Optimize (9-18 months)
+### Phase 3: Scale and Optimize (9-18 months)
 
 {{phase_3}}
 
@@ -174,7 +174,7 @@
 
 ---
 
-## ⚠️ RISKS & MITIGATION
+## ⚠️ RISKS AND MITIGATION
 
 ### Key Risks
 

package/src/modules/cis/workflows/innovation-strategy/workflow.yaml

@@ -7,6 +7,7 @@ author: "BMad"
 config_source: "{project-root}/bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
 date: system-generated
 
 # Optional inputs for context
@@ -27,3 +28,16 @@ innovation_frameworks: "{installed_path}/innovation-frameworks.csv"
 
 # Output configuration
 default_output_file: "{output_folder}/innovation-strategy-{{date}}.md"
+
+standalone: true
+
+web_bundle:
+  name: "innovation-strategy"
+  description: "Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities."
+  author: "BMad"
+  instructions: "bmad/cis/workflows/innovation-strategy/instructions.md"
+  template: "bmad/cis/workflows/innovation-strategy/template.md"
+  web_bundle_files:
+    - "bmad/cis/workflows/innovation-strategy/instructions.md"
+    - "bmad/cis/workflows/innovation-strategy/template.md"
+    - "bmad/cis/workflows/innovation-strategy/innovation-frameworks.csv"

package/src/modules/cis/workflows/problem-solving/instructions.md

@@ -1,6 +1,6 @@
 # Problem Solving Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {project_root}/bmad/cis/workflows/problem-solving/workflow.yaml</critical>
 <critical>Load and understand solving methods from: {solving_methods}</critical>
 

package/src/modules/cis/workflows/problem-solving/solving-methods.csv

@@ -1,8 +1,8 @@
-category,method_name,description,facilitation_prompts,best_for,complexity,typical_duration
-diagnosis,Five Whys Root Cause,Drill down through layers of symptoms to uncover true root cause by asking why five times,Why did this happen?|Why is that the case?|Why does that occur?|What's beneath that?|What's the root cause?,linear-causation,simple,10-15
-diagnosis,Fishbone Diagram,Map all potential causes across categories - people process materials equipment environment - to systematically explore cause space,What people factors contribute?|What process issues?|What material problems?|What equipment factors?|What environmental conditions?,complex-multi-factor,moderate,20-30
-diagnosis,Problem Statement Refinement,Transform vague complaints into precise actionable problem statements that focus solution effort,What exactly is wrong?|Who is affected and how?|When and where does it occur?|What's the gap between current and desired?|What makes this a problem?,problem-framing,simple,10-15
-diagnosis,Is/Is Not Analysis,Define problem boundaries by contrasting where problem exists vs doesn't exist to narrow investigation,Where does problem occur?|Where doesn't it?|When does it happen?|When doesn't it?|Who experiences it?|Who doesn't?|What pattern emerges?,pattern-identification,simple,15-20
+category,method_name,description,facilitation_prompts
+diagnosis,Five Whys Root Cause,Drill down through layers of symptoms to uncover true root cause by asking why five times,Why did this happen?|Why is that the case?|Why does that occur?|What's beneath that?|What's the root cause?
+diagnosis,Fishbone Diagram,Map all potential causes across categories - people process materials equipment environment - to systematically explore cause space,What people factors contribute?|What process issues?|What material problems?|What equipment factors?|What environmental conditions?
+diagnosis,Problem Statement Refinement,Transform vague complaints into precise actionable problem statements that focus solution effort,What exactly is wrong?|Who is affected and how?|When and where does it occur?|What's the gap between current and desired?|What makes this a problem?
+diagnosis,Is/Is Not Analysis,Define problem boundaries by contrasting where problem exists vs doesn't exist to narrow investigation,Where does problem occur?|Where doesn't it?|When does it happen?|When doesn't it?|Who experiences it?|Who doesn't?|What pattern emerges?
 diagnosis,Systems Thinking,Map interconnected system elements feedback loops and leverage points to understand complex problem dynamics,What are system components?|What relationships exist?|What feedback loops?|What delays occur?|Where are leverage points?
 analysis,Force Field Analysis,Identify driving forces pushing toward solution and restraining forces blocking progress to plan interventions,What forces drive toward solution?|What forces resist change?|Which are strongest?|Which can we influence?|What's the strategy?
 analysis,Pareto Analysis,Apply 80/20 rule to identify vital few causes creating majority of impact worth solving first,What causes exist?|What's the frequency or impact of each?|What's the cumulative impact?|What vital few drive 80%?|Focus where?
@@ -12,7 +12,7 @@ analysis,Failure Mode Analysis,Anticipate how solutions could fail and engineer
 synthesis,TRIZ Contradiction Matrix,Resolve technical contradictions using 40 inventive principles from pattern analysis of patents,What improves?|What worsens?|What's the contradiction?|What principles apply?|How to resolve?
 synthesis,Lateral Thinking Techniques,Use provocative operations and random entry to break pattern-thinking and access novel solutions,Make a provocation|Challenge assumptions|Use random stimulus|Escape dominant ideas|Generate alternatives
 synthesis,Morphological Analysis,Systematically explore all combinations of solution parameters to find non-obvious optimal configurations,What are key parameters?|What options exist for each?|Try different combinations|What patterns emerge?|What's optimal?
-synthesis,Biomimicry Problem Solving,Learn from nature's 3.8 billion years of R&D to find elegant solutions to engineering challenges,How does nature solve this?|What biological analogy?|What principles transfer?|How to adapt?
+synthesis,Biomimicry Problem Solving,Learn from nature's 3.8 billion years of R and D to find elegant solutions to engineering challenges,How does nature solve this?|What biological analogy?|What principles transfer?|How to adapt?
 synthesis,Synectics Method,Make strange familiar and familiar strange through analogies to spark creative problem-solving breakthrough,What's this like?|How are they similar?|What metaphor fits?|What does that suggest?|What insight emerges?
 evaluation,Decision Matrix,Systematically evaluate solution options against weighted criteria for objective selection,What are options?|What criteria matter?|What weights?|Rate each option|Calculate scores|What wins?
 evaluation,Cost Benefit Analysis,Quantify expected costs and benefits of solution options to support rational investment decisions,What are costs?|What are benefits?|Quantify each|What's payback period?|What's ROI?|What's recommended?

package/src/modules/cis/workflows/problem-solving/template.md

@@ -26,7 +26,7 @@
 
 ---
 
-## 🔍 DIAGNOSIS & ROOT CAUSE ANALYSIS
+## 🔍 DIAGNOSIS AND ROOT CAUSE ANALYSIS
 
 ### Problem Boundaries (Is/Is Not)
 
@@ -112,7 +112,7 @@
 
 {{action_steps}}
 
-### Timeline & Milestones
+### Timeline and Milestones
 
 {{timeline}}
 
@@ -126,7 +126,7 @@
 
 ---
 
-## 📈 MONITORING & VALIDATION
+## 📈 MONITORING AND VALIDATION
 
 ### Success Metrics
 

package/src/modules/cis/workflows/problem-solving/workflow.yaml

@@ -7,6 +7,7 @@ author: "BMad"
 config_source: "{project-root}/bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
 date: system-generated
 
 # Optional inputs for context
@@ -27,3 +28,16 @@ solving_methods: "{installed_path}/solving-methods.csv"
 
 # Output configuration
 default_output_file: "{output_folder}/problem-solution-{{date}}.md"
+
+standalone: true
+
+web_bundle:
+  name: "problem-solving"
+  description: "Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks."
+  author: "BMad"
+  instructions: "bmad/cis/workflows/problem-solving/instructions.md"
+  template: "bmad/cis/workflows/problem-solving/template.md"
+  web_bundle_files:
+    - "bmad/cis/workflows/problem-solving/instructions.md"
+    - "bmad/cis/workflows/problem-solving/template.md"
+    - "bmad/cis/workflows/problem-solving/solving-methods.csv"

package/src/modules/cis/workflows/storytelling/instructions.md

@@ -3,26 +3,31 @@
 ## Workflow
 
 <workflow>
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {project_root}/bmad/cis/workflows/storytelling/workflow.yaml</critical>
+<critical>Communicate all responses in {communication_language}</critical>
 
 <step n="1" goal="Story Context Setup">
 
 <action>Check if context data was provided with workflow invocation</action>
-<check>If data attribute was passed to this workflow:</check>
-<action>Load the context document from the data file path</action>
-<action>Study the background information, brand details, or subject matter</action>
-<action>Use the provided context to inform story development</action>
-<action>Acknowledge the focused storytelling goal</action>
-<ask response="story_refinement">I see we're crafting a story based on the context provided. What specific angle or emphasis would you like?</ask>
-<check>Else (no context data provided):</check>
-<action>Proceed with context gathering</action>
-<ask response="story_purpose">1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study)</ask>
-<ask response="target_audience">2. Who is your target audience?</ask>
-<ask response="key_messages">3. What key messages or takeaways do you want the audience to have?</ask>
-<ask>4. Any constraints? (length, tone, medium, existing brand guidelines)</ask>
+
+<check if="data attribute was passed to this workflow">
+  <action>Load the context document from the data file path</action>
+  <action>Study the background information, brand details, or subject matter</action>
+  <action>Use the provided context to inform story development</action>
+  <action>Acknowledge the focused storytelling goal</action>
+  <ask response="story_refinement">I see we're crafting a story based on the context provided. What specific angle or emphasis would you like?</ask>
+</check>
+
+<check if="no context data provided">
+  <action>Proceed with context gathering</action>
+  <ask response="story_purpose">1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study)</ask>
+  <ask response="target_audience">2. Who is your target audience?</ask>
+  <ask response="key_messages">3. What key messages or takeaways do you want the audience to have?</ask>
+  <ask>4. Any constraints? (length, tone, medium, existing brand guidelines)</ask>
 
 <critical>Wait for user response before proceeding. This context shapes the narrative approach.</critical>
+</check>
 
 <template-output>story_purpose, target_audience, key_messages</template-output>
 
@@ -52,13 +57,14 @@ I can help craft your story using these proven narrative frameworks:
 Which framework best fits your purpose? (Enter 1-10, or ask for my recommendation)
 </ask>
 
-<check>If user asks for recommendation:</check>
-<action>Analyze story_purpose, target_audience, and key_messages</action>
-<action>Recommend best-fit framework with clear rationale</action>
-<example>
-Based on your {{story_purpose}} for {{target_audience}}, I recommend:
-**{{framework_name}}** because {{rationale}}
-</example>
+<check if="user asks for recommendation">
+  <action>Analyze story_purpose, target_audience, and key_messages</action>
+  <action>Recommend best-fit framework with clear rationale</action>
+  <example>
+  Based on your {{story_purpose}} for {{target_audience}}, I recommend:
+  **{{framework_name}}** because {{rationale}}
+  </example>
+</check>
 
 <template-output>story_type, framework_name</template-output>
 
@@ -177,8 +183,6 @@ The first moment determines if they keep reading/listening.
 
 <step n="6" goal="Write Core Narrative">
 
-<check>Ask if user wants to write or wants AI to write</check>
-
 <ask>Would you like to:
 
 1. Draft the story yourself with my guidance
@@ -186,13 +190,13 @@ The first moment determines if they keep reading/listening.
 3. Co-create it iteratively together
    </ask>
 
-<if selection="1">
+<if selection="1 or draft themselves">
   <action>Provide writing prompts and encouragement</action>
   <action>Offer feedback on drafts they share</action>
   <action>Suggest refinements for clarity, emotion, flow</action>
 </if>
 
-<if selection="2">
+<if selection="2 or ai writes the next draft based on discussions">
   <action>Synthesize all gathered elements</action>
   <action>Write complete narrative in appropriate tone/style</action>
   <action>Structure according to chosen framework</action>
@@ -200,7 +204,7 @@ The first moment determines if they keep reading/listening.
   <action>Present draft for feedback and refinement</action>
 </if>
 
-<if selection="3">
+<if selection="3 or work collaboratively with co-creation">
   <action>Write opening paragraph</action>
   <action>Get feedback and iterate</action>
   <action>Build section by section collaboratively</action>
@@ -245,16 +249,17 @@ Provide strategic guidance for story deployment:
 
 </step>
 
-<step n="9" goal="Refinement & Next Steps">
+<step n="9" goal="Refinement AND Next Steps">
 
 Polish and plan forward:
 
 <ask>What parts of the story feel strongest?</ask>
 <ask>What areas could use more refinement?</ask>
+<ask>What's the key resolution or call to action for your story?</ask>
 <ask>Do you need additional story versions for other audiences/purposes?</ask>
 <ask>How will you test this story with your audience?</ask>
 
-<template-output>refinement_opportunities, additional_versions, feedback_plan</template-output>
+<template-output>resolution, refinement_opportunities, additional_versions, feedback_plan</template-output>
 
 </step>
 
@@ -268,6 +273,9 @@ Compile all story components into the structured template:
 4. Verify tone and voice consistency
 5. Fill all template placeholders with actual content
 
+<action>Write final story document to {output_folder}/story-{{date}}.md</action>
+<action>Confirm completion with: "Story complete, {user_name}! Your narrative has been saved to {output_folder}/story-{{date}}.md"</action>
+
 <template-output>agent_role, agent_name, user_name, date</template-output>
 
 </step>

package/src/modules/cis/workflows/storytelling/template.md

@@ -62,7 +62,7 @@
 
 {{key_messages}}
 
-## Variations & Adaptations
+## Variations AND Adaptations
 
 ### Short Version (Tweet/Social)
 
@@ -86,7 +86,7 @@
 
 {{audience_considerations}}
 
-### Tone & Voice Notes
+### Tone AND Voice Notes
 
 {{tone_notes}}
 

package/src/modules/cis/workflows/storytelling/workflow.yaml

@@ -7,6 +7,7 @@ author: "BMad"
 config_source: "{project-root}/bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
 date: system-generated
 
 # Optional inputs for context
@@ -27,3 +28,16 @@ story_frameworks: "{installed_path}/story-types.csv"
 
 # Output configuration
 default_output_file: "{output_folder}/story-{{date}}.md"
+
+standalone: true
+
+web_bundle:
+  name: "storytelling"
+  description: "Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose."
+  author: "BMad"
+  instructions: "bmad/cis/workflows/storytelling/instructions.md"
+  template: "bmad/cis/workflows/storytelling/template.md"
+  web_bundle_files:
+    - "bmad/cis/workflows/storytelling/instructions.md"
+    - "bmad/cis/workflows/storytelling/template.md"
+    - "bmad/cis/workflows/storytelling/story-types.csv"

package/src/utility/models/agent-activation-ide.xml

@@ -12,15 +12,15 @@
     <handlers>
       <handler type="run-workflow">
         When command has: run-workflow="path/to/x.yaml" You MUST:
-        1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.md
+        1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
         2. READ its entire contents - the is the CORE OS for EXECUTING modules
         3. Pass the yaml path as 'workflow-config' parameter to those instructions
-        4. Follow workflow.md instructions EXACTLY as written
+        4. Follow workflow.xml instructions EXACTLY as written
         5. Save outputs after EACH section (never batch)
       </handler>
       <handler type="validate-workflow">
         When command has: validate-workflow="path/to/workflow.yaml" You MUST:
-        1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.md
+        1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
         2. READ its entire contents and EXECUTE all instructions in that file
         3. Pass the workflow, and also check the workflow location for a checklist.md to pass as the checklist
         4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify

package/src/utility/models/agent-activation-web.xml

@@ -0,0 +1,60 @@
+<activation critical="MANDATORY">
+  <init>
+    <step n="1">Load persona from this current agent xml block containing this activation you are reading now</step>
+    <step n="2">Show greeting + numbered list of ALL commands IN ORDER from current agent's cmds section</step>
+    <step n="3">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
+  </init>
+  <bundled-files critical="MANDATORY">
+    <access-method>
+      All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
+      When you need to access a file path like "bmad/core/tasks/workflow.xml":
+      1. Find the &lt;file id="bmad/core/tasks/workflow.xml"&gt; element in this document
+      2. Extract the content from within the CDATA section
+      3. Use that content as if you read it from the filesystem
+    </access-method>
+    <rules>
+      <rule>NEVER attempt to read files from filesystem - all files are bundled in this XML</rule>
+      <rule>File paths starting with "bmad/" or "{project-root}/bmad/" refer to &lt;file id="..."&gt; elements</rule>
+      <rule>When instructions reference a file path, locate the corresponding &lt;file&gt; element by matching the id attribute</rule>
+      <rule>YAML files are bundled with only their web_bundle section content (flattened to root level)</rule>
+    </rules>
+  </bundled-files>
+  <commands critical="MANDATORY">
+    <input>Number → cmd[n] | Text → fuzzy match *commands</input>
+    <extract>exec, tmpl, data, action, run-workflow, validate-workflow</extract>
+    <handlers>
+      <handler type="run-workflow">
+        When command has: run-workflow="path/to/x.yaml" You MUST:
+        1. CRITICAL: Locate &lt;file id="bmad/core/tasks/workflow.xml"&gt; in this XML bundle
+        2. Extract and READ its CDATA content - this is the CORE OS for EXECUTING workflows
+        3. Locate &lt;file id="path/to/x.yaml"&gt; for the workflow config
+        4. Pass the yaml content as 'workflow-config' parameter to workflow.xml instructions
+        5. Follow workflow.xml instructions EXACTLY as written
+        6. When workflow references other files, locate them by id in &lt;file&gt; elements
+        7. Save outputs after EACH section (never batch)
+      </handler>
+      <handler type="action">
+        When command has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+        When command has: action="text" → Execute the text directly as a critical action prompt
+      </handler>
+      <handler type="data">
+        When command has: data="path/to/x.json|yaml|yml"
+        Locate &lt;file id="path/to/x.json|yaml|yml"&gt; in this bundle, extract CDATA, parse as JSON/YAML, make available as {data}
+      </handler>
+      <handler type="tmpl">
+        When command has: tmpl="path/to/x.md"
+        Locate &lt;file id="path/to/x.md"&gt; in this bundle, extract CDATA, parse as markdown with {{mustache}} templates
+      </handler>
+      <handler type="exec">
+        When command has: exec="path"
+        Locate &lt;file id="path"&gt; in this bundle, extract CDATA, and EXECUTE that content
+      </handler>
+    </handlers>
+  </commands>
+  <rules critical="MANDATORY">
+    Stay in character until *exit
+    Number all option lists, use letters for sub-options
+    All file content is bundled in &lt;file&gt; elements - locate by id attribute
+    NEVER attempt filesystem operations - everything is in this XML
+  </rules>
+</activation>

package/src/utility/models/agent-in-team-activation.xml

@@ -0,0 +1,3 @@
+<activation critical="MANDATORY">
+
+</activation>

package/src/utility/models/fragments/activation-rules.xml

@@ -0,0 +1,8 @@
+<rules>
+  - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
+  - Stay in character until exit selected
+  - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
+  - Number all lists, use letters for sub-options
+  - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
+  - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
+</rules>

package/src/utility/models/fragments/activation-steps.xml

@@ -0,0 +1,15 @@
+<step n="1">Load persona from this current agent file (already in context)</step>
+<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+    - Load and read {project-root}/bmad/{{module}}/config.yaml NOW
+    - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+    - VERIFY: If config not loaded, STOP and report error to user
+    - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
+<step n="3">Remember: user's name is {user_name}</step>
+{AGENT_SPECIFIC_STEPS}
+<step n="{MENU_STEP}">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+    ALL menu items from menu section</step>
+<step n="{HALT_STEP}">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+<step n="{INPUT_STEP}">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+    to clarify | No match → show "Not recognized"</step>
+<step n="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+    (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>

package/src/utility/models/fragments/handler-action.xml

@@ -0,0 +1,4 @@
+    <handler type="action">
+      When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+      When menu item has: action="text" → Execute the text directly as an inline instruction
+    </handler>

package/src/utility/models/fragments/handler-data.xml

@@ -0,0 +1,5 @@
+    <handler type="data">
+      When menu item has: data="path/to/file.json|yaml|yml|csv|xml"
+      Load the file first, parse according to extension
+      Make available as {data} variable to subsequent handler operations
+    </handler>

package/src/utility/models/fragments/handler-exec.xml

@@ -0,0 +1,5 @@
+    <handler type="exec">
+      When menu item has: exec="path/to/file.md"
+      Actually LOAD and EXECUTE the file at that path - do not improvise
+      Read the complete file and follow all instructions within it
+    </handler>

package/src/utility/models/fragments/handler-tmpl.xml

@@ -0,0 +1,5 @@
+    <handler type="tmpl">
+      When menu item has: tmpl="path/to/template.md"
+      Load template file, parse as markdown with {{mustache}} style variables
+      Make template content available as {template} to action/exec/workflow handlers
+    </handler>

package/src/utility/models/fragments/handler-validate-workflow.xml

@@ -0,0 +1,7 @@
+<handler type="validate-workflow">
+  When command has: validate-workflow="path/to/workflow.yaml"
+  1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
+  2. READ its entire contents and EXECUTE all instructions in that file
+  3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+  4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+</handler>