bmad-method 6.0.0-alpha.9 → 6.0.1

package/src/core/tasks/adv-elicit-methods.csv

@@ -1,39 +0,0 @@
-category,method_name,description,output_pattern
-advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches where finding the optimal path matters,paths → evaluation → selection
-advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns in complex multi-factor situations,nodes → connections → patterns
-advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency in lengthy analyses,context → thread → synthesis
-advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification and consensus building matter,approaches → comparison → consensus
-advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving strategies,current → analysis → optimization
-advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making tasks,model → planning → strategy
-collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
-collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
-competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions through adversarial thinking,defense → attack → hardening
-core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - essential when content needs to match specific reader capabilities,audience → adjustments → refined content
-core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts needing polish and enhancement,strengths/weaknesses → improvements → refined version
-core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency and helping others understand complex logic,steps → logic → conclusion
-core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving seemingly impossible problems,assumptions → truths → new approach
-core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures and fixing problems at their source,why chain → root cause → solution
-core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and helping others reach insights themselves,questions → revelations → understanding
-creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding how to reach specific endpoints,end state → steps backward → path forward
-creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and creative exploration,scenarios → implications → insights
-creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation and improvement,S→C→A→M→P→E→R
-learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding and excellent for knowledge transfer,complex → simple → gaps → mastery
-learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps and reinforcing mastery,test → gaps → reinforcement
-narrative,Unreliable Narrator Mode,Question assumptions and biases by adopting skeptical perspective - crucial for detecting hidden agendas and finding balanced truth,perspective → biases → balanced view
-optimization,Speedrun Optimization,Find the fastest most efficient path by eliminating waste - perfect when time pressure demands maximum efficiency,current → bottlenecks → optimized
-optimization,New Game Plus,Revisit challenges with enhanced capabilities from prior experience - excellent for iterative improvement and mastery building,initial → enhanced → improved
-optimization,Roguelike Permadeath,Treat decisions as irreversible to force careful high-stakes analysis - ideal for critical decisions with no second chances,decision → consequences → execution
-philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging and theory selection,options → simplification → selection
-philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and making difficult ethical decisions,dilemma → analysis → decision
-quantum,Observer Effect Consideration,Analyze how the act of measurement changes what's being measured - important for understanding metrics impact and self-aware systems,unmeasured → observation → impact
-retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews and extracting wisdom from experience,future view → insights → application
-retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for knowledge transfer and continuous improvement,experience → lessons → actions
-risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
-risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink and building robust solutions,assumptions → challenges → strengthening
-risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
-risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
-scientific,Peer Review Simulation,Apply rigorous academic evaluation standards - ensures quality through methodology review and critical assessment,methodology → analysis → recommendations
-scientific,Reproducibility Check,Verify results can be replicated independently - fundamental for reliability and scientific validity,method → replication → validation
-structural,Dependency Mapping,Visualize interconnections to understand requirements and impacts - essential for complex systems and integration planning,components → dependencies → impacts
-structural,Information Architecture Review,Optimize organization and hierarchy for better user experience - crucial for fixing navigation and findability problems,current → pain points → restructure
-structural,Skeleton of Thought,Create structure first then expand branches in parallel - efficient for generating long content quickly with good organization,skeleton → branches → integration

package/src/core/tasks/advanced-elicitation.xml

