chore: add BMAD framework modules, folder features, and tooling configs
Includes BMAD bmb/bmm/cis/tea workflow modules, folder (declaration) feature implementation (controllers, models, enums, views, tests), claude/cursor command configs, and email templates. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
31
_bmad/cis/workflows/design-thinking/design-methods.csv
Normal file
31
_bmad/cis/workflows/design-thinking/design-methods.csv
Normal file
@@ -0,0 +1,31 @@
|
||||
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?
|
||||
empathize,Journey Mapping,Document complete user experience across touchpoints to identify pain points and opportunities,What's their starting point?|What steps do they take?|Where do they struggle?|What delights them?|What's the emotional arc?
|
||||
empathize,Diary Studies,Have users document experiences over time to capture authentic moments and evolving needs,What did you experience today?|How did you feel?|What worked or didn't?|What surprised you?
|
||||
define,Problem Framing,Transform observations into clear actionable problem statements that inspire solution generation,What's the real problem?|Who experiences this?|Why does it matter?|What would success look like?
|
||||
define,How Might We,Reframe problems as opportunity questions that open solution space without prescribing answers,How might we help users...?|How might we make it easier to...?|How might we reduce the friction of...?
|
||||
define,Point of View Statement,Create specific user-centered problem statements that capture who what and why,User type needs what because insight|What's driving this need?|Why does it matter to them?
|
||||
define,Affinity Clustering,Group related observations and insights to reveal patterns and opportunity themes,What connects these?|What themes emerge?|Group similar items|Name each cluster|What story do they tell?
|
||||
define,Jobs to be Done,Identify functional emotional and social jobs users are hiring solutions to accomplish,What job are they trying to do?|What progress do they want?|What are they really hiring this for?|What alternatives exist?
|
||||
ideate,Brainstorming,Generate large quantity of diverse ideas without judgment to explore solution space fully,No bad ideas|Build on others|Go for quantity|Be visual|Stay on topic|Defer judgment
|
||||
ideate,Crazy 8s,Rapidly sketch eight solution variations in eight minutes to force quick creative thinking,Fold paper in 8|1 minute per sketch|No overthinking|Quantity over quality|Push past obvious
|
||||
ideate,SCAMPER Design,Apply seven design lenses to existing solutions - Substitute Combine Adapt Modify Purposes Eliminate Reverse,What could we substitute?|How could we combine elements?|What could we adapt?|How could we modify it?|Other purposes?|What to eliminate?|What if reversed?
|
||||
ideate,Provotype Sketching,Create deliberately provocative or extreme prototypes to spark breakthrough thinking,What's the most extreme version?|Make it ridiculous|Push boundaries|What useful insights emerge?
|
||||
ideate,Analogous Inspiration,Find inspiration from completely different domains to spark innovative connections,What other field solves this?|How does nature handle this?|What's an analogous problem?|What can we borrow?
|
||||
prototype,Paper Prototyping,Create quick low-fidelity sketches and mockups to make ideas tangible for testing,Sketch it out|Make it rough|Focus on core concept|Test assumptions|Learn fast
|
||||
prototype,Role Playing,Act out user scenarios and service interactions to test experience flow and pain points,Play the user|Act out the scenario|What feels awkward?|Where does it break?|What works?
|
||||
prototype,Wizard of Oz,Simulate complex functionality manually behind scenes to test concept before building,Fake the backend|Focus on experience|What do they think is happening?|Does the concept work?
|
||||
prototype,Storyboarding,Visualize user experience across time and touchpoints as sequential illustrated narrative,What's scene 1?|How does it progress?|What's the emotional journey?|Where's the climax?|How does it resolve?
|
||||
prototype,Physical Mockups,Build tangible artifacts users can touch and interact with to test form and function,Make it 3D|Use basic materials|Make it interactive|Test ergonomics|Gather reactions
|
||||
test,Usability Testing,Watch users attempt tasks with prototype to identify friction points and opportunities,Try to accomplish X|Think aloud please|Don't help them|Where do they struggle?|What surprises them?
|
||||
test,Feedback Capture Grid,Organize user feedback across likes questions ideas and changes for actionable insights,What did they like?|What questions arose?|What ideas did they have?|What needs changing?
|
||||
test,A/B Testing,Compare two variations to understand which approach better serves user needs,Show version A|Show version B|Which works better?|Why the difference?|What does data show?
|
||||
test,Assumption Testing,Identify and validate critical assumptions underlying your solution to reduce risk,What are we assuming?|How can we test this?|What would prove us wrong?|What's the riskiest assumption?
|
||||
test,Iterate and Refine,Use test insights to improve prototype through rapid cycles of refinement and re-testing,What did we learn?|What needs fixing?|What stays?|Make changes quickly|Test again
|
||||
implement,Pilot Programs,Launch small-scale real-world implementation to learn before full rollout,Start small|Real users|Real context|What breaks?|What works?|Scale lessons learned
|
||||
implement,Service Blueprinting,Map all service components interactions and touchpoints to guide implementation,What's visible to users?|What happens backstage?|What systems are needed?|Where are handoffs?
|
||||
implement,Design System Creation,Build consistent patterns components and guidelines for scalable implementation,What patterns repeat?|Create reusable components|Document standards|Enable consistency
|
||||
implement,Stakeholder Alignment,Bring team and stakeholders along journey to build shared understanding and commitment,Show the research|Walk through prototypes|Share user stories|Build empathy|Get buy-in
|
||||
implement,Measurement Framework,Define success metrics and feedback loops to track impact and inform future iterations,How will we measure success?|What are key metrics?|How do we gather feedback?|When do we revisit?
|
||||
|
202
_bmad/cis/workflows/design-thinking/instructions.md
Normal file
202
_bmad/cis/workflows/design-thinking/instructions.md
Normal file
@@ -0,0 +1,202 @@
|
||||
# Design Thinking Workflow Instructions
|
||||
|
||||
<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>
|
||||
<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
|
||||
<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
|
||||
|
||||
<facilitation-principles>
|
||||
YOU ARE A HUMAN-CENTERED DESIGN FACILITATOR:
|
||||
- Keep users at the center of every decision
|
||||
- Encourage divergent thinking before convergent action
|
||||
- Make ideas tangible quickly - prototype beats discussion
|
||||
- Embrace failure as feedback, not defeat
|
||||
- Test with real users, not assumptions
|
||||
- Balance empathy with action momentum
|
||||
</facilitation-principles>
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Gather context and define design challenge">
|
||||
Ask the user about their design challenge:
|
||||
- What problem or opportunity are you exploring?
|
||||
- Who are the primary users or stakeholders?
|
||||
- What constraints exist (time, budget, technology)?
|
||||
- What success looks like for this project?
|
||||
- Any existing research or context to consider?
|
||||
|
||||
Load any context data provided via the data attribute.
|
||||
|
||||
Create a clear design challenge statement.
|
||||
|
||||
<template-output>design_challenge</template-output>
|
||||
<template-output>challenge_statement</template-output>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="EMPATHIZE - Build understanding of users">
|
||||
Guide the user through empathy-building activities. Explain in your own voice why deep empathy with users is essential before jumping to solutions.
|
||||
|
||||
Review empathy methods from {design_methods} (phase: empathize) and select 3-5 that fit the design challenge context. Consider:
|
||||
|
||||
- Available resources and access to users
|
||||
- Time constraints
|
||||
- Type of product/service being designed
|
||||
- Depth of understanding needed
|
||||
|
||||
Offer selected methods with guidance on when each works best, then ask which the user has used or can use, or offer a recommendation based on their specific challenge.
|
||||
|
||||
Help gather and synthesize user insights:
|
||||
|
||||
- What did users say, think, do, and feel?
|
||||
- What pain points emerged?
|
||||
- What surprised you?
|
||||
- What patterns do you see?
|
||||
|
||||
<template-output>user_insights</template-output>
|
||||
<template-output>key_observations</template-output>
|
||||
<template-output>empathy_map</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="DEFINE - Frame the problem clearly">
|
||||
<energy-checkpoint>
|
||||
Check in: "We've gathered rich user insights. How are you feeling? Ready to synthesize into problem statements?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Transform observations into actionable problem statements.
|
||||
|
||||
Guide through problem framing (phase: define methods):
|
||||
|
||||
1. Create Point of View statement: "[User type] needs [need] because [insight]"
|
||||
2. Generate "How Might We" questions that open solution space
|
||||
3. Identify key insights and opportunity areas
|
||||
|
||||
Ask probing questions:
|
||||
|
||||
- What's the REAL problem we're solving?
|
||||
- Why does this matter to users?
|
||||
- What would success look like for them?
|
||||
- What assumptions are we making?
|
||||
|
||||
<template-output>pov_statement</template-output>
|
||||
<template-output>hmw_questions</template-output>
|
||||
<template-output>problem_insights</template-output>
|
||||
</step>
|
||||
|
||||
<step n="4" goal="IDEATE - Generate diverse solutions">
|
||||
Facilitate creative solution generation. Explain in your own voice the importance of divergent thinking and deferring judgment during ideation.
|
||||
|
||||
Review ideation methods from {design_methods} (phase: ideate) and select 3-5 methods appropriate for the context. Consider:
|
||||
|
||||
- Group vs individual ideation
|
||||
- Time available
|
||||
- Problem complexity
|
||||
- Team creativity comfort level
|
||||
|
||||
Offer selected methods with brief descriptions of when each works best.
|
||||
|
||||
Walk through chosen method(s):
|
||||
|
||||
- Generate 15-30 ideas minimum
|
||||
- Build on others' ideas
|
||||
- Go for wild and practical
|
||||
- Defer judgment
|
||||
|
||||
Help cluster and select top concepts:
|
||||
|
||||
- Which ideas excite you most?
|
||||
- Which address the core user need?
|
||||
- Which are feasible given constraints?
|
||||
- Select 2-3 to prototype
|
||||
|
||||
<template-output>ideation_methods</template-output>
|
||||
<template-output>generated_ideas</template-output>
|
||||
<template-output>top_concepts</template-output>
|
||||
</step>
|
||||
|
||||
<step n="5" goal="PROTOTYPE - Make ideas tangible">
|
||||
<energy-checkpoint>
|
||||
Check in: "We've generated lots of ideas! How's your energy for making some of these tangible through prototyping?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Guide creation of low-fidelity prototypes for testing. Explain in your own voice why rough and quick prototypes are better than polished ones at this stage.
|
||||
|
||||
Review prototyping methods from {design_methods} (phase: prototype) and select 2-4 appropriate for the solution type. Consider:
|
||||
|
||||
- Physical vs digital product
|
||||
- Service vs product
|
||||
- Available materials and tools
|
||||
- What needs to be tested
|
||||
|
||||
Offer selected methods with guidance on fit.
|
||||
|
||||
Help define prototype:
|
||||
|
||||
- What's the minimum to test your assumptions?
|
||||
- What are you trying to learn?
|
||||
- What should users be able to do?
|
||||
- What can you fake vs build?
|
||||
|
||||
<template-output>prototype_approach</template-output>
|
||||
<template-output>prototype_description</template-output>
|
||||
<template-output>features_to_test</template-output>
|
||||
</step>
|
||||
|
||||
<step n="6" goal="TEST - Validate with users">
|
||||
Design validation approach and capture learnings. Explain in your own voice why observing what users DO matters more than what they SAY.
|
||||
|
||||
Help plan testing (phase: test methods):
|
||||
|
||||
- Who will you test with? (aim for 5-7 users)
|
||||
- What tasks will they attempt?
|
||||
- What questions will you ask?
|
||||
- How will you capture feedback?
|
||||
|
||||
Guide feedback collection:
|
||||
|
||||
- What worked well?
|
||||
- Where did they struggle?
|
||||
- What surprised them (and you)?
|
||||
- What questions arose?
|
||||
- What would they change?
|
||||
|
||||
Synthesize learnings:
|
||||
|
||||
- What assumptions were validated/invalidated?
|
||||
- What needs to change?
|
||||
- What should stay?
|
||||
- What new insights emerged?
|
||||
|
||||
<template-output>testing_plan</template-output>
|
||||
<template-output>user_feedback</template-output>
|
||||
<template-output>key_learnings</template-output>
|
||||
</step>
|
||||
|
||||
<step n="7" goal="Plan next iteration">
|
||||
<energy-checkpoint>
|
||||
Check in: "Great work! How's your energy for final planning - defining next steps and success metrics?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Define clear next steps and success criteria.
|
||||
|
||||
Based on testing insights:
|
||||
|
||||
- What refinements are needed?
|
||||
- What's the priority action?
|
||||
- Who needs to be involved?
|
||||
- What timeline makes sense?
|
||||
- How will you measure success?
|
||||
|
||||
Determine next cycle:
|
||||
|
||||
- Do you need more empathy work?
|
||||
- Should you reframe the problem?
|
||||
- Ready to refine prototype?
|
||||
- Time to pilot with real users?
|
||||
|
||||
<template-output>refinements</template-output>
|
||||
<template-output>action_items</template-output>
|
||||
<template-output>success_metrics</template-output>
|
||||
</step>
|
||||
|
||||
</workflow>
|
||||
111
_bmad/cis/workflows/design-thinking/template.md
Normal file
111
_bmad/cis/workflows/design-thinking/template.md
Normal file
@@ -0,0 +1,111 @@
|
||||
# Design Thinking Session: {{project_name}}
|
||||
|
||||
**Date:** {{date}}
|
||||
**Facilitator:** {{user_name}}
|
||||
**Design Challenge:** {{design_challenge}}
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Design Challenge
|
||||
|
||||
{{challenge_statement}}
|
||||
|
||||
---
|
||||
|
||||
## 👥 EMPATHIZE: Understanding Users
|
||||
|
||||
### User Insights
|
||||
|
||||
{{user_insights}}
|
||||
|
||||
### Key Observations
|
||||
|
||||
{{key_observations}}
|
||||
|
||||
### Empathy Map Summary
|
||||
|
||||
{{empathy_map}}
|
||||
|
||||
---
|
||||
|
||||
## 🎨 DEFINE: Frame the Problem
|
||||
|
||||
### Point of View Statement
|
||||
|
||||
{{pov_statement}}
|
||||
|
||||
### How Might We Questions
|
||||
|
||||
{{hmw_questions}}
|
||||
|
||||
### Key Insights
|
||||
|
||||
{{problem_insights}}
|
||||
|
||||
---
|
||||
|
||||
## 💡 IDEATE: Generate Solutions
|
||||
|
||||
### Selected Methods
|
||||
|
||||
{{ideation_methods}}
|
||||
|
||||
### Generated Ideas
|
||||
|
||||
{{generated_ideas}}
|
||||
|
||||
### Top Concepts
|
||||
|
||||
{{top_concepts}}
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ PROTOTYPE: Make Ideas Tangible
|
||||
|
||||
### Prototype Approach
|
||||
|
||||
{{prototype_approach}}
|
||||
|
||||
### Prototype Description
|
||||
|
||||
{{prototype_description}}
|
||||
|
||||
### Key Features to Test
|
||||
|
||||
{{features_to_test}}
|
||||
|
||||
---
|
||||
|
||||
## ✅ TEST: Validate with Users
|
||||
|
||||
### Testing Plan
|
||||
|
||||
{{testing_plan}}
|
||||
|
||||
### User Feedback
|
||||
|
||||
{{user_feedback}}
|
||||
|
||||
### Key Learnings
|
||||
|
||||
{{key_learnings}}
|
||||
|
||||
---
|
||||
|
||||
## 🚀 Next Steps
|
||||
|
||||
### Refinements Needed
|
||||
|
||||
{{refinements}}
|
||||
|
||||
### Action Items
|
||||
|
||||
{{action_items}}
|
||||
|
||||
### Success Metrics
|
||||
|
||||
{{success_metrics}}
|
||||
|
||||
---
|
||||
|
||||
_Generated using BMAD Creative Intelligence Suite - Design Thinking Workflow_
|
||||
26
_bmad/cis/workflows/design-thinking/workflow.yaml
Normal file
26
_bmad/cis/workflows/design-thinking/workflow.yaml
Normal file
@@ -0,0 +1,26 @@
|
||||
# Design Thinking Workflow Configuration
|
||||
name: "design-thinking"
|
||||
description: 'Guide human-centered design processes using empathy-driven methodologies. Use when the user says "lets run design thinking" or "I want to apply design thinking"'
|
||||
|
||||
# Critical variables load from config_source
|
||||
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
|
||||
|
||||
# Context can be provided via data attribute when invoking
|
||||
# Example: data="{path}/product-context.md" provides project context
|
||||
|
||||
# Module path and component files
|
||||
installed_path: "{project-root}/_bmad/cis/workflows/design-thinking"
|
||||
template: "{installed_path}/template.md"
|
||||
instructions: "{installed_path}/instructions.md"
|
||||
|
||||
# Required Data Files
|
||||
design_methods: "{installed_path}/design-methods.csv"
|
||||
|
||||
# Output configuration
|
||||
default_output_file: "{output_folder}/design-thinking-{{date}}.md"
|
||||
|
||||
standalone: true
|
||||
@@ -0,0 +1,31 @@
|
||||
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?
|
||||
disruption,Crossing the Chasm,Navigate the gap between early adopters and mainstream market with focused beachhead strategy,Who are the innovators and early adopters?|What's our beachhead market?|What's the compelling reason to buy?|What's our whole product?|How do we cross to mainstream?
|
||||
disruption,Platform Revolution,Transform linear value chains into exponential platform ecosystems that connect producers and consumers,What network effects exist?|Who are the producers?|Who are the consumers?|What transaction do we enable?|How do we achieve critical mass?
|
||||
business_model,Business Model Canvas,Map and innovate across nine building blocks of how organizations create deliver and capture value,Who are customer segments?|What value propositions?|What channels and relationships?|What revenue streams?|What key resources activities partnerships?|What cost structure?
|
||||
business_model,Value Proposition Canvas,Design compelling value propositions that match customer jobs pains and gains with precision,What are customer jobs?|What pains do they experience?|What gains do they desire?|How do we relieve pains?|How do we create gains?|What products and services?
|
||||
business_model,Business Model Patterns,Apply proven business model patterns from other industries to your context for rapid innovation,What patterns could apply?|Subscription? Freemium? Marketplace? Razor blade? Bait and hook?|How would this change our model?
|
||||
business_model,Revenue Model Innovation,Explore alternative ways to monetize value creation beyond traditional pricing approaches,How else could we charge?|Usage based? Performance based? Subscription?|What would customers pay for differently?|What new revenue streams exist?
|
||||
business_model,Cost Structure Innovation,Redesign cost structure to enable new price points or improve margins through radical efficiency,What are our biggest costs?|What could we eliminate or automate?|What could we outsource or share?|How could we flip fixed to variable costs?
|
||||
market_analysis,TAM SAM SOM Analysis,Size market opportunity across Total Addressable Serviceable and Obtainable markets for realistic planning,What's total market size?|What can we realistically serve?|What can we obtain near-term?|What assumptions underlie these?|How fast is it growing?
|
||||
market_analysis,Five Forces Analysis,Assess industry structure and competitive dynamics to identify strategic positioning opportunities,What's supplier power?|What's buyer power?|What's competitive rivalry?|What's threat of substitutes?|What's threat of new entrants?|Where's opportunity?
|
||||
market_analysis,PESTLE Analysis,Analyze macro environmental factors - Political Economic Social Tech Legal Environmental - shaping opportunities,What political factors affect us?|Economic trends?|Social shifts?|Technology changes?|Legal requirements?|Environmental factors?|What opportunities or threats?
|
||||
market_analysis,Market Timing Assessment,Evaluate whether market conditions are right for your innovation - too early or too late both fail,What needs to be true first?|What's changing now?|Are customers ready?|Is technology mature enough?|What's the window of opportunity?
|
||||
market_analysis,Competitive Positioning Map,Visualize competitive landscape across key dimensions to identify white space and differentiation opportunities,What dimensions matter most?|Where are competitors positioned?|Where's the white space?|What's our unique position?|What's defensible?
|
||||
strategic,Three Horizons Framework,Balance portfolio across current business emerging opportunities and future possibilities for sustainable growth,What's our core business?|What emerging opportunities?|What future possibilities?|How do we invest across horizons?|What transitions are needed?
|
||||
strategic,Lean Startup Methodology,Build measure learn in rapid cycles to validate assumptions and pivot to product market fit efficiently,What's the riskiest assumption?|What's minimum viable product?|What will we measure?|What did we learn?|Build or pivot?
|
||||
strategic,Innovation Ambition Matrix,Define innovation portfolio balance across core adjacent and transformational initiatives based on risk and impact,What's core enhancement?|What's adjacent expansion?|What's transformational breakthrough?|What's our portfolio balance?|What's the right mix?
|
||||
strategic,Strategic Intent Development,Define bold aspirational goals that stretch organization beyond current capabilities to drive innovation,What's our audacious goal?|What would change our industry?|What seems impossible but valuable?|What's our moon shot?|What capability must we build?
|
||||
strategic,Scenario Planning,Explore multiple plausible futures to build robust strategies that work across different outcomes,What critical uncertainties exist?|What scenarios could unfold?|How would we respond?|What strategies work across scenarios?|What early signals to watch?
|
||||
value_chain,Value Chain Analysis,Map activities from raw materials to end customer to identify where value is created and captured,What's the full value chain?|Where's value created?|What activities are we good at?|What could we outsource?|Where could we disintermediate?
|
||||
value_chain,Unbundling Analysis,Identify opportunities to break apart integrated value chains and capture specific high-value components,What's bundled together?|What could be separated?|Where's most value?|What would customers pay for separately?|Who else could provide pieces?
|
||||
value_chain,Platform Ecosystem Design,Architect multi-sided platforms that create value through network effects and reduced transaction costs,What sides exist?|What value exchange?|How do we attract each side?|What network effects?|What's our revenue model?|How do we govern?
|
||||
value_chain,Make vs Buy Analysis,Evaluate strategic decisions about vertical integration versus outsourcing for competitive advantage,What's core competence?|What provides advantage?|What should we own?|What should we partner?|What's the risk of each?
|
||||
value_chain,Partnership Strategy,Design strategic partnerships and ecosystem plays that expand capabilities and reach efficiently,Who has complementary strengths?|What could we achieve together?|What's the value exchange?|How do we structure this?|What's governance model?
|
||||
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 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?
|
||||
|
276
_bmad/cis/workflows/innovation-strategy/instructions.md
Normal file
276
_bmad/cis/workflows/innovation-strategy/instructions.md
Normal file
@@ -0,0 +1,276 @@
|
||||
# Innovation Strategy Workflow Instructions
|
||||
|
||||
<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>
|
||||
<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
|
||||
<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
|
||||
|
||||
<facilitation-principles>
|
||||
YOU ARE A STRATEGIC INNOVATION ADVISOR:
|
||||
- Demand brutal truth about market realities before innovation exploration
|
||||
- Challenge assumptions ruthlessly - comfortable illusions kill strategies
|
||||
- Balance bold vision with pragmatic execution
|
||||
- Focus on sustainable competitive advantage, not clever features
|
||||
- Push for evidence-based decisions over hopeful guesses
|
||||
- Celebrate strategic clarity when achieved
|
||||
</facilitation-principles>
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Establish strategic context">
|
||||
Understand the strategic situation and objectives:
|
||||
|
||||
Ask the user:
|
||||
|
||||
- What company or business are we analyzing?
|
||||
- What's driving this strategic exploration? (market pressure, new opportunity, plateau, etc.)
|
||||
- What's your current business model in brief?
|
||||
- What constraints or boundaries exist? (resources, timeline, regulatory)
|
||||
- What would breakthrough success look like?
|
||||
|
||||
Load any context data provided via the data attribute.
|
||||
|
||||
Synthesize into clear strategic framing.
|
||||
|
||||
<template-output>company_name</template-output>
|
||||
<template-output>strategic_focus</template-output>
|
||||
<template-output>current_situation</template-output>
|
||||
<template-output>strategic_challenge</template-output>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="Analyze market landscape and competitive dynamics">
|
||||
Conduct thorough market analysis using strategic frameworks. Explain in your own voice why unflinching clarity about market realities must precede innovation exploration.
|
||||
|
||||
Review market analysis frameworks from {innovation_frameworks} (category: market_analysis) and select 2-4 most relevant to the strategic context. Consider:
|
||||
|
||||
- Stage of business (startup vs established)
|
||||
- Industry maturity
|
||||
- Available market data
|
||||
- Strategic priorities
|
||||
|
||||
Offer selected frameworks with guidance on what each reveals. Common options:
|
||||
|
||||
- **TAM SAM SOM Analysis** - For sizing opportunity
|
||||
- **Five Forces Analysis** - For industry structure
|
||||
- **Competitive Positioning Map** - For differentiation analysis
|
||||
- **Market Timing Assessment** - For innovation timing
|
||||
|
||||
Key questions to explore:
|
||||
|
||||
- What market segments exist and how are they evolving?
|
||||
- Who are the real competitors (including non-obvious ones)?
|
||||
- What substitutes threaten your value proposition?
|
||||
- What's changing in the market that creates opportunity or threat?
|
||||
- Where are customers underserved or overserved?
|
||||
|
||||
<template-output>market_landscape</template-output>
|
||||
<template-output>competitive_dynamics</template-output>
|
||||
<template-output>market_opportunities</template-output>
|
||||
<template-output>market_insights</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Analyze current business model">
|
||||
<energy-checkpoint>
|
||||
Check in: "We've covered market landscape. How's your energy? This next part - deconstructing your business model - requires honest self-assessment. Ready?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Deconstruct the existing business model to identify strengths and weaknesses. Explain in your own voice why understanding current model vulnerabilities is essential before innovation.
|
||||
|
||||
Review business model frameworks from {innovation_frameworks} (category: business_model) and select 2-3 appropriate for the business type. Consider:
|
||||
|
||||
- Business maturity (early stage vs mature)
|
||||
- Complexity of model
|
||||
- Key strategic questions
|
||||
|
||||
Offer selected frameworks. Common options:
|
||||
|
||||
- **Business Model Canvas** - For comprehensive mapping
|
||||
- **Value Proposition Canvas** - For product-market fit
|
||||
- **Revenue Model Innovation** - For monetization analysis
|
||||
- **Cost Structure Innovation** - For efficiency opportunities
|
||||
|
||||
Critical questions:
|
||||
|
||||
- Who are you really serving and what jobs are they hiring you for?
|
||||
- How do you create, deliver, and capture value today?
|
||||
- What's your defensible competitive advantage (be honest)?
|
||||
- Where is your model vulnerable to disruption?
|
||||
- What assumptions underpin your model that might be wrong?
|
||||
|
||||
<template-output>current_business_model</template-output>
|
||||
<template-output>value_proposition</template-output>
|
||||
<template-output>revenue_cost_structure</template-output>
|
||||
<template-output>model_weaknesses</template-output>
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Identify disruption opportunities">
|
||||
Hunt for disruption vectors and strategic openings. Explain in your own voice what makes disruption different from incremental innovation.
|
||||
|
||||
Review disruption frameworks from {innovation_frameworks} (category: disruption) and select 2-3 most applicable. Consider:
|
||||
|
||||
- Industry disruption potential
|
||||
- Customer job analysis needs
|
||||
- Platform opportunity existence
|
||||
|
||||
Offer selected frameworks with context. Common options:
|
||||
|
||||
- **Disruptive Innovation Theory** - For finding overlooked segments
|
||||
- **Jobs to be Done** - For unmet needs analysis
|
||||
- **Blue Ocean Strategy** - For uncontested market space
|
||||
- **Platform Revolution** - For network effect plays
|
||||
|
||||
Provocative questions:
|
||||
|
||||
- Who are the NON-consumers you could serve?
|
||||
- What customer jobs are massively underserved?
|
||||
- What would be "good enough" for a new segment?
|
||||
- What technology enablers create sudden strategic openings?
|
||||
- Where could you make the competition irrelevant?
|
||||
|
||||
<template-output>disruption_vectors</template-output>
|
||||
<template-output>unmet_jobs</template-output>
|
||||
<template-output>technology_enablers</template-output>
|
||||
<template-output>strategic_whitespace</template-output>
|
||||
</step>
|
||||
|
||||
<step n="5" goal="Generate innovation opportunities">
|
||||
<energy-checkpoint>
|
||||
Check in: "We've identified disruption vectors. How are you feeling? Ready to generate concrete innovation opportunities?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Develop concrete innovation options across multiple vectors. Explain in your own voice the importance of exploring multiple innovation paths before committing.
|
||||
|
||||
Review strategic and value_chain frameworks from {innovation_frameworks} (categories: strategic, value_chain) and select 2-4 that fit the strategic context. Consider:
|
||||
|
||||
- Innovation ambition (core vs transformational)
|
||||
- Value chain position
|
||||
- Partnership opportunities
|
||||
|
||||
Offer selected frameworks. Common options:
|
||||
|
||||
- **Three Horizons Framework** - For portfolio balance
|
||||
- **Value Chain Analysis** - For activity selection
|
||||
- **Partnership Strategy** - For ecosystem thinking
|
||||
- **Business Model Patterns** - For proven approaches
|
||||
|
||||
Generate 5-10 specific innovation opportunities addressing:
|
||||
|
||||
- Business model innovations (how you create/capture value)
|
||||
- Value chain innovations (what activities you own)
|
||||
- Partnership and ecosystem opportunities
|
||||
- Technology-enabled transformations
|
||||
|
||||
<template-output>innovation_initiatives</template-output>
|
||||
<template-output>business_model_innovation</template-output>
|
||||
<template-output>value_chain_opportunities</template-output>
|
||||
<template-output>partnership_opportunities</template-output>
|
||||
</step>
|
||||
|
||||
<step n="6" goal="Develop and evaluate strategic options">
|
||||
Synthesize insights into 3 distinct strategic options.
|
||||
|
||||
For each option:
|
||||
|
||||
- Clear description of strategic direction
|
||||
- Business model implications
|
||||
- Competitive positioning
|
||||
- Resource requirements
|
||||
- Key risks and dependencies
|
||||
- Expected outcomes and timeline
|
||||
|
||||
Evaluate each option against:
|
||||
|
||||
- Strategic fit with capabilities
|
||||
- Market timing and readiness
|
||||
- Competitive defensibility
|
||||
- Resource feasibility
|
||||
- Risk vs reward profile
|
||||
|
||||
<template-output>option_a_name</template-output>
|
||||
<template-output>option_a_description</template-output>
|
||||
<template-output>option_a_pros</template-output>
|
||||
<template-output>option_a_cons</template-output>
|
||||
<template-output>option_b_name</template-output>
|
||||
<template-output>option_b_description</template-output>
|
||||
<template-output>option_b_pros</template-output>
|
||||
<template-output>option_b_cons</template-output>
|
||||
<template-output>option_c_name</template-output>
|
||||
<template-output>option_c_description</template-output>
|
||||
<template-output>option_c_pros</template-output>
|
||||
<template-output>option_c_cons</template-output>
|
||||
</step>
|
||||
|
||||
<step n="7" goal="Recommend strategic direction">
|
||||
Make bold recommendation with clear rationale.
|
||||
|
||||
Synthesize into recommended strategy:
|
||||
|
||||
- Which option (or combination) is recommended?
|
||||
- Why this direction over alternatives?
|
||||
- What makes you confident (and what scares you)?
|
||||
- What hypotheses MUST be validated first?
|
||||
- What would cause you to pivot or abandon?
|
||||
|
||||
Define critical success factors:
|
||||
|
||||
- What capabilities must be built or acquired?
|
||||
- What partnerships are essential?
|
||||
- What market conditions must hold?
|
||||
- What execution excellence is required?
|
||||
|
||||
<template-output>recommended_strategy</template-output>
|
||||
<template-output>key_hypotheses</template-output>
|
||||
<template-output>success_factors</template-output>
|
||||
</step>
|
||||
|
||||
<step n="8" goal="Build execution roadmap">
|
||||
<energy-checkpoint>
|
||||
Check in: "We've got the strategy direction. How's your energy for the execution planning - turning strategy into actionable roadmap?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Create phased roadmap with clear milestones.
|
||||
|
||||
Structure in three phases:
|
||||
|
||||
- **Phase 1 - Immediate Impact**: Quick wins, hypothesis validation, initial momentum
|
||||
- **Phase 2 - Foundation Building**: Capability development, market entry, systematic growth
|
||||
- **Phase 3 - Scale & Optimization**: Market expansion, efficiency gains, competitive positioning
|
||||
|
||||
For each phase:
|
||||
|
||||
- Key initiatives and deliverables
|
||||
- Resource requirements
|
||||
- Success metrics
|
||||
- Decision gates
|
||||
|
||||
<template-output>phase_1</template-output>
|
||||
<template-output>phase_2</template-output>
|
||||
<template-output>phase_3</template-output>
|
||||
</step>
|
||||
|
||||
<step n="9" goal="Define metrics and risk mitigation">
|
||||
Establish measurement framework and risk management.
|
||||
|
||||
Define success metrics:
|
||||
|
||||
- **Leading indicators** - Early signals of strategy working (engagement, adoption, efficiency)
|
||||
- **Lagging indicators** - Business outcomes (revenue, market share, profitability)
|
||||
- **Decision gates** - Go/no-go criteria at key milestones
|
||||
|
||||
Identify and mitigate key risks:
|
||||
|
||||
- What could kill this strategy?
|
||||
- What assumptions might be wrong?
|
||||
- What competitive responses could occur?
|
||||
- How do we de-risk systematically?
|
||||
- What's our backup plan?
|
||||
|
||||
<template-output>leading_indicators</template-output>
|
||||
<template-output>lagging_indicators</template-output>
|
||||
<template-output>decision_gates</template-output>
|
||||
<template-output>key_risks</template-output>
|
||||
<template-output>risk_mitigation</template-output>
|
||||
</step>
|
||||
|
||||
</workflow>
|
||||
189
_bmad/cis/workflows/innovation-strategy/template.md
Normal file
189
_bmad/cis/workflows/innovation-strategy/template.md
Normal file
@@ -0,0 +1,189 @@
|
||||
# Innovation Strategy: {{company_name}}
|
||||
|
||||
**Date:** {{date}}
|
||||
**Strategist:** {{user_name}}
|
||||
**Strategic Focus:** {{strategic_focus}}
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Strategic Context
|
||||
|
||||
### Current Situation
|
||||
|
||||
{{current_situation}}
|
||||
|
||||
### Strategic Challenge
|
||||
|
||||
{{strategic_challenge}}
|
||||
|
||||
---
|
||||
|
||||
## 📊 MARKET ANALYSIS
|
||||
|
||||
### Market Landscape
|
||||
|
||||
{{market_landscape}}
|
||||
|
||||
### Competitive Dynamics
|
||||
|
||||
{{competitive_dynamics}}
|
||||
|
||||
### Market Opportunities
|
||||
|
||||
{{market_opportunities}}
|
||||
|
||||
### Critical Insights
|
||||
|
||||
{{market_insights}}
|
||||
|
||||
---
|
||||
|
||||
## 💼 BUSINESS MODEL ANALYSIS
|
||||
|
||||
### Current Business Model
|
||||
|
||||
{{current_business_model}}
|
||||
|
||||
### Value Proposition Assessment
|
||||
|
||||
{{value_proposition}}
|
||||
|
||||
### Revenue and Cost Structure
|
||||
|
||||
{{revenue_cost_structure}}
|
||||
|
||||
### Business Model Weaknesses
|
||||
|
||||
{{model_weaknesses}}
|
||||
|
||||
---
|
||||
|
||||
## ⚡ DISRUPTION OPPORTUNITIES
|
||||
|
||||
### Disruption Vectors
|
||||
|
||||
{{disruption_vectors}}
|
||||
|
||||
### Unmet Customer Jobs
|
||||
|
||||
{{unmet_jobs}}
|
||||
|
||||
### Technology Enablers
|
||||
|
||||
{{technology_enablers}}
|
||||
|
||||
### Strategic White Space
|
||||
|
||||
{{strategic_whitespace}}
|
||||
|
||||
---
|
||||
|
||||
## 🚀 INNOVATION OPPORTUNITIES
|
||||
|
||||
### Innovation Initiatives
|
||||
|
||||
{{innovation_initiatives}}
|
||||
|
||||
### Business Model Innovation
|
||||
|
||||
{{business_model_innovation}}
|
||||
|
||||
### Value Chain Opportunities
|
||||
|
||||
{{value_chain_opportunities}}
|
||||
|
||||
### Partnership and Ecosystem Plays
|
||||
|
||||
{{partnership_opportunities}}
|
||||
|
||||
---
|
||||
|
||||
## 🎲 STRATEGIC OPTIONS
|
||||
|
||||
### Option A: {{option_a_name}}
|
||||
|
||||
{{option_a_description}}
|
||||
|
||||
**Pros:** {{option_a_pros}}
|
||||
|
||||
**Cons:** {{option_a_cons}}
|
||||
|
||||
### Option B: {{option_b_name}}
|
||||
|
||||
{{option_b_description}}
|
||||
|
||||
**Pros:** {{option_b_pros}}
|
||||
|
||||
**Cons:** {{option_b_cons}}
|
||||
|
||||
### Option C: {{option_c_name}}
|
||||
|
||||
{{option_c_description}}
|
||||
|
||||
**Pros:** {{option_c_pros}}
|
||||
|
||||
**Cons:** {{option_c_cons}}
|
||||
|
||||
---
|
||||
|
||||
## 🏆 RECOMMENDED STRATEGY
|
||||
|
||||
### Strategic Direction
|
||||
|
||||
{{recommended_strategy}}
|
||||
|
||||
### Key Hypotheses to Validate
|
||||
|
||||
{{key_hypotheses}}
|
||||
|
||||
### Critical Success Factors
|
||||
|
||||
{{success_factors}}
|
||||
|
||||
---
|
||||
|
||||
## 📋 EXECUTION ROADMAP
|
||||
|
||||
### Phase 1: Immediate Impact
|
||||
|
||||
{{phase_1}}
|
||||
|
||||
### Phase 2: Foundation Building
|
||||
|
||||
{{phase_2}}
|
||||
|
||||
### Phase 3: Scale & Optimization
|
||||
|
||||
{{phase_3}}
|
||||
|
||||
---
|
||||
|
||||
## 📈 SUCCESS METRICS
|
||||
|
||||
### Leading Indicators
|
||||
|
||||
{{leading_indicators}}
|
||||
|
||||
### Lagging Indicators
|
||||
|
||||
{{lagging_indicators}}
|
||||
|
||||
### Decision Gates
|
||||
|
||||
{{decision_gates}}
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ RISKS AND MITIGATION
|
||||
|
||||
### Key Risks
|
||||
|
||||
{{key_risks}}
|
||||
|
||||
### Mitigation Strategies
|
||||
|
||||
{{risk_mitigation}}
|
||||
|
||||
---
|
||||
|
||||
_Generated using BMAD Creative Intelligence Suite - Innovation Strategy Workflow_
|
||||
26
_bmad/cis/workflows/innovation-strategy/workflow.yaml
Normal file
26
_bmad/cis/workflows/innovation-strategy/workflow.yaml
Normal file
@@ -0,0 +1,26 @@
|
||||
# Innovation Strategy Workflow Configuration
|
||||
name: "innovation-strategy"
|
||||
description: 'Identify disruption opportunities and architect business model innovation. Use when the user says "lets create an innovation strategy" or "I want to find disruption opportunities"'
|
||||
|
||||
# Critical variables load from config_source
|
||||
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
|
||||
|
||||
# Context can be provided via data attribute when invoking
|
||||
# Example: data="{path}/industry-analysis.md" provides market context
|
||||
|
||||
# Module path and component files
|
||||
installed_path: "{project-root}/_bmad/cis/workflows/innovation-strategy"
|
||||
template: "{installed_path}/template.md"
|
||||
instructions: "{installed_path}/instructions.md"
|
||||
|
||||
# Required Data Files
|
||||
innovation_frameworks: "{installed_path}/innovation-frameworks.csv"
|
||||
|
||||
# Output configuration
|
||||
default_output_file: "{output_folder}/innovation-strategy-{{date}}.md"
|
||||
|
||||
standalone: true
|
||||
252
_bmad/cis/workflows/problem-solving/instructions.md
Normal file
252
_bmad/cis/workflows/problem-solving/instructions.md
Normal file
@@ -0,0 +1,252 @@
|
||||
# Problem Solving Workflow Instructions
|
||||
|
||||
<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>
|
||||
<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
|
||||
<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
|
||||
|
||||
<facilitation-principles>
|
||||
YOU ARE A SYSTEMATIC PROBLEM-SOLVING FACILITATOR:
|
||||
- Guide through diagnosis before jumping to solutions
|
||||
- Ask questions that reveal patterns and root causes
|
||||
- Help them think systematically, not do thinking for them
|
||||
- Balance rigor with momentum - don't get stuck in analysis
|
||||
- Celebrate insights when they emerge
|
||||
- Monitor energy - problem-solving is mentally intensive
|
||||
</facilitation-principles>
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Define and refine the problem">
|
||||
Establish clear problem definition before jumping to solutions. Explain in your own voice why precise problem framing matters before diving into solutions.
|
||||
|
||||
Load any context data provided via the data attribute.
|
||||
|
||||
Gather problem information by asking:
|
||||
|
||||
- What problem are you trying to solve?
|
||||
- How did you first notice this problem?
|
||||
- Who is experiencing this problem?
|
||||
- When and where does it occur?
|
||||
- What's the impact or cost of this problem?
|
||||
- What would success look like?
|
||||
|
||||
Reference the **Problem Statement Refinement** method from {solving_methods} to guide transformation of vague complaints into precise statements. Focus on:
|
||||
|
||||
- What EXACTLY is wrong?
|
||||
- What's the gap between current and desired state?
|
||||
- What makes this a problem worth solving?
|
||||
|
||||
<template-output>problem_title</template-output>
|
||||
<template-output>problem_category</template-output>
|
||||
<template-output>initial_problem</template-output>
|
||||
<template-output>refined_problem_statement</template-output>
|
||||
<template-output>problem_context</template-output>
|
||||
<template-output>success_criteria</template-output>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="Diagnose and bound the problem">
|
||||
Use systematic diagnosis to understand problem scope and patterns. Explain in your own voice why mapping boundaries reveals important clues.
|
||||
|
||||
Reference **Is/Is Not Analysis** method from {solving_methods} and guide the user through:
|
||||
|
||||
- Where DOES the problem occur? Where DOESN'T it?
|
||||
- When DOES it happen? When DOESN'T it?
|
||||
- Who IS affected? Who ISN'T?
|
||||
- What IS the problem? What ISN'T it?
|
||||
|
||||
Help identify patterns that emerge from these boundaries.
|
||||
|
||||
<template-output>problem_boundaries</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Conduct root cause analysis">
|
||||
Drill down to true root causes rather than treating symptoms. Explain in your own voice the distinction between symptoms and root causes.
|
||||
|
||||
Review diagnosis methods from {solving_methods} (category: diagnosis) and select 2-3 methods that fit the problem type. Offer these to the user with brief descriptions of when each works best.
|
||||
|
||||
Common options include:
|
||||
|
||||
- **Five Whys Root Cause** - Good for linear cause chains
|
||||
- **Fishbone Diagram** - Good for complex multi-factor problems
|
||||
- **Systems Thinking** - Good for interconnected dynamics
|
||||
|
||||
Walk through chosen method(s) to identify:
|
||||
|
||||
- What are the immediate symptoms?
|
||||
- What causes those symptoms?
|
||||
- What causes those causes? (Keep drilling)
|
||||
- What's the root cause we must address?
|
||||
- What system dynamics are at play?
|
||||
|
||||
<template-output>root_cause_analysis</template-output>
|
||||
<template-output>contributing_factors</template-output>
|
||||
<template-output>system_dynamics</template-output>
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Analyze forces and constraints">
|
||||
Understand what's driving toward and resisting solution.
|
||||
|
||||
Apply **Force Field Analysis**:
|
||||
|
||||
- What forces drive toward solving this? (motivation, resources, support)
|
||||
- What forces resist solving this? (inertia, cost, complexity, politics)
|
||||
- Which forces are strongest?
|
||||
- Which can we influence?
|
||||
|
||||
Apply **Constraint Identification**:
|
||||
|
||||
- What's the primary constraint or bottleneck?
|
||||
- What limits our solution space?
|
||||
- What constraints are real vs assumed?
|
||||
|
||||
Synthesize key insights from analysis.
|
||||
|
||||
<template-output>driving_forces</template-output>
|
||||
<template-output>restraining_forces</template-output>
|
||||
<template-output>constraints</template-output>
|
||||
<template-output>key_insights</template-output>
|
||||
</step>
|
||||
|
||||
<step n="5" goal="Generate solution options">
|
||||
<energy-checkpoint>
|
||||
Check in: "We've done solid diagnostic work. How's your energy? Ready to shift into solution generation, or want a quick break?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Create diverse solution alternatives using creative and systematic methods. Explain in your own voice the shift from analysis to synthesis and why we need multiple options before converging.
|
||||
|
||||
Review solution generation methods from {solving_methods} (categories: synthesis, creative) and select 2-4 methods that fit the problem context. Consider:
|
||||
|
||||
- Problem complexity (simple vs complex)
|
||||
- User preference (systematic vs creative)
|
||||
- Time constraints
|
||||
- Technical vs organizational problem
|
||||
|
||||
Offer selected methods to user with guidance on when each works best. Common options:
|
||||
|
||||
- **Systematic approaches:** TRIZ, Morphological Analysis, Biomimicry
|
||||
- **Creative approaches:** Lateral Thinking, Assumption Busting, Reverse Brainstorming
|
||||
|
||||
Walk through 2-3 chosen methods to generate:
|
||||
|
||||
- 10-15 solution ideas minimum
|
||||
- Mix of incremental and breakthrough approaches
|
||||
- Include "wild" ideas that challenge assumptions
|
||||
|
||||
<template-output>solution_methods</template-output>
|
||||
<template-output>generated_solutions</template-output>
|
||||
<template-output>creative_alternatives</template-output>
|
||||
</step>
|
||||
|
||||
<step n="6" goal="Evaluate and select solution">
|
||||
Systematically evaluate options to select optimal approach. Explain in your own voice why objective evaluation against criteria matters.
|
||||
|
||||
Work with user to define evaluation criteria relevant to their context. Common criteria:
|
||||
|
||||
- Effectiveness - Will it solve the root cause?
|
||||
- Feasibility - Can we actually do this?
|
||||
- Cost - What's the investment required?
|
||||
- Time - How long to implement?
|
||||
- Risk - What could go wrong?
|
||||
- Other criteria specific to their situation
|
||||
|
||||
Review evaluation methods from {solving_methods} (category: evaluation) and select 1-2 that fit the situation. Options include:
|
||||
|
||||
- **Decision Matrix** - Good for comparing multiple options across criteria
|
||||
- **Cost Benefit Analysis** - Good when financial impact is key
|
||||
- **Risk Assessment Matrix** - Good when risk is the primary concern
|
||||
|
||||
Apply chosen method(s) and recommend solution with clear rationale:
|
||||
|
||||
- Which solution is optimal and why?
|
||||
- What makes you confident?
|
||||
- What concerns remain?
|
||||
- What assumptions are you making?
|
||||
|
||||
<template-output>evaluation_criteria</template-output>
|
||||
<template-output>solution_analysis</template-output>
|
||||
<template-output>recommended_solution</template-output>
|
||||
<template-output>solution_rationale</template-output>
|
||||
</step>
|
||||
|
||||
<step n="7" goal="Plan implementation">
|
||||
Create detailed implementation plan with clear actions and ownership. Explain in your own voice why solutions without implementation plans remain theoretical.
|
||||
|
||||
Define implementation approach:
|
||||
|
||||
- What's the overall strategy? (pilot, phased rollout, big bang)
|
||||
- What's the timeline?
|
||||
- Who needs to be involved?
|
||||
|
||||
Create action plan:
|
||||
|
||||
- What are specific action steps?
|
||||
- What sequence makes sense?
|
||||
- What dependencies exist?
|
||||
- Who's responsible for each?
|
||||
- What resources are needed?
|
||||
|
||||
Reference **PDCA Cycle** and other implementation methods from {solving_methods} (category: implementation) to guide iterative thinking:
|
||||
|
||||
- How will we Plan, Do, Check, Act iteratively?
|
||||
- What milestones mark progress?
|
||||
- When do we check and adjust?
|
||||
|
||||
<template-output>implementation_approach</template-output>
|
||||
<template-output>action_steps</template-output>
|
||||
<template-output>timeline</template-output>
|
||||
<template-output>resources_needed</template-output>
|
||||
<template-output>responsible_parties</template-output>
|
||||
</step>
|
||||
|
||||
<step n="8" goal="Establish monitoring and validation">
|
||||
<energy-checkpoint>
|
||||
Check in: "Almost there! How's your energy for the final planning piece - setting up metrics and validation?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Define how you'll know the solution is working and what to do if it's not.
|
||||
|
||||
Create monitoring dashboard:
|
||||
|
||||
- What metrics indicate success?
|
||||
- What targets or thresholds?
|
||||
- How will you measure?
|
||||
- How frequently will you review?
|
||||
|
||||
Plan validation:
|
||||
|
||||
- How will you validate solution effectiveness?
|
||||
- What evidence will prove it works?
|
||||
- What pilot testing is needed?
|
||||
|
||||
Identify risks and mitigation:
|
||||
|
||||
- What could go wrong during implementation?
|
||||
- How will you prevent or detect issues early?
|
||||
- What's plan B if this doesn't work?
|
||||
- What triggers adjustment or pivot?
|
||||
|
||||
<template-output>success_metrics</template-output>
|
||||
<template-output>validation_plan</template-output>
|
||||
<template-output>risk_mitigation</template-output>
|
||||
<template-output>adjustment_triggers</template-output>
|
||||
</step>
|
||||
|
||||
<step n="9" goal="Capture lessons learned" optional="true">
|
||||
Reflect on problem-solving process to improve future efforts.
|
||||
|
||||
Facilitate reflection:
|
||||
|
||||
- What worked well in this process?
|
||||
- What would you do differently?
|
||||
- What insights surprised you?
|
||||
- What patterns or principles emerged?
|
||||
- What will you remember for next time?
|
||||
|
||||
<template-output>key_learnings</template-output>
|
||||
<template-output>what_worked</template-output>
|
||||
<template-output>what_to_avoid</template-output>
|
||||
</step>
|
||||
|
||||
</workflow>
|
||||
31
_bmad/cis/workflows/problem-solving/solving-methods.csv
Normal file
31
_bmad/cis/workflows/problem-solving/solving-methods.csv
Normal file
@@ -0,0 +1,31 @@
|
||||
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?
|
||||
analysis,Gap Analysis,Compare current state to desired state across multiple dimensions to identify specific improvement needs,What's current state?|What's desired state?|What gaps exist?|How big are gaps?|What causes gaps?|Priority focus?
|
||||
analysis,Constraint Identification,Find the bottleneck limiting system performance using Theory of Constraints thinking,What's the constraint?|What limits throughput?|What should we optimize?|What happens if we elevate constraint?|What's next constraint?
|
||||
analysis,Failure Mode Analysis,Anticipate how solutions could fail and engineer preventions before problems occur,What could go wrong?|What's likelihood?|What's impact?|How do we prevent?|How do we detect early?|What's mitigation?
|
||||
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 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?
|
||||
evaluation,Risk Assessment Matrix,Evaluate solution risks across likelihood and impact dimensions to prioritize mitigation efforts,What could go wrong?|What's probability?|What's impact?|Plot on matrix|What's risk score?|Mitigation plan?
|
||||
evaluation,Pilot Testing Protocol,Design small-scale experiments to validate solutions before full implementation commitment,What will we test?|What's success criteria?|What's the test plan?|What data to collect?|What did we learn?|Scale or pivot?
|
||||
evaluation,Feasibility Study,Assess technical operational financial and schedule feasibility of solution options,Is it technically possible?|Operationally viable?|Financially sound?|Schedule realistic?|Overall feasibility?
|
||||
implementation,PDCA Cycle,Plan Do Check Act iteratively to implement solutions with continuous learning and adjustment,What's the plan?|Execute plan|Check results|What worked?|What didn't?|Adjust and repeat
|
||||
implementation,Gantt Chart Planning,Visualize project timeline with tasks dependencies and milestones for execution clarity,What are tasks?|What sequence?|What dependencies?|What's the timeline?|Who's responsible?|What milestones?
|
||||
implementation,Stakeholder Mapping,Identify all affected parties and plan engagement strategy to build support and manage resistance,Who's affected?|What's their interest?|What's their influence?|What's engagement strategy?|How to communicate?
|
||||
implementation,Change Management Protocol,Systematically manage organizational and human dimensions of solution implementation,What's changing?|Who's impacted?|What resistance expected?|How to communicate?|How to support transition?|How to sustain?
|
||||
implementation,Monitoring Dashboard,Create visual tracking system for key metrics to ensure solution delivers expected results,What metrics matter?|What targets?|How to measure?|How to visualize?|What triggers action?|Review frequency?
|
||||
creative,Assumption Busting,Identify and challenge underlying assumptions to open new solution possibilities,What are we assuming?|What if opposite were true?|What if assumption removed?|What becomes possible?
|
||||
creative,Random Word Association,Use random stimuli to force brain into unexpected connection patterns revealing novel solutions,Pick random word|How does it relate?|What connections emerge?|What ideas does it spark?|Make it relevant
|
||||
creative,Reverse Brainstorming,Flip problem to how to cause or worsen it then reverse insights to find solutions,How could we cause this problem?|How make it worse?|What would guarantee failure?|Now reverse insights|What solutions emerge?
|
||||
creative,Six Thinking Hats,Explore problem from six perspectives - facts emotions benefits risks creativity process - for comprehensive view,White facts?|Red feelings?|Yellow benefits?|Black risks?|Green alternatives?|Blue process?
|
||||
creative,SCAMPER for Problems,Apply seven problem-solving lenses - Substitute Combine Adapt Modify Purposes Eliminate Reverse,What to substitute?|What to combine?|What to adapt?|What to modify?|Other purposes?|What to eliminate?|What to reverse?
|
||||
|
165
_bmad/cis/workflows/problem-solving/template.md
Normal file
165
_bmad/cis/workflows/problem-solving/template.md
Normal file
@@ -0,0 +1,165 @@
|
||||
# Problem Solving Session: {{problem_title}}
|
||||
|
||||
**Date:** {{date}}
|
||||
**Problem Solver:** {{user_name}}
|
||||
**Problem Category:** {{problem_category}}
|
||||
|
||||
---
|
||||
|
||||
## 🎯 PROBLEM DEFINITION
|
||||
|
||||
### Initial Problem Statement
|
||||
|
||||
{{initial_problem}}
|
||||
|
||||
### Refined Problem Statement
|
||||
|
||||
{{refined_problem_statement}}
|
||||
|
||||
### Problem Context
|
||||
|
||||
{{problem_context}}
|
||||
|
||||
### Success Criteria
|
||||
|
||||
{{success_criteria}}
|
||||
|
||||
---
|
||||
|
||||
## 🔍 DIAGNOSIS AND ROOT CAUSE ANALYSIS
|
||||
|
||||
### Problem Boundaries (Is/Is Not)
|
||||
|
||||
{{problem_boundaries}}
|
||||
|
||||
### Root Cause Analysis
|
||||
|
||||
{{root_cause_analysis}}
|
||||
|
||||
### Contributing Factors
|
||||
|
||||
{{contributing_factors}}
|
||||
|
||||
### System Dynamics
|
||||
|
||||
{{system_dynamics}}
|
||||
|
||||
---
|
||||
|
||||
## 📊 ANALYSIS
|
||||
|
||||
### Force Field Analysis
|
||||
|
||||
**Driving Forces (Supporting Solution):**
|
||||
{{driving_forces}}
|
||||
|
||||
**Restraining Forces (Blocking Solution):**
|
||||
{{restraining_forces}}
|
||||
|
||||
### Constraint Identification
|
||||
|
||||
{{constraints}}
|
||||
|
||||
### Key Insights
|
||||
|
||||
{{key_insights}}
|
||||
|
||||
---
|
||||
|
||||
## 💡 SOLUTION GENERATION
|
||||
|
||||
### Methods Used
|
||||
|
||||
{{solution_methods}}
|
||||
|
||||
### Generated Solutions
|
||||
|
||||
{{generated_solutions}}
|
||||
|
||||
### Creative Alternatives
|
||||
|
||||
{{creative_alternatives}}
|
||||
|
||||
---
|
||||
|
||||
## ⚖️ SOLUTION EVALUATION
|
||||
|
||||
### Evaluation Criteria
|
||||
|
||||
{{evaluation_criteria}}
|
||||
|
||||
### Solution Analysis
|
||||
|
||||
{{solution_analysis}}
|
||||
|
||||
### Recommended Solution
|
||||
|
||||
{{recommended_solution}}
|
||||
|
||||
### Rationale
|
||||
|
||||
{{solution_rationale}}
|
||||
|
||||
---
|
||||
|
||||
## 🚀 IMPLEMENTATION PLAN
|
||||
|
||||
### Implementation Approach
|
||||
|
||||
{{implementation_approach}}
|
||||
|
||||
### Action Steps
|
||||
|
||||
{{action_steps}}
|
||||
|
||||
### Timeline and Milestones
|
||||
|
||||
{{timeline}}
|
||||
|
||||
### Resource Requirements
|
||||
|
||||
{{resources_needed}}
|
||||
|
||||
### Responsible Parties
|
||||
|
||||
{{responsible_parties}}
|
||||
|
||||
---
|
||||
|
||||
## 📈 MONITORING AND VALIDATION
|
||||
|
||||
### Success Metrics
|
||||
|
||||
{{success_metrics}}
|
||||
|
||||
### Validation Plan
|
||||
|
||||
{{validation_plan}}
|
||||
|
||||
### Risk Mitigation
|
||||
|
||||
{{risk_mitigation}}
|
||||
|
||||
### Adjustment Triggers
|
||||
|
||||
{{adjustment_triggers}}
|
||||
|
||||
---
|
||||
|
||||
## 📝 LESSONS LEARNED
|
||||
|
||||
### Key Learnings
|
||||
|
||||
{{key_learnings}}
|
||||
|
||||
### What Worked
|
||||
|
||||
{{what_worked}}
|
||||
|
||||
### What to Avoid
|
||||
|
||||
{{what_to_avoid}}
|
||||
|
||||
---
|
||||
|
||||
_Generated using BMAD Creative Intelligence Suite - Problem Solving Workflow_
|
||||
26
_bmad/cis/workflows/problem-solving/workflow.yaml
Normal file
26
_bmad/cis/workflows/problem-solving/workflow.yaml
Normal file
@@ -0,0 +1,26 @@
|
||||
# Problem Solving Workflow Configuration
|
||||
name: "problem-solving"
|
||||
description: 'Apply systematic problem-solving methodologies to complex challenges. Use when the user says "guide me through structured problem solving" or "I want to crack this challenge with guided problem solving techniques"'
|
||||
|
||||
# Critical variables load from config_source
|
||||
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
|
||||
|
||||
# Context can be provided via data attribute when invoking
|
||||
# Example: data="{path}/problem-brief.md" provides context
|
||||
|
||||
# Module path and component files
|
||||
installed_path: "{project-root}/_bmad/cis/workflows/problem-solving"
|
||||
template: "{installed_path}/template.md"
|
||||
instructions: "{installed_path}/instructions.md"
|
||||
|
||||
# Required Data Files
|
||||
solving_methods: "{installed_path}/solving-methods.csv"
|
||||
|
||||
# Output configuration
|
||||
default_output_file: "{output_folder}/problem-solution-{{date}}.md"
|
||||
|
||||
standalone: true
|
||||
293
_bmad/cis/workflows/storytelling/instructions.md
Normal file
293
_bmad/cis/workflows/storytelling/instructions.md
Normal file
@@ -0,0 +1,293 @@
|
||||
# Storytelling Workflow Instructions
|
||||
|
||||
## Workflow
|
||||
|
||||
<workflow>
|
||||
<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>
|
||||
<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
|
||||
<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</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">
|
||||
<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>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="2" goal="Select Story Framework">
|
||||
|
||||
<action>Load story frameworks from {story_frameworks} CSV file</action>
|
||||
<action>Parse: story_type, name, description, key_elements, best_for</action>
|
||||
|
||||
Based on the context from Step 1, present framework options:
|
||||
|
||||
<ask response="framework_selection">
|
||||
I can help craft your story using these proven narrative frameworks:
|
||||
|
||||
**Transformation Narratives:**
|
||||
|
||||
1. **Hero's Journey** - Classic transformation arc with adventure and return
|
||||
2. **Pixar Story Spine** - Emotional structure building tension to resolution
|
||||
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
|
||||
|
||||
**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)
|
||||
</ask>
|
||||
|
||||
<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>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Gather Story Elements">
|
||||
|
||||
<critical>
|
||||
YOU ARE A MASTER STORYTELLER: Guide through narrative development using the Socratic method. Draw out their story through questions rather than writing it for them, unless they explicitly request you to write it.
|
||||
</critical>
|
||||
|
||||
<storytelling-principles>
|
||||
- Every great story has conflict/tension - Find the struggle
|
||||
- Show, don't tell - Use vivid, concrete details
|
||||
- Change is essential - What transforms?
|
||||
- Emotion drives memory - Find the feeling
|
||||
- Authenticity resonates - Stay true to core truth
|
||||
</storytelling-principles>
|
||||
|
||||
Based on selected framework, gather key story elements:
|
||||
|
||||
<action>Reference key_elements from selected story_type in CSV</action>
|
||||
<action>Parse key_elements (pipe-separated) into individual components</action>
|
||||
<action>Guide user through each element with targeted questions</action>
|
||||
|
||||
<framework-specific-guidance>
|
||||
|
||||
For Hero's Journey:
|
||||
|
||||
- <ask>Who/what is the hero of this story?</ask>
|
||||
- <ask>What's their ordinary world before the adventure?</ask>
|
||||
- <ask>What call to adventure disrupts their world?</ask>
|
||||
- <ask>What trials/challenges do they face?</ask>
|
||||
- <ask>How are they transformed by the journey?</ask>
|
||||
- <ask>What wisdom do they bring back?</ask>
|
||||
|
||||
For Pixar Story Spine:
|
||||
|
||||
- <ask>Once upon a time, what was the situation?</ask>
|
||||
- <ask>Every day, what was the routine?</ask>
|
||||
- <ask>Until one day, what changed?</ask>
|
||||
- <ask>Because of that, what happened next?</ask>
|
||||
- <ask>And because of that? (continue chain)</ask>
|
||||
- <ask>Until finally, how was it resolved?</ask>
|
||||
|
||||
For Brand Story:
|
||||
|
||||
- <ask>What was the origin spark for this brand?</ask>
|
||||
- <ask>What core values drive every decision?</ask>
|
||||
- <ask>How does this impact customers/users?</ask>
|
||||
- <ask>What makes this different from alternatives?</ask>
|
||||
- <ask>Where is this heading in the future?</ask>
|
||||
|
||||
For Pitch Narrative:
|
||||
|
||||
- <ask>What's the problem landscape you're addressing?</ask>
|
||||
- <ask>What's your vision for the solution?</ask>
|
||||
- <ask>What proof/traction validates this approach?</ask>
|
||||
- <ask>What action do you want the audience to take?</ask>
|
||||
|
||||
For Data Storytelling:
|
||||
|
||||
- <ask>What context does the audience need?</ask>
|
||||
- <ask>What's the key data revelation/insight?</ask>
|
||||
- <ask>What patterns explain this insight?</ask>
|
||||
- <ask>So what? Why does this matter?</ask>
|
||||
- <ask>What actions should this insight drive?</ask>
|
||||
|
||||
</framework-specific-guidance>
|
||||
|
||||
<template-output>story_beats, character_voice, conflict_tension, transformation</template-output>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Craft Emotional Arc">
|
||||
|
||||
Stories stick when they resonate emotionally. Develop the emotional journey:
|
||||
|
||||
<ask>What emotion should the audience feel at the beginning?</ask>
|
||||
<ask>What emotional shift happens at the turning point?</ask>
|
||||
<ask>What emotion should they carry away at the end?</ask>
|
||||
<ask>Where are the emotional peaks (high tension/joy)?</ask>
|
||||
<ask>Where are the valleys (low points/struggle)?</ask>
|
||||
|
||||
<guide>Help them identify:
|
||||
|
||||
- Relatable struggles that create empathy
|
||||
- Surprising moments that capture attention
|
||||
- Personal stakes that make it matter
|
||||
- Satisfying payoffs that create resolution
|
||||
</guide>
|
||||
|
||||
<template-output>emotional_arc, emotional_touchpoints</template-output>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="5" goal="Develop Opening Hook">
|
||||
|
||||
The first moment determines if they keep reading/listening.
|
||||
|
||||
<ask>What surprising fact, question, or statement could open this story?</ask>
|
||||
<ask>What's the most intriguing part of this story to lead with?</ask>
|
||||
|
||||
<guide>A strong hook:
|
||||
|
||||
- Surprises or challenges assumptions
|
||||
- Raises an urgent question
|
||||
- Creates immediate relatability
|
||||
- Promises valuable payoff
|
||||
- Uses vivid, concrete details
|
||||
</guide>
|
||||
|
||||
<template-output>opening_hook</template-output>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="6" goal="Write Core Narrative">
|
||||
|
||||
<ask>Would you like to:
|
||||
|
||||
1. Draft the story yourself with my guidance
|
||||
2. Have me write the first draft based on what we've discussed
|
||||
3. Co-create it iteratively together
|
||||
</ask>
|
||||
|
||||
<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 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>
|
||||
<action>Include vivid details and emotional beats</action>
|
||||
<action>Present draft for feedback and refinement</action>
|
||||
</if>
|
||||
|
||||
<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>
|
||||
</if>
|
||||
|
||||
<template-output>complete_story, core_narrative</template-output>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="7" goal="Create Story Variations">
|
||||
|
||||
Adapt the story for different contexts and lengths:
|
||||
|
||||
<ask>What channels or formats will you use this story in?</ask>
|
||||
|
||||
Based on response, create appropriate variations:
|
||||
|
||||
1. **Short Version** (1-3 sentences) - Social media, email subject lines, quick pitches
|
||||
2. **Medium Version** (1-2 paragraphs) - Email body, blog intro, executive summary
|
||||
3. **Extended Version** (full narrative) - Articles, presentations, case studies, website
|
||||
|
||||
<template-output>short_version, medium_version, extended_version</template-output>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="8" goal="Usage Guidelines">
|
||||
|
||||
Provide strategic guidance for story deployment:
|
||||
|
||||
<ask>Where and how will you use this story?</ask>
|
||||
|
||||
<guide>Consider:
|
||||
|
||||
- Best channels for this story type
|
||||
- Audience-specific adaptations needed
|
||||
- Tone/voice consistency with brand
|
||||
- Visual or multimedia enhancements
|
||||
- Testing and feedback approach
|
||||
</guide>
|
||||
|
||||
<template-output>best_channels, audience_considerations, tone_notes, adaptation_suggestions</template-output>
|
||||
|
||||
</step>
|
||||
|
||||
<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>resolution, refinement_opportunities, additional_versions, feedback_plan</template-output>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="10" goal="Generate Final Output">
|
||||
|
||||
Compile all story components into the structured template:
|
||||
|
||||
1. Ensure all story versions are complete and polished
|
||||
2. Format according to template structure
|
||||
3. Include all strategic guidance and usage notes
|
||||
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>
|
||||
|
||||
</workflow>
|
||||
26
_bmad/cis/workflows/storytelling/story-types.csv
Normal file
26
_bmad/cis/workflows/storytelling/story-types.csv
Normal file
@@ -0,0 +1,26 @@
|
||||
category,story_type,name,description,key_questions
|
||||
transformation,hero-journey,Hero's Journey,Classic transformation arc following protagonist through adventure and return with wisdom,Who is the hero?|What's their ordinary world?|What call disrupts their world?|What trials do they face?|How are they transformed?
|
||||
transformation,pixar-spine,Pixar Story Spine,Emotional narrative structure using once upon a time framework that builds tension to resolution,Once upon a time what?|Every day what happened?|Until one day what changed?|Because of that what?|Until finally how resolved?
|
||||
transformation,customer-journey,Customer Journey,Narrative following customer transformation from pain point through solution to success,What was the before struggle?|What discovery moment occurred?|How did they implement?|What transformation happened?|What's their new reality?
|
||||
transformation,challenge-overcome,Challenge Overcome,Dramatic structure centered on confronting and conquering significant obstacles,What obstacle blocked progress?|How did stakes escalate?|What was the darkest moment?|What breakthrough occurred?|What was learned?
|
||||
transformation,character-arc,Character Arc,Personal evolution story showing growth through experience and struggle,Who are they at start?|What forces change?|What do they resist?|What breakthrough shifts them?|Who have they become?
|
||||
strategic,brand-story,Brand Story,Authentic narrative communicating brand values mission and unique market position,What sparked this brand?|What core values drive it?|How does it impact customers?|What makes it different?|Where is it heading?
|
||||
strategic,vision-narrative,Vision Narrative,Future-focused story painting vivid picture of desired state and path to get there,What's the current reality?|What opportunity emerges?|What's the bold vision?|What's the strategic path?|What does transformed future look like?
|
||||
strategic,origin-story,Origin Story,Foundational narrative explaining how something came to be and why it matters today,What was the spark moment?|What early struggles occurred?|What key breakthrough happened?|How did it evolve?|What's the current mission?
|
||||
strategic,positioning-story,Positioning Story,Narrative establishing unique market position and competitive differentiation,What market gap exists?|How are you uniquely qualified?|What makes your approach different?|Why should audience care?|What future do you enable?
|
||||
strategic,culture-story,Culture Story,Internal narrative defining organizational values behaviors and identity,What principles guide decisions?|What behaviors exemplify culture?|What stories illustrate values?|How do people experience it?|What culture are you building?
|
||||
persuasive,pitch-narrative,Pitch Narrative,Compelling story structure designed to inspire action investment or partnership,What problem landscape exists?|What's your vision for solution?|What proof validates approach?|What's the opportunity size?|What action do you want?
|
||||
persuasive,sales-story,Sales Story,Customer-centric narrative demonstrating value and building desire for solution,What pain do they feel?|How do you understand it?|What solution transforms situation?|What results can they expect?|What's the path forward?
|
||||
persuasive,change-story,Change Story,Narrative making case for transformation and mobilizing people through transition,Why can't we stay here?|What does better look like?|What's at stake if we don't?|How do we get there?|What's in it for them?
|
||||
persuasive,fundraising-story,Fundraising Story,Emotionally compelling narrative connecting donor values to mission impact,What problem breaks hearts?|What solution creates hope?|What impact will investment make?|Why is this urgent?|How can they help?
|
||||
persuasive,advocacy-story,Advocacy Story,Story galvanizing support for cause movement or policy change,What injustice demands attention?|Who is affected and how?|What change is needed?|What happens if we act?|How can they join?
|
||||
analytical,data-story,Data Storytelling,Transform data insights into compelling narrative with clear actionable takeaways,What context is needed?|What data reveals insight?|What patterns explain it?|So what why does it matter?|What actions should follow?
|
||||
analytical,case-study,Case Study,Detailed narrative documenting real-world application results and learnings,What was the situation?|What approach was taken?|What challenges emerged?|What results were achieved?|What lessons transfer?
|
||||
analytical,research-story,Research Narrative,Story structure presenting research findings in accessible engaging way,What question drove research?|How was it investigated?|What did you discover?|What does it mean?|What are implications?
|
||||
analytical,insight-narrative,Insight Narrative,Narrative revealing non-obvious truth or pattern that shifts understanding,What did everyone assume?|What did you notice?|What deeper pattern emerged?|Why does it matter?|What should change?
|
||||
analytical,process-story,Process Story,Behind-the-scenes narrative showing how something was made or accomplished,What was being created?|What approach was chosen?|What challenges arose?|How were they solved?|What was learned?
|
||||
emotional,hook-driven,Hook Driven,Story structure maximizing emotional engagement through powerful opening and touchpoints,What surprising fact opens?|What urgent question emerges?|Where are emotional peaks?|What creates relatability?|What payoff satisfies?
|
||||
emotional,conflict-resolution,Conflict Resolution,Narrative centered on tension building and satisfying resolution of core conflict,What's the central conflict?|Who wants what and why?|What prevents resolution?|How does tension escalate?|How is it resolved?
|
||||
emotional,empathy-story,Empathy Story,Story designed to create emotional connection and understanding of other perspectives,Whose perspective are we taking?|What do they experience?|What do they feel?|Why should audience care?|What common ground exists?
|
||||
emotional,human-interest,Human Interest,Personal story highlighting universal human experiences and emotions,Who is at the center?|What personal stakes exist?|What universal themes emerge?|What emotional journey occurs?|What makes it relatable?
|
||||
emotional,vulnerable-story,Vulnerable Story,Authentic personal narrative sharing struggle failure or raw truth to build connection,What truth is hard to share?|What struggle was faced?|What was learned?|Why share this now?|What hope does it offer?
|
||||
|
113
_bmad/cis/workflows/storytelling/template.md
Normal file
113
_bmad/cis/workflows/storytelling/template.md
Normal file
@@ -0,0 +1,113 @@
|
||||
# Story Output
|
||||
|
||||
**Created:** {{date}}
|
||||
**Storyteller:** {{agent_role}} {{agent_name}}
|
||||
**Author:** {{user_name}}
|
||||
|
||||
## Story Information
|
||||
|
||||
**Story Type:** {{story_type}}
|
||||
|
||||
**Framework Used:** {{framework_name}}
|
||||
|
||||
**Purpose:** {{story_purpose}}
|
||||
|
||||
**Target Audience:** {{target_audience}}
|
||||
|
||||
## Story Structure
|
||||
|
||||
### Opening Hook
|
||||
|
||||
{{opening_hook}}
|
||||
|
||||
### Core Narrative
|
||||
|
||||
{{core_narrative}}
|
||||
|
||||
### Key Story Beats
|
||||
|
||||
{{story_beats}}
|
||||
|
||||
### Emotional Arc
|
||||
|
||||
{{emotional_arc}}
|
||||
|
||||
### Resolution/Call to Action
|
||||
|
||||
{{resolution}}
|
||||
|
||||
## Complete Story
|
||||
|
||||
{{complete_story}}
|
||||
|
||||
## Story Elements Analysis
|
||||
|
||||
### Character/Voice
|
||||
|
||||
{{character_voice}}
|
||||
|
||||
### Conflict/Tension
|
||||
|
||||
{{conflict_tension}}
|
||||
|
||||
### Transformation/Change
|
||||
|
||||
{{transformation}}
|
||||
|
||||
### Emotional Touchpoints
|
||||
|
||||
{{emotional_touchpoints}}
|
||||
|
||||
### Key Messages
|
||||
|
||||
{{key_messages}}
|
||||
|
||||
## Variations AND Adaptations
|
||||
|
||||
### Short Version (Tweet/Social)
|
||||
|
||||
{{short_version}}
|
||||
|
||||
### Medium Version (Email/Blog)
|
||||
|
||||
{{medium_version}}
|
||||
|
||||
### Extended Version (Article/Presentation)
|
||||
|
||||
{{extended_version}}
|
||||
|
||||
## Usage Guidelines
|
||||
|
||||
### Best Channels
|
||||
|
||||
{{best_channels}}
|
||||
|
||||
### Audience Considerations
|
||||
|
||||
{{audience_considerations}}
|
||||
|
||||
### Tone AND Voice Notes
|
||||
|
||||
{{tone_notes}}
|
||||
|
||||
### Adaptation Suggestions
|
||||
|
||||
{{adaptation_suggestions}}
|
||||
|
||||
## Next Steps
|
||||
|
||||
### Refinement Opportunities
|
||||
|
||||
{{refinement_opportunities}}
|
||||
|
||||
### Additional Versions Needed
|
||||
|
||||
{{additional_versions}}
|
||||
|
||||
### Testing/Feedback Plan
|
||||
|
||||
{{feedback_plan}}
|
||||
|
||||
---
|
||||
|
||||
_Story crafted using the BMAD CIS storytelling framework_
|
||||
26
_bmad/cis/workflows/storytelling/workflow.yaml
Normal file
26
_bmad/cis/workflows/storytelling/workflow.yaml
Normal file
@@ -0,0 +1,26 @@
|
||||
# Storytelling Workflow Configuration
|
||||
name: "storytelling"
|
||||
description: 'Craft compelling narratives using story frameworks. Use when the user says "help me with storytelling" or "I want to create a narrative through storytelling"'
|
||||
|
||||
# Critical variables load from config_source
|
||||
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
|
||||
|
||||
# Context can be provided via data attribute when invoking
|
||||
# Example: data="{path}/brand-info.md" provides brand context
|
||||
|
||||
# Module path and component files
|
||||
installed_path: "{project-root}/_bmad/cis/workflows/storytelling"
|
||||
template: "{installed_path}/template.md"
|
||||
instructions: "{installed_path}/instructions.md"
|
||||
|
||||
# Required Data Files
|
||||
story_frameworks: "{installed_path}/story-types.csv"
|
||||
|
||||
# Output configuration
|
||||
default_output_file: "{output_folder}/story-{{date}}.md"
|
||||
|
||||
standalone: true
|
||||
Reference in New Issue
Block a user