create-byan-agent 2.18.0 → 2.19.1

package/install/templates/_byan/cis/workflows/innovation-strategy/instructions.md

@@ -1,276 +0,0 @@
-# Innovation Strategy Workflow Instructions
-
-<critical>The workflow execution engine is governed by: {project-root}/_byan/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/_byan/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>

package/install/templates/_byan/cis/workflows/innovation-strategy/workflow.yaml

@@ -1,27 +0,0 @@
-# Innovation Strategy Workflow Configuration
-name: "innovation-strategy"
-description: "Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities."
-author: "BMad"
-
-# Critical variables load from config_source
-config_source: "{project-root}/_byan/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}/_byan/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

package/install/templates/_byan/cis/workflows/problem-solving/instructions.md

@@ -1,252 +0,0 @@
-# Problem Solving Workflow Instructions
-
-<critical>The workflow execution engine is governed by: {project-root}/_byan/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/_byan/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/install/templates/_byan/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}/_byan/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}/_byan/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