@@ -1,106 +0,0 @@
-<task id="{bmad_folder}/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
-  methods="{project-root}/{bmad_folder}/core/tasks/advanced-elicitation-methods.csv"
-  agent-party="{project-root}/{bmad_folder}/_cfg/agent-manifest.csv">
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-
-  <integration description="When called from workflow">
-    <desc>When called during template workflow processing:</desc>
-    <i>1. Receive or review the current section content that was just generated or</i>
-    <i>2. Apply elicitation methods iteratively to enhance that specific content</i>
-    <i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
-    <i>4. The enhanced content replaces the original section content in the output document</i>
-  </integration>
-
-  <flow>
-    <step n="1" title="Method Registry Loading">
-      <action>Load and read {{methods}} and {{agent-party}}</action>
-
-      <csv-structure>
-        <i>category: Method grouping (core, structural, risk, etc.)</i>
-        <i>method_name: Display name for the method</i>
-        <i>description: Rich explanation of what the method does, when to use it, and why it's valuable</i>
-        <i>output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action")</i>
-      </csv-structure>
-
-      <context-analysis>
-        <i>Use conversation history</i>
-        <i>Analyze: content type, complexity, stakeholder needs, risk level, and creative potential</i>
-      </context-analysis>
-
-      <smart-selection>
-        <i>1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential</i>
-        <i>2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV</i>
-        <i>3. Select 5 methods: Choose methods that best match the context based on their descriptions</i>
-        <i>4. Balance approach: Include mix of foundational and specialized techniques as appropriate</i>
-      </smart-selection>
-    </step>
-
-    <step n="2" title="Present Options and Handle Responses">
-
-      <format>
-        **Advanced Elicitation Options**
-        Choose a number (1-5), r to shuffle, or x to proceed:
-
-        1. [Method Name]
-        2. [Method Name]
-        3. [Method Name]
-        4. [Method Name]
-        5. [Method Name]
-        r. Reshuffle the list with 5 new options
-        x. Proceed / No Further Actions
-      </format>
-
-      <response-handling>
-        <case n="1-5">
-          <i>Execute the selected method using its description from the CSV</i>
-          <i>Adapt the method's complexity and output format based on the current context</i>
-          <i>Apply the method creatively to the current section content being enhanced</i>
-          <i>Display the enhanced version showing what the method revealed or improved</i>
-          <i>CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.</i>
-          <i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to
-            follow the instructions given by the user.</i>
-          <i>CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
-        </case>
-        <case n="r">
-          <i>Select 5 different methods from advanced-elicitation-methods.csv, present new list with same prompt format</i>
-        </case>
-        <case n="x">
-          <i>Complete elicitation and proceed</i>
-          <i>Return the fully enhanced content back to create-doc.md</i>
-          <i>The enhanced content becomes the final version for that section</i>
-          <i>Signal completion back to create-doc.md to continue with next section</i>
-        </case>
-        <case n="direct-feedback">
-          <i>Apply changes to current section content and re-present choices</i>
-        </case>
-        <case n="multiple-numbers">
-          <i>Execute methods in sequence on the content, then re-offer choices</i>
-        </case>
-      </response-handling>
-    </step>
-
-    <step n="3" title="Execution Guidelines">
-      <i>Method execution: Use the description from CSV to understand and apply each method</i>
-      <i>Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")</i>
-      <i>Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)</i>
-      <i>Creative application: Interpret methods flexibly based on context while maintaining pattern consistency</i>
-      <i>Be concise: Focus on actionable insights</i>
-      <i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from create-doc)</i>
-      <i>Identify personas: For multi-persona methods, clearly identify viewpoints</i>
-      <i>Critical loop behavior: Always re-offer the 1-5,r,x choices after each method execution</i>
-      <i>Continue until user selects 'x' to proceed with enhanced content</i>
-      <i>Each method application builds upon previous enhancements</i>
-      <i>Content preservation: Track all enhancements made during elicitation</i>
-      <i>Iterative enhancement: Each selected method (1-5) should:</i>
-      <i> 1. Apply to the current enhanced version of the content</i>
-      <i> 2. Show the improvements made</i>
-      <i> 3. Return to the prompt for additional elicitations or completion</i>
-    </step>
-  </flow>
-</task>

package/src/core/tasks/validate-workflow.xml

