create-byan-agent 2.1.0 → 2.1.1

package/_bmad/cis/workflows/problem-solving/instructions.md

@@ -1,252 +0,0 @@
-# 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>

package/_bmad/cis/workflows/problem-solving/solving-methods.csv

@@ -1,31 +0,0 @@
-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?

package/_bmad/cis/workflows/problem-solving/template.md

@@ -1,165 +0,0 @@
-# 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_

package/_bmad/cis/workflows/problem-solving/workflow.yaml

@@ -1,27 +0,0 @@
-# Problem Solving Workflow Configuration
-name: "problem-solving"
-description: "Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks."
-author: "BMad"
-
-# 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

package/_bmad/cis/workflows/storytelling/README.md

@@ -1,58 +0,0 @@
----
-last-redoc-date: 2025-09-28
----
-
-# Storytelling Workflow
-
-**Type:** Interactive Document Workflow
-**Module:** Creative Intelligence System (CIS)
-
-## Purpose
-
-Crafts compelling narratives using proven story frameworks and techniques. Guides structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose—brand narratives, user stories, change communications, or creative fiction.
-
-## Distinctive Features
-
-- **Framework Library**: Comprehensive story frameworks in `story-types.csv` (Hero's Journey, Three-Act Structure, Story Brand, etc.)
-- **Emotional Psychology**: Leverages deep understanding of universal human themes and emotional connection
-- **Platform Adaptation**: Tailors narrative structure to medium and audience
-- **Whimsical Facilitation**: Flowery, enrapturing communication style that embodies master storytelling
-
-## Usage
-
-```bash
-# Basic invocation
-workflow storytelling
-
-# With brand or project context
-workflow storytelling --data /path/to/brand-info.md
-```
-
-## Inputs
-
-- **story_purpose**: Why the story is being told (persuade, educate, entertain, inspire)
-- **target_audience**: Who will experience the narrative
-- **story_subject**: What or whom the story is about
-- **platform_medium**: Where the story will be told
-- **desired_impact**: What audience should feel/think/do after
-
-## Outputs
-
-**File:** `{output_folder}/story-{date}.md`
-
-**Structure:**
-
-- Story framework selection and rationale
-- Character development and voice
-- Narrative arc with tension and resolution
-- Emotional beats and human truths
-- Vivid sensory details and concrete moments
-- Platform-specific adaptations
-- Impact measurement approach
-
-## Workflow Components
-
-- `workflow.yaml` - Configuration with story_frameworks CSV reference
-- `instructions.md` - Narrative development facilitation guide
-- `template.md` - Story output format
-- `story-types.csv` - Narrative framework library