agentvibes 2.13.6 → 2.13.8

package/.bmad/core/tasks/workflow.xml

@@ -1,270 +0,0 @@
-<task id="{bmad_folder}/core/tasks/workflow.xml" name="Execute Workflow">
-  <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
-
-  <llm critical="true">
-    <mandate>Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files</mandate>
-    <mandate>Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown</mandate>
-    <mandate>Execute ALL steps in instructions IN EXACT ORDER</mandate>
-    <mandate>Save to template output file after EVERY "template-output" tag</mandate>
-    <mandate>NEVER delegate a step - YOU are responsible for every steps execution</mandate>
-  </llm>
-
-  <WORKFLOW-RULES critical="true">
-    <rule n="1">Steps execute in exact numerical order (1, 2, 3...)</rule>
-    <rule n="2">Optional steps: Ask user unless #yolo mode active</rule>
-    <rule n="3">Template-output tags: Save content → Show user → Get approval before continuing</rule>
-    <rule n="4">User must approve each major section before continuing UNLESS #yolo mode active</rule>
-  </WORKFLOW-RULES>
-
-  <flow>
-    <step n="1" title="Load and Initialize Workflow">
-      <substep n="1a" title="Load Configuration and Resolve Variables">
-        <action>Read workflow.yaml from provided path</action>
-        <mandate>Load config_source (REQUIRED for all modules)</mandate>
-        <phase n="1">Load external config from config_source path</phase>
-        <phase n="2">Resolve all {config_source}: references with values from config</phase>
-        <phase n="3">Resolve system variables (date:system-generated) and paths ({project-root}, {installed_path})</phase>
-        <phase n="4">Ask user for input of any variables that are still unknown</phase>
-      </substep>
-
-      <substep n="1b" title="Load Required Components">
-        <mandate>Instructions: Read COMPLETE file from path OR embedded list (REQUIRED)</mandate>
-        <check>If template path → Read COMPLETE template file</check>
-        <check>If validation path → Note path for later loading when needed</check>
-        <check>If template: false → Mark as action-workflow (else template-workflow)</check>
-        <note>Data files (csv, json) → Store paths only, load on-demand when instructions reference them</note>
-      </substep>
-
-      <substep n="1c" title="Initialize Output" if="template-workflow">
-        <action>Resolve default_output_file path with all variables and {{date}}</action>
-        <action>Create output directory if doesn't exist</action>
-        <action>If template-workflow → Write template to output file with placeholders</action>
-        <action>If action-workflow → Skip file creation</action>
-      </substep>
-    </step>
-
-    <step n="2" title="Process Each Instruction Step">
-      <iterate>For each step in instructions:</iterate>
-
-      <substep n="2a" title="Handle Step Attributes">
-        <check>If optional="true" and NOT #yolo → Ask user to include</check>
-        <check>If if="condition" → Evaluate condition</check>
-        <check>If for-each="item" → Repeat step for each item</check>
-        <check>If repeat="n" → Repeat step n times</check>
-      </substep>
-
-      <substep n="2b" title="Execute Step Content">
-        <action>Process step instructions (markdown or XML tags)</action>
-        <action>Replace {{variables}} with values (ask user if unknown)</action>
-        <execute-tags>
-          <tag>action xml tag → Perform the action</tag>
-          <tag>check if="condition" xml tag → Conditional block wrapping actions (requires closing &lt;/check&gt;)</tag>
-          <tag>ask xml tag → Prompt user and WAIT for response</tag>
-          <tag>invoke-workflow xml tag → Execute another workflow with given inputs</tag>
-          <tag>invoke-task xml tag → Execute specified task</tag>
-          <tag>invoke-protocol name="protocol_name" xml tag → Execute reusable protocol from protocols section</tag>
-          <tag>goto step="x" → Jump to specified step</tag>
-        </execute-tags>
-      </substep>
-
-      <substep n="2c" title="Handle template-output Tags">
-        <if tag="template-output">
-          <mandate>Generate content for this section</mandate>
-          <mandate>Save to file (Write first time, Edit subsequent)</mandate>
-          <action>Show checkpoint separator: ━━━━━━━━━━━━━━━━━━━━━━━</action>
-          <action>Display generated content</action>
-          <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
-              response="a">
-              <action>Start the advanced elicitation workflow {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</action>
-            </if>
-            <if
-              response="c">
-              <action>Continue to next step</action>
-            </if>
-            <if response="p">
-              <action>Start the party-mode workflow {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml</action>
-            </if>
-            <if
-              response="y">
-              <action>Enter #yolo mode for the rest of the workflow</action>
-            </if>
-          </ask>
-        </if>
-      </substep>
-
-      <substep n="2d" title="Step Completion">
-        <check>If no special tags and NOT #yolo:</check>
-        <ask>Continue to next step? (y/n/edit)</ask>
-      </substep>
-    </step>
-
-    <step n="3" title="Completion">
-      <check>If checklist exists → Run validation</check>
-      <check>If template: false → Confirm actions completed</check>
-      <check>Else → Confirm document saved to output path</check>
-      <action>Report workflow completion</action>
-    </step>
-  </flow>
-
-  <execution-modes>
-    <mode name="normal">Full user interaction at all decision points</mode>
-    <mode name="#yolo">Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by
-      simulating the remaining discussions with an simulated expert user</mode>
-  </execution-modes>
-
-  <supported-tags desc="Instructions can use these tags">
-    <structural>
-      <tag>step n="X" goal="..." - Define step with number and goal</tag>
-      <tag>optional="true" - Step can be skipped</tag>
-      <tag>if="condition" - Conditional execution</tag>
-      <tag>for-each="collection" - Iterate over items</tag>
-      <tag>repeat="n" - Repeat n times</tag>
-    </structural>
-    <execution>
-      <tag>action - Required action to perform</tag>
-      <tag>action if="condition" - Single conditional action (inline, no closing tag needed)</tag>
-      <tag>check if="condition"&gt;...&lt;/check&gt; - Conditional block wrapping multiple items (closing tag required)</tag>
-      <tag>ask - Get user input (wait for response)</tag>
-      <tag>goto - Jump to another step</tag>
-      <tag>invoke-workflow - Call another workflow</tag>
-      <tag>invoke-task - Call a task</tag>
-      <tag>invoke-protocol - Execute a reusable protocol (e.g., discover_inputs)</tag>
-    </execution>
-    <output>
-      <tag>template-output - Save content checkpoint</tag>
-      <tag>critical - Cannot be skipped</tag>
-      <tag>example - Show example output</tag>
-    </output>
-  </supported-tags>
-
-  <conditional-execution-patterns desc="When to use each pattern">
-    <pattern type="single-action">
-      <use-case>One action with a condition</use-case>
-      <syntax>&lt;action if="condition"&gt;Do something&lt;/action&gt;</syntax>
-      <example>&lt;action if="file exists"&gt;Load the file&lt;/action&gt;</example>
-      <rationale>Cleaner and more concise for single items</rationale>
-    </pattern>
-
-    <pattern type="multi-action-block">
-      <use-case>Multiple actions/tags under same condition</use-case>
-      <syntax>&lt;check if="condition"&gt;
-        &lt;action&gt;First action&lt;/action&gt;
-        &lt;action&gt;Second action&lt;/action&gt;
-        &lt;/check&gt;</syntax>
-      <example>&lt;check if="validation fails"&gt;
-        &lt;action&gt;Log error&lt;/action&gt;
-        &lt;goto step="1"&gt;Retry&lt;/goto&gt;
-        &lt;/check&gt;</example>
-      <rationale>Explicit scope boundaries prevent ambiguity</rationale>
-    </pattern>
-
-    <pattern type="nested-conditions">
-      <use-case>Else/alternative branches</use-case>
-      <syntax>&lt;check if="condition A"&gt;...&lt;/check&gt;
-        &lt;check if="else"&gt;...&lt;/check&gt;</syntax>
-      <rationale>Clear branching logic with explicit blocks</rationale>
-    </pattern>
-  </conditional-execution-patterns>
-
-  <protocols desc="Reusable workflow protocols that can be invoked via invoke-protocol tag">
-    <protocol name="discover_inputs" desc="Smart file discovery and loading based on input_file_patterns">
-      <objective>Intelligently load project files (whole or sharded) based on workflow's input_file_patterns configuration</objective>
-
-      <critical>Only execute if workflow.yaml contains input_file_patterns section</critical>
-
-      <flow>
-        <step n="1" title="Parse Input File Patterns">
-          <action>Read input_file_patterns from loaded workflow.yaml</action>
-          <action>For each pattern group (prd, architecture, epics, etc.), note the load_strategy if present</action>
-        </step>
-
-        <step n="2" title="Load Files Using Smart Strategies">
-          <iterate>For each pattern in input_file_patterns:</iterate>
-
-          <substep n="2a" title="Try Whole Document First">
-            <action>Attempt glob match on 'whole' pattern (e.g., "{output_folder}/*prd*.md")</action>
-            <check if="matches found">
-              <action>Load ALL matching files completely (no offset/limit)</action>
-              <action>Store content in variable: {pattern_name_content} (e.g., {prd_content})</action>
-              <action>Mark pattern as RESOLVED, skip to next pattern</action>
-            </check>
-          </substep>
-
-          <substep n="2b" title="Try Sharded Document if Whole Not Found">
-            <check if="no whole matches AND sharded pattern exists">
-              <action>Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified)</action>
-
-              <strategy name="FULL_LOAD">
-                <desc>Load ALL files in sharded directory - used for PRD, Architecture, UX, brownfield docs</desc>
-                <action>Use glob pattern to find ALL .md files (e.g., "{output_folder}/*architecture*/*.md")</action>
-                <action>Load EVERY matching file completely</action>
-                <action>Concatenate content in logical order (index.md first if exists, then alphabetical)</action>
-                <action>Store in variable: {pattern_name_content}</action>
-              </strategy>
-
-              <strategy name="SELECTIVE_LOAD">
-                <desc>Load specific shard using template variable - example: used for epics with {{epic_num}}</desc>
-                <action>Check for template variables in sharded_single pattern (e.g., {{epic_num}})</action>
-                <action>If variable undefined, ask user for value OR infer from context</action>
-                <action>Resolve template to specific file path</action>
-                <action>Load that specific file</action>
-                <action>Store in variable: {pattern_name_content}</action>
-              </strategy>
-
-              <strategy name="INDEX_GUIDED">
-                <desc>Load index.md, analyze structure and description of each doc in the index, then intelligently load relevant docs</desc>
-                <mandate>DO NOT BE LAZY - use best judgment to load documents that might have relevant information, even if only a 5% chance</mandate>
-                <action>Load index.md from sharded directory</action>
-                <action>Parse table of contents, links, section headers</action>
-                <action>Analyze workflow's purpose and objective</action>
-                <action>Identify which linked/referenced documents are likely relevant</action>
-                <example>If workflow is about authentication and index shows "Auth Overview", "Payment Setup", "Deployment" → Load auth
-                  docs, consider deployment docs, skip payment</example>
-                <action>Load all identified relevant documents</action>
-                <action>Store combined content in variable: {pattern_name_content}</action>
-                <note>When in doubt, LOAD IT - context is valuable, being thorough is better than missing critical info</note>
-              </strategy>
-            </check>
-          </substep>
-
-          <substep n="2c" title="Handle Not Found">
-            <check if="no matches for whole OR sharded">
-              <action>Set {pattern_name_content} to empty string</action>
-              <action>Note in session: "No {pattern_name} files found" (not an error, just unavailable, offer use change to provide)</action>
-            </check>
-          </substep>
-        </step>
-
-        <step n="3" title="Report Discovery Results">
-          <action>List all loaded content variables with file counts</action>
-          <example>
-            ✓ Loaded {prd_content} from 1 file: PRD.md
-            ✓ Loaded {architecture_content} from 5 sharded files: architecture/index.md, architecture/system-design.md, ...
-            ✓ Loaded {epics_content} from selective load: epics/epic-3.md
-            ○ No ux_design files found
-          </example>
-          <note>This gives workflow transparency into what context is available</note>
-        </step>
-      </flow>
-
-      <usage-in-instructions>
-        <example desc="Typical usage in workflow instructions.md">
-          &lt;step n="0" goal="Discover and load project context"&gt;
-          &lt;invoke-protocol name="discover_inputs" /&gt;
-          &lt;/step&gt;
-
-          &lt;step n="1" goal="Analyze requirements"&gt;
-          &lt;action&gt;Review {prd_content} for functional requirements&lt;/action&gt;
-          &lt;action&gt;Cross-reference with {architecture_content} for technical constraints&lt;/action&gt;
-          &lt;/step&gt;
-        </example>
-      </usage-in-instructions>
-    </protocol>
-  </protocols>
-
-  <llm final="true">
-    <mandate>This is the complete workflow execution engine</mandate>
-    <mandate>You MUST Follow instructions exactly as written and maintain conversation context between steps</mandate>
-    <mandate>If confused, re-read this task, the workflow yaml, and any yaml indicated files</mandate>
-  </llm>
-</task>

package/.bmad/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 explode [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/.bmad/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/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/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_