@@ -1,89 +0,0 @@
-<task id="{bmad_folder}/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
-  <objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
-
-  <inputs>
-    <input name="workflow" desc="Workflow path containing checklist.md" />
-    <input name="checklist" desc="Checklist to validate against (defaults to workflow's checklist.md)" />
-    <input name="document" desc="Document to validate (ask user if not specified)" />
-  </inputs>
-
-  <flow>
-    <step n="1" title="Setup">
-      <action>If checklist not provided, load checklist.md from workflow location</action>
-      <action>Try to fuzzy match for files similar to the input document name or if user did not provide the document. If document not
-        provided or unsure, ask user: "Which document should I validate?"</action>
-      <action>Load both the checklist and document</action>
-    </step>
-
-    <step n="2" title="Validate" critical="true">
-      <mandate>For EVERY checklist item, WITHOUT SKIPPING ANY:</mandate>
-
-      <for-each-item>
-        <action>Read requirement carefully</action>
-        <action>Search document for evidence along with any ancillary loaded documents or artifacts (quotes with line numbers)</action>
-        <action>Analyze deeply - look for explicit AND implied coverage</action>
-
-        <mark-as>
-          ✓ PASS - Requirement fully met (provide evidence)
-          ⚠ PARTIAL - Some coverage but incomplete (explain gaps)
-          ✗ FAIL - Not met or severely deficient (explain why)
-          ➖ N/A - Not applicable (explain reason)
-        </mark-as>
-      </for-each-item>
-
-      <critical>DO NOT SKIP ANY SECTIONS OR ITEMS</critical>
-    </step>
-
-    <step n="3" title="Generate Report">
-      <action>Create validation-report-{timestamp}.md in document's folder</action>
-
-      <report-format>
-        # Validation Report
-
-        **Document:** {document-path}
-        **Checklist:** {checklist-path}
-        **Date:** {timestamp}
-
-        ## Summary
-        - Overall: X/Y passed (Z%)
-        - Critical Issues: {count}
-
-        ## Section Results
-
-        ### {Section Name}
-        Pass Rate: X/Y (Z%)
-
-        {For each item:}
-        [MARK] {Item description}
-        Evidence: {Quote with line# or explanation}
-        {If FAIL/PARTIAL: Impact: {why this matters}}
-
-        ## Failed Items
-        {All ✗ items with recommendations}
-
-        ## Partial Items
-        {All ⚠ items with what's missing}
-
-        ## Recommendations
-        1. Must Fix: {critical failures}
-        2. Should Improve: {important gaps}
-        3. Consider: {minor improvements}
-      </report-format>
-    </step>
-
-    <step n="4" title="Summary for User">
-      <action>Present section-by-section summary</action>
-      <action>Highlight all critical issues</action>
-      <action>Provide path to saved report</action>
-      <action>HALT - do not continue unless user asks</action>
-    </step>
-  </flow>
-
-  <critical-rules>
-    <rule>NEVER skip sections - validate EVERYTHING</rule>
-    <rule>ALWAYS provide evidence (quotes + line numbers) for marks</rule>
-    <rule>Think deeply about each requirement - don't rush</rule>
-    <rule>Save report to document's folder automatically</rule>
-    <rule>HALT after presenting summary - wait for user</rule>
-  </critical-rules>
-</task>

package/src/core/tools/shard-doc.xml

@@ -1,109 +0,0 @@
-<tool id="{bmad_folder}/core/tasks/shard-doc" name="Shard Document"
-  description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
-  standalone="true">
-  <objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>
-
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-
-  <critical-context>
-    <i>Uses `npx @kayvan/markdown-tree-parser` to automatically shard documents by level 2 headings and generate an index</i>
-  </critical-context>
-
-  <flow>
-    <step n="1" title="Get Source Document">
-      <action>Ask user for the source document path if not provided already</action>
-      <action>Verify file exists and is accessible</action>
-      <action>Verify file is markdown format (.md extension)</action>
-      <action if="file not found or not markdown">HALT with error message</action>
-    </step>
-
-    <step n="2" title="Get Destination Folder">
-      <action>Determine default destination: same location as source file, folder named after source file without .md extension</action>
-      <action>Example: /path/to/architecture.md → /path/to/architecture/</action>
-      <action>Ask user for the destination folder path ([y] to confirm use of default: [suggested-path], else enter a new path)</action>
-      <action if="user accepts default">Use the suggested destination path</action>
-      <action if="user provides custom path">Use the custom destination path</action>
-      <action>Verify destination folder exists or can be created</action>
-      <action>Check write permissions for destination</action>
-      <action if="permission denied">HALT with error message</action>
-    </step>
-
-    <step n="3" title="Execute Sharding">
-      <action>Inform user that sharding is beginning</action>
-      <action>Execute command: `npx @kayvan/markdown-tree-parser [source-document] [destination-folder]`</action>
-      <action>Capture command output and any errors</action>
-      <action if="command fails">HALT and display error to user</action>
-    </step>
-
-    <step n="4" title="Verify Output">
-      <action>Check that destination folder contains sharded files</action>
-      <action>Verify index.md was created in destination folder</action>
-      <action>Count the number of files created</action>
-      <action if="no files created">HALT with error message</action>
-    </step>
-
-    <step n="5" title="Report Completion">
-      <action>Display completion report to user including:</action>
-      <i>- Source document path and name</i>
-      <i>- Destination folder path</i>
-      <i>- Number of section files created</i>
-      <i>- Confirmation that index.md was created</i>
-      <i>- Any tool output or warnings</i>
-      <action>Inform user that sharding completed successfully</action>
-    </step>
-
-    <step n="6" title="Handle Original Document">
-      <critical>Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion</critical>
-      <action>Present user with options for the original document:</action>
-
-      <ask>What would you like to do with the original document `[source-document-name]`?
-
-Options:
-[d] Delete - Remove the original (recommended - shards can always be recombined)
-[m] Move to archive - Move original to a backup/archive location
-[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
-
-Your choice (d/m/k):</ask>
-
-      <check if="user selects 'd' (delete)">
-        <action>Delete the original source document file</action>
-        <action>Confirm deletion to user: "✓ Original document deleted: [source-document-path]"</action>
-        <note>The document can be reconstructed from shards by concatenating all section files in order</note>
-      </check>
-
-      <check if="user selects 'm' (move)">
-        <action>Determine default archive location: same directory as source, in an "archive" subfolder</action>
-        <action>Example: /path/to/architecture.md → /path/to/archive/architecture.md</action>
-        <ask>Archive location ([y] to use default: [default-archive-path], or provide custom path):</ask>
-        <action if="user accepts default">Use default archive path</action>
-        <action if="user provides custom path">Use custom archive path</action>
-        <action>Create archive directory if it doesn't exist</action>
-        <action>Move original document to archive location</action>
-        <action>Confirm move to user: "✓ Original document moved to: [archive-path]"</action>
-      </check>
-
-      <check if="user selects 'k' (keep)">
-        <action>Display warning to user:</action>
-        <output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
-
-This creates confusion because:
-- The discover_inputs protocol may load the wrong version
-- Updates to one won't reflect in the other
-- You'll have duplicate content taking up space
-
-Consider deleting or archiving the original document.</output>
-        <action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
-      </check>
-    </step>
-  </flow>
-
-  <halt-conditions critical="true">
-    <i>HALT if npx command fails or produces no output files</i>
-  </halt-conditions>
-</tool>

package/src/core/workflows/brainstorming/README.md

@@ -1,261 +0,0 @@
----
-last-redoc-date: 2025-09-28
----
-
-# Brainstorming Session Workflow
-
-## Overview
-
-The brainstorming workflow facilitates interactive brainstorming sessions using diverse creative techniques. This workflow acts as an AI facilitator guiding users through various ideation methods to generate and refine creative solutions in a structured, energetic, and highly interactive manner.
-
-## Key Features
-
-- **36 Creative Techniques**: Comprehensive library spanning collaborative, structured, creative, deep, theatrical, wild, and introspective approaches
-- **Interactive Facilitation**: AI acts as a skilled facilitator using "Yes, and..." methodology
-- **Flexible Approach Selection**: User-guided, AI-recommended, random, or progressive technique flows
-- **Context-Aware Sessions**: Supports domain-specific brainstorming through context document input
-- **Systematic Organization**: Converges ideas into immediate opportunities, future innovations, and moonshots
-- **Action Planning**: Prioritizes top ideas with concrete next steps and timelines
-- **Session Documentation**: Comprehensive structured reports capturing all insights and outcomes
-
-## Usage
-
-### Configuration
-
-The workflow leverages configuration from `{bmad_folder}/core/config.yaml`:
-
-- **output_folder**: Where session results are saved
-- **user_name**: Session participant identification
-
-And the following has a default or can be passed in as an override for custom brainstorming scenarios.
-
-- **brain_techniques**: CSV database of 36 creative techniques, default is `./brain-methods.csv`
-
-## Workflow Structure
-
-### Files Included
-
-```
-brainstorming/
-├── workflow.yaml           # Configuration and metadata
-├── instructions.md         # Step-by-step execution guide
-├── template.md            # Session report structure
-├── brain-methods.csv      # Database of 36 creative techniques
-└── README.md              # This file
-```
-
-## Creative Techniques Library
-
-The workflow includes 36 techniques organized into 7 categories:
-
-### Collaborative Techniques
-
-- **Yes And Building**: Build momentum through positive additions
-- **Brain Writing Round Robin**: Silent idea generation with sequential building
-- **Random Stimulation**: Use random catalysts for unexpected connections
-- **Role Playing**: Generate solutions from multiple stakeholder perspectives
-
-### Structured Approaches
-
-- **SCAMPER Method**: Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse)
-- **Six Thinking Hats**: Explore through six perspectives (facts/emotions/benefits/risks/creativity/process)
-- **Mind Mapping**: Visual branching from central concepts
-- **Resource Constraints**: Innovation through extreme limitations
-
-### Creative Methods
-
-- **What If Scenarios**: Explore radical possibilities by questioning constraints
-- **Analogical Thinking**: Find solutions through domain parallels
-- **Reversal Inversion**: Flip problems upside down for fresh angles
-- **First Principles Thinking**: Strip away assumptions to rebuild from fundamentals
-- **Forced Relationships**: Connect unrelated concepts for innovation
-- **Time Shifting**: Explore solutions across different time periods
-- **Metaphor Mapping**: Use extended metaphors as thinking tools
-
-### Deep Analysis
-
-- **Five Whys**: Drill down through causation layers to root causes
-- **Morphological Analysis**: Systematically explore parameter combinations
-- **Provocation Technique**: Extract useful ideas from absurd starting points
-- **Assumption Reversal**: Challenge and flip core assumptions
-- **Question Storming**: Generate questions before seeking answers
-
-### Theatrical Approaches
-
-- **Time Travel Talk Show**: Interview past/present/future selves
-- **Alien Anthropologist**: Examine through completely foreign eyes
-- **Dream Fusion Laboratory**: Start with impossible solutions, work backwards
-- **Emotion Orchestra**: Let different emotions lead separate sessions
-- **Parallel Universe Cafe**: Explore under alternative reality rules
-
-### Wild Methods
-
-- **Chaos Engineering**: Deliberately break things to discover robust solutions
-- **Guerrilla Gardening Ideas**: Plant unexpected solutions in unlikely places
-- **Pirate Code Brainstorm**: Take what works from anywhere and remix
-- **Zombie Apocalypse Planning**: Design for extreme survival scenarios
-- **Drunk History Retelling**: Explain with uninhibited simplicity
-
-### Introspective Delight
-
-- **Inner Child Conference**: Channel pure childhood curiosity
-- **Shadow Work Mining**: Explore what you're avoiding or resisting
-- **Values Archaeology**: Excavate deep personal values driving decisions
-- **Future Self Interview**: Seek wisdom from your wiser future self
-- **Body Wisdom Dialogue**: Let physical sensations guide ideation
-
-## Workflow Process
-
-### Phase 1: Session Setup (Step 1)
-
-- Context gathering (topic, goals, constraints)
-- Domain-specific guidance if context document provided
-- Session scope definition (broad exploration vs. focused ideation)
-
-### Phase 2: Approach Selection (Step 2)
-
-- **User-Selected**: Browse and choose specific techniques
-- **AI-Recommended**: Tailored technique suggestions based on context
-- **Random Selection**: Surprise technique for creative breakthrough
-- **Progressive Flow**: Multi-technique journey from broad to focused
-
-### Phase 3: Interactive Facilitation (Step 3)
-
-- Master facilitator approach using questions, not answers
-- "Yes, and..." building methodology
-- Energy monitoring and technique switching
-- Real-time idea capture and momentum building
-- Quantity over quality focus (aim: 100 ideas in 60 minutes)
-
-### Phase 4: Convergent Organization (Step 4)
-
-- Review and categorize all generated ideas
-- Identify patterns and themes across techniques
-- Sort into three priority buckets for action planning
-
-### Phase 5: Insight Extraction (Step 5)
-
-- Surface recurring themes across multiple techniques
-- Identify key realizations and surprising connections
-- Extract deeper patterns and meta-insights
-
-### Phase 6: Action Planning (Step 6)
-
-- Prioritize top 3 ideas for implementation
-- Define concrete next steps for each priority
-- Determine resource needs and realistic timelines
-
-### Phase 7: Session Reflection (Step 7)
-
-- Analyze what worked well and areas for further exploration
-- Recommend follow-up techniques and next session planning
-- Capture emergent questions for future investigation
-
-### Phase 8: Report Generation (Step 8)
-
-- Compile comprehensive structured report
-- Calculate total ideas generated and techniques used
-- Format all content for sharing and future reference
-
-## Output
-
-### Generated Files
-
-- **Primary output**: Structured session report saved to `{output_folder}/brainstorming-session-results-{date}.md`
-- **Context integration**: Links to previous brainstorming sessions if available
-
-### Output Structure
-
-1. **Executive Summary** - Topic, goals, techniques used, total ideas generated, key themes
-2. **Technique Sessions** - Detailed capture of each technique's ideation process
-3. **Idea Categorization** - Immediate opportunities, future innovations, moonshots, insights
-4. **Action Planning** - Top 3 priorities with rationale, steps, resources, timelines
-5. **Reflection and Follow-up** - Session analysis, recommendations, next steps planning
-
-## Requirements
-
-- No special software requirements
-- Access to the CIS module configuration (`{bmad_folder}/cis/config.yaml`)
-- Active participation and engagement throughout the interactive session
-- Optional: Domain context document for focused brainstorming
-
-## Best Practices
-
-### Before Starting
-
-1. **Define Clear Intent**: Know whether you want broad exploration or focused problem-solving
-2. **Gather Context**: Prepare any relevant background documents or domain knowledge
-3. **Set Time Expectations**: Plan for 45-90 minutes for a comprehensive session
-4. **Create Open Environment**: Ensure distraction-free space for creative thinking
-
-### During Execution
-
-1. **Embrace Quantity**: Generate many ideas without self-censoring
-2. **Build with "Yes, And"**: Accept and expand on ideas rather than judging
-3. **Stay Curious**: Follow unexpected connections and tangents
-4. **Trust the Process**: Let the facilitator guide you through technique transitions
-5. **Capture Everything**: Document all ideas, even seemingly silly ones
-6. **Monitor Energy**: Communicate when you need technique changes or breaks
-
-### After Completion
-
-1. **Review Within 24 Hours**: Re-read the report while insights are fresh
-2. **Act on Quick Wins**: Implement immediate opportunities within one week
-3. **Schedule Follow-ups**: Plan development sessions for promising concepts
-4. **Share Selectively**: Distribute relevant insights to appropriate stakeholders
-
-## Facilitation Principles
-
-The AI facilitator operates using these core principles:
-
-- **Ask, Don't Tell**: Use questions to draw out participant's own ideas
-- **Build, Don't Judge**: Use "Yes, and..." methodology, never "No, but..."
-- **Quantity Over Quality**: Aim for volume in generation phase
-- **Defer Judgment**: Evaluation comes after generation is complete
-- **Stay Curious**: Show genuine interest in participant's unique perspectives
-- **Monitor Energy**: Adapt technique and pace to participant's engagement level
-
-## Example Session Flow
-
-### Progressive Technique Flow
-
-1. **Mind Mapping** (10 min) - Build the landscape of possibilities
-2. **SCAMPER** (15 min) - Systematic exploration of improvement angles
-3. **Six Thinking Hats** (15 min) - Multiple perspectives on solutions
-4. **Forced Relationships** (10 min) - Creative synthesis of unexpected connections
-
-### Energy Checkpoints
-
-- After 15-20 minutes: "Should we continue with this technique or try something new?"
-- Before convergent phase: "Are you ready to start organizing ideas, or explore more?"
-- During action planning: "How's your energy for the final planning phase?"
-
-## Customization
-
-To customize this workflow:
-
-1. **Add New Techniques**: Extend `brain-methods.csv` with additional creative methods
-2. **Modify Facilitation Style**: Adjust prompts in `instructions.md` for different energy levels
-3. **Update Report Structure**: Modify `template.md` to include additional analysis sections
-4. **Create Domain Variants**: Develop specialized technique sets for specific industries
-
-## Version History
-
-- **v1.0.0** - Initial release
-  - 36 creative techniques across 7 categories
-  - Interactive facilitation with energy monitoring
-  - Comprehensive structured reporting
-  - Context-aware session guidance
-
-## Support
-
-For issues or questions:
-
-- Review technique descriptions in `brain-methods.csv` for facilitation guidance
-- Consult the workflow instructions in `instructions.md` for step-by-step details
-- Reference the template structure in `template.md` for output expectations
-- Follow BMAD documentation standards for workflow customization
-
----
-
-_Part of the BMad Method v6 - Creative Ideation and Synthesis (CIS) Module_