bmad-method 4.26.0 → 4.27.0

package/bmad-core/tasks/advanced-elicitation.md

@@ -5,88 +5,113 @@
 - Provide optional reflective and brainstorming actions to enhance content quality
 - Enable deeper exploration of ideas through structured elicitation techniques
 - Support iterative refinement through multiple analytical perspectives
+- Usable during template-driven document creation or any chat conversation
 
-## Task Instructions
+## Usage Scenarios
 
-### 1. Section Context and Review
+### Scenario 1: Template Document Creation
 
-[[LLM: When invoked after outputting a section:
+After outputting a section during document creation:
 
-1. First, provide a brief 1-2 sentence summary of what the user should look for in the section just presented (e.g., "Please review the technology choices for completeness and alignment with your project needs. Pay special attention to version numbers and any missing categories.")
+1. **Section Review**: Ask user to review the drafted section
+2. **Offer Elicitation**: Present 9 carefully selected elicitation methods
+3. **Simple Selection**: User types a number (0-8) to engage method, or 9 to proceed
+4. **Execute & Loop**: Apply selected method, then re-offer choices until user proceeds
 
-2. If the section contains Mermaid diagrams, explain each diagram briefly before offering elicitation options (e.g., "The component diagram shows the main system modules and their interactions. Notice how the API Gateway routes requests to different services.")
+### Scenario 2: General Chat Elicitation
 
-3. If the section contains multiple distinct items (like multiple components, multiple patterns, etc.), inform the user they can apply elicitation actions to:
+User can request advanced elicitation on any agent output:
 
-   - The entire section as a whole
-   - Individual items within the section (specify which item when selecting an action)
+- User says "do advanced elicitation" or similar
+- Agent selects 9 relevant methods for the context
+- Same simple 0-9 selection process
 
-4. Then present the action list as specified below.]]
+## Task Instructions
 
-### 2. Ask for Review and Present Action List
+### 1. Intelligent Method Selection
 
-[[LLM: Ask the user to review the drafted section. In the SAME message, inform them that they can suggest additions, removals, or modifications, OR they can select an action by number from the 'Advanced Reflective, Elicitation & Brainstorming Actions'. If there are multiple items in the section, mention they can specify which item(s) to apply the action to. Then, present ONLY the numbered list (0-9) of these actions. Conclude by stating that selecting 9 will proceed to the next section. Await user selection. If an elicitation action (0-8) is chosen, execute it and then re-offer this combined review/elicitation choice. If option 9 is chosen, or if the user provides direct feedback, proceed accordingly.]]
+**Context Analysis**: Before presenting options, analyze:
 
-**Present the numbered list (0-9) with this exact format:**
+- **Content Type**: Technical specs, user stories, architecture, requirements, etc.
+- **Complexity Level**: Simple, moderate, or complex content
+- **Stakeholder Needs**: Who will use this information
+- **Risk Level**: High-impact decisions vs routine items
+- **Creative Potential**: Opportunities for innovation or alternatives
 
-```text
-**Advanced Reflective, Elicitation & Brainstorming Actions**
-Choose an action (0-9 - 9 to bypass - HELP for explanation of these options):
-
-0. Expand or Contract for Audience
-1. Explain Reasoning (CoT Step-by-Step)
-2. Critique and Refine
-3. Analyze Logical Flow and Dependencies
-4. Assess Alignment with Overall Goals
-5. Identify Potential Risks and Unforeseen Issues
-6. Challenge from Critical Perspective (Self or Other Persona)
-7. Explore Diverse Alternatives (ToT-Inspired)
-8. Hindsight is 20/20: The 'If Only...' Reflection
-9. Proceed / No Further Actions
-```
+**Method Selection Strategy**:
 
-### 2. Processing Guidelines
+1. **Always Include Core Methods** (choose 3-4):
+   - Expand or Contract for Audience
+   - Critique and Refine
+   - Identify Potential Risks
+   - Assess Alignment with Goals
 
-**Do NOT show:**
+2. **Context-Specific Methods** (choose 4-5):
+   - **Technical Content**: Tree of Thoughts, ReWOO, Meta-Prompting
+   - **User-Facing Content**: Agile Team Perspective, Stakeholder Roundtable
+   - **Creative Content**: Innovation Tournament, Escape Room Challenge
+   - **Strategic Content**: Red Team vs Blue Team, Hindsight Reflection
 
-- The full protocol text with `[[LLM: ...]]` instructions
-- Detailed explanations of each option unless executing or the user asks, when giving the definition you can modify to tie its relevance
-- Any internal template markup
+3. **Always Include**: "Proceed / No Further Actions" as option 9
 
-**After user selection from the list:**
+### 2. Section Context and Review
 
-- Execute the chosen action according to the protocol instructions below
-- Ask if they want to select another action or proceed with option 9 once complete
-- Continue until user selects option 9 or indicates completion
+When invoked after outputting a section:
 
-## Action Definitions
+1. **Provide Context Summary**: Give a brief 1-2 sentence summary of what the user should look for in the section just presented
 
-0. Expand or Contract for Audience
-   [[LLM: Ask the user whether they want to 'expand' on the content (add more detail, elaborate) or 'contract' it (simplify, clarify, make more concise). Also, ask if there's a specific target audience they have in mind. Once clarified, perform the expansion or contraction from your current role's perspective, tailored to the specified audience if provided.]]
+2. **Explain Visual Elements**: If the section contains diagrams, explain them briefly before offering elicitation options
 
-1. Explain Reasoning (CoT Step-by-Step)
-   [[LLM: Explain the step-by-step thinking process, characteristic of your role, that you used to arrive at the current proposal for this content.]]
+3. **Clarify Scope Options**: If the section contains multiple distinct items, inform the user they can apply elicitation actions to:
+   - The entire section as a whole
+   - Individual items within the section (specify which item when selecting an action)
 
-2. Critique and Refine
-   [[LLM: From your current role's perspective, review your last output or the current section for flaws, inconsistencies, or areas for improvement, and then suggest a refined version reflecting your expertise.]]
+### 3. Present Elicitation Options
 
-3. Analyze Logical Flow and Dependencies
-   [[LLM: From your role's standpoint, examine the content's structure for logical progression, internal consistency, and any relevant dependencies. Confirm if elements are presented in an effective order.]]
+**Review Request Process:**
 
-4. Assess Alignment with Overall Goals
-   [[LLM: Evaluate how well the current content contributes to the stated overall goals of the document, interpreting this from your specific role's perspective and identifying any misalignments you perceive.]]
+- Ask the user to review the drafted section
+- In the SAME message, inform them they can suggest direct changes OR select an elicitation method
+- Present 9 intelligently selected methods (0-8) plus "Proceed" (9)
+- Keep descriptions short - just the method name
+- Await simple numeric selection
 
-5. Identify Potential Risks and Unforeseen Issues
-   [[LLM: Based on your role's expertise, brainstorm potential risks, overlooked edge cases, or unintended consequences related to the current content or proposal.]]
+**Action List Presentation Format:**
 
-6. Challenge from Critical Perspective (Self or Other Persona)
-   [[LLM: Adopt a critical perspective on the current content. If the user specifies another role or persona (e.g., 'as a customer', 'as [Another Persona Name]'), critique the content or play devil's advocate from that specified viewpoint. If no other role is specified, play devil's advocate from your own current persona's viewpoint, arguing against the proposal or current content and highlighting weaknesses or counterarguments specific to your concerns. This can also randomly include YAGNI when appropriate, such as when trimming the scope of an MVP, the perspective might challenge the need for something to cut MVP scope.]]
+```text
+**Advanced Elicitation Options**
+Choose a number (0-8) or 9 to proceed:
+
+0. [Method Name]
+1. [Method Name]
+2. [Method Name]
+3. [Method Name]
+4. [Method Name]
+5. [Method Name]
+6. [Method Name]
+7. [Method Name]
+8. [Method Name]
+9. Proceed / No Further Actions
+```
 
-7. Explore Diverse Alternatives (ToT-Inspired)
-   [[LLM: From your role's perspective, first broadly brainstorm a range of diverse approaches or solutions to the current topic. Then, from this wider exploration, select and present 2 distinct alternatives, detailing the pros, cons, and potential implications you foresee for each.]]
+**Response Handling:**
 
-8. Hindsight is 20/20: The 'If Only...' Reflection
-   [[LLM: In your current persona, imagine it's a retrospective for a project based on the current content. What's the one 'if only we had known/done X...' that your role would humorously or dramatically highlight, along with the imagined consequences?]]
+- **Numbers 0-8**: Execute the selected method, then re-offer the choice
+- **Number 9**: Proceed to next section or continue conversation
+- **Direct Feedback**: Apply user's suggested changes and continue
 
-9. Proceed / No Further Actions
-   [[LLM: Acknowledge the user's choice to finalize the current work, accept the AI's last output as is, or move on to the next step without selecting another action from this list. Prepare to proceed accordingly.]]
+### 4. Method Execution Framework
+
+**Execution Process:**
+
+1. **Retrieve Method**: Access the specific elicitation method from the elicitation-methods data file
+2. **Apply Context**: Execute the method from your current role's perspective
+3. **Provide Results**: Deliver insights, critiques, or alternatives relevant to the content
+4. **Re-offer Choice**: Present the same 9 options again until user selects 9 or gives direct feedback
+
+**Execution Guidelines:**
+
+- **Be Concise**: Focus on actionable insights, not lengthy explanations
+- **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
+- **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
+- **Maintain Flow**: Keep the process moving efficiently

package/bmad-core/tasks/facilitate-brainstorming-session.md

@@ -0,0 +1,136 @@
+---
+docOutputLocation: docs/brainstorming-session-results.md
+template: brainstorming-output-tmpl
+---
+
+# Facilitate Brainstorming Session Task
+
+Facilitate interactive brainstorming sessions with users. Be creative and adaptive in applying techniques.
+
+## Process
+
+### Step 1: Session Setup
+
+Ask 4 context questions (don't preview what happens next):
+
+1. What are we brainstorming about?
+2. Any constraints or parameters?
+3. Goal: broad exploration or focused ideation?
+4. Do you want a structured document output to reference later? (Y/N)
+
+### Step 2: Present Approach Options
+
+After getting answers to Step 1, present 4 approach options (numbered):
+
+1. User selects specific techniques
+2. Analyst recommends techniques based on context
+3. Random technique selection for creative variety
+4. Progressive technique flow (start broad, narrow down)
+
+### Step 3: Execute Techniques Interactively
+
+**KEY PRINCIPLES:**
+
+- **FACILITATOR ROLE**: Guide user to generate their own ideas through questions, prompts, and examples
+- **CONTINUOUS ENGAGEMENT**: Keep user engaged with chosen technique until they want to switch or are satisfied
+- **CAPTURE OUTPUT**: If document output requested, capture all ideas generated in each technique section
+
+**Technique Selection:**
+If user selects Option 1, present numbered list of techniques from the brainstorming-techniques data file. User can select by number (e.g., "7" for Mind Mapping).
+
+**Technique Execution:**
+
+1. Apply selected technique according to data file description
+2. Keep engaging with technique until user indicates they want to:
+   - Choose a different technique
+   - Apply current ideas to a new technique  
+   - Move to convergent phase
+   - End session
+
+**Output Capture (if requested):**
+For each technique used, capture:
+
+- Technique name and duration
+- Key ideas generated by user
+- Insights and patterns identified
+- User's reflections on the process
+
+### Step 4: Session Flow
+
+1. **Warm-up** (5-10 min) - Build creative confidence
+2. **Divergent** (20-30 min) - Generate quantity over quality
+3. **Convergent** (15-20 min) - Group and categorize ideas
+4. **Synthesis** (10-15 min) - Refine and develop concepts
+
+### Step 5: Document Output (if requested)
+
+Generate structured document with these sections:
+
+**Executive Summary**
+
+- Session topic and goals
+- Techniques used and duration
+- Total ideas generated
+- Key themes and patterns identified
+
+**Technique Sections** (for each technique used)
+
+- Technique name and description
+- Ideas generated (user's own words)
+- Insights discovered
+- Notable connections or patterns
+
+**Idea Categorization**
+
+- **Immediate Opportunities** - Ready to implement now
+- **Future Innovations** - Requires development/research
+- **Moonshots** - Ambitious, transformative concepts
+- **Insights & Learnings** - Key realizations from session
+
+**Action Planning**
+
+- Top 3 priority ideas with rationale
+- Next steps for each priority
+- Resources/research needed
+- Timeline considerations
+
+**Reflection & Follow-up**
+
+- What worked well in this session
+- Areas for further exploration
+- Recommended follow-up techniques
+- Questions that emerged for future sessions
+
+## Key Principles
+
+- **YOU ARE A FACILITATOR**: Guide the user to brainstorm, don't brainstorm for them
+- **INTERACTIVE DIALOGUE**: Ask questions, wait for responses, build on their ideas
+- **ONE TECHNIQUE AT A TIME**: Don't mix multiple techniques in one response
+- **CONTINUOUS ENGAGEMENT**: Stay with one technique until user wants to switch
+- **DRAW IDEAS OUT**: Use prompts and examples to help them generate their own ideas
+- **REAL-TIME ADAPTATION**: Monitor engagement and adjust approach as needed
+- Maintain energy and momentum
+- Defer judgment during generation
+- Quantity leads to quality (aim for 100 ideas in 60 minutes)
+- Build on ideas collaboratively
+- Document everything if output requested
+
+## Advanced Engagement Strategies
+
+**Energy Management**
+
+- Check engagement levels: "How are you feeling about this direction?"
+- Offer breaks or technique switches if energy flags
+- Use encouraging language and celebrate idea generation
+
+**Depth vs. Breadth**
+
+- Ask follow-up questions to deepen ideas: "Tell me more about that..."
+- Use "Yes, and..." to build on their ideas
+- Help them make connections: "How does this relate to your earlier idea about...?"
+
+**Transition Management**
+
+- Always ask before switching techniques: "Ready to try a different approach?"
+- Offer options: "Should we explore this idea deeper or generate more alternatives?"
+- Respect their process and timing

package/bmad-core/templates/architecture-tmpl.md

@@ -8,7 +8,7 @@
 
 [[LLM: This section establishes the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
 
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
+After presenting this section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 This document outlines the overall project architecture for {{Project Name}}, including backend systems, shared services, and non-UI specific concerns. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development, ensuring consistency and adherence to chosen patterns and technologies.
 
@@ -53,7 +53,7 @@ If the project includes a significant user interface, a separate Frontend Archit
 
 Document the decision here before proceeding with the architecture design. In none, just say N/A
 
-After presenting this starter template section, apply `tasks#advanced-elicitation` protocol]]
+After presenting this starter template section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ### Change Log
 
@@ -64,7 +64,7 @@ After presenting this starter template section, apply `tasks#advanced-elicitatio
 
 ## High Level Architecture
 
-[[LLM: This section contains multiple subsections that establish the foundation of the architecture. Present all subsections together (Introduction, Technical Summary, High Level Overview, Project Diagram, and Architectural Patterns), then apply `tasks#advanced-elicitation` protocol to the complete High Level Architecture section. The user can choose to refine the entire section or specific subsections.]]
+[[LLM: This section contains multiple subsections that establish the foundation of the architecture. Present all subsections together (Introduction, Technical Summary, High Level Overview, Project Diagram, and Architectural Patterns), then apply `{root}/tasks/advanced-elicitation.md` protocol to the complete High Level Architecture section. The user can choose to refine the entire section or specific subsections.]]
 
 ### Technical Summary
 
@@ -86,7 +86,7 @@ After presenting this starter template section, apply `tasks#advanced-elicitatio
 4. Primary user interaction flow or data flow at a conceptual level
 5. Key architectural decisions and their rationale
 
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
+After presenting this section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ### High Level Project Diagram
 
@@ -100,7 +100,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 Use appropriate Mermaid diagram type (graph TD, C4, sequence) based on what best represents the architecture
 
-After presenting the diagram, apply `tasks#advanced-elicitation` protocol]]
+After presenting the diagram, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ### Architectural and Design Patterns
 
@@ -132,13 +132,13 @@ Common patterns to consider:
 
 @{/example}
 
-[[LLM: After presenting the patterns, apply `tasks#advanced-elicitation` protocol]]
+[[LLM: After presenting the patterns, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Tech Stack
 
 [[LLM: This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
 
-1. Review PRD technical assumptions and any preferences from `data#technical-preferences` or an attached `technical-preferences`
+1. Review PRD technical assumptions and any preferences from `{root}/data/technical-preferences.yaml` or an attached `technical-preferences`
 2. For each category, present 2-3 viable options with pros/cons
 3. Make a clear recommendation based on project needs
 4. Get explicit user approval for each selection
@@ -154,7 +154,7 @@ Key decisions to finalize - before displaying the table, ensure you are aware of
 - Database and storage solutions - if unclear suggest sql or nosql or other types depending on the project and depending on cloud provider offer a suggestion
 - Development tools
 
-Upon render of the table, ensure the user is aware of the importance of this sections choices, should also look for gaps or disagreements with anything, ask for any clarifications if something is unclear why its in the list, and also right away apply `tasks#advanced-elicitation` display - this statement and the options should be rendered and then prompt right all before allowing user input.]]
+Upon render of the table, ensure the user is aware of the importance of this sections choices, should also look for gaps or disagreements with anything, ask for any clarifications if something is unclear why its in the list, and also right away apply `{root}/tasks/advanced-elicitation.md` display - this statement and the options should be rendered and then prompt right all before allowing user input.]]
 
 ### Cloud Infrastructure
 
@@ -198,7 +198,7 @@ Upon render of the table, ensure the user is aware of the importance of this sec
 
 Create a clear conceptual model before moving to database schema.
 
-After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
+After presenting all data models, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 <<REPEAT: data_model>>
 
@@ -232,7 +232,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
 - Technology specifics based on tech stack choices
 
 5. Create component diagrams where helpful
-6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
+6. After presenting all components, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 <<REPEAT: component>>
 
@@ -259,7 +259,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
 - Sequence diagrams for complex interactions
   Choose the most appropriate for clarity
 
-After presenting the diagrams, apply `tasks#advanced-elicitation` protocol]]
+After presenting the diagrams, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## External APIs
 
@@ -313,7 +313,7 @@ If no external APIs are needed, state this explicitly and skip to next section.]
 
 ^^/CONDITION: has_external_apis^^
 
-[[LLM: After presenting external APIs (or noting their absence), apply `tasks#advanced-elicitation` protocol]]
+[[LLM: After presenting external APIs (or noting their absence), apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Core Workflows
 
@@ -327,7 +327,7 @@ If no external APIs are needed, state this explicitly and skip to next section.]
 
 Focus on workflows that clarify architecture decisions or complex interactions.
 
-After presenting the workflow diagrams, apply `tasks#advanced-elicitation` protocol]]
+After presenting the workflow diagrams, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## REST API Spec
 
@@ -361,7 +361,7 @@ servers:
 
 ^^/CONDITION: has_rest_api^^
 
-[[LLM: After presenting the REST API spec (or noting its absence if not applicable), apply `tasks#advanced-elicitation` protocol]]
+[[LLM: After presenting the REST API spec (or noting its absence if not applicable), apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Database Schema
 
@@ -375,7 +375,7 @@ servers:
 
 Present schema in format appropriate to database type (SQL DDL, JSON schema, etc.)
 
-After presenting the database schema, apply `tasks#advanced-elicitation` protocol]]
+After presenting the database schema, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Source Tree
 
@@ -390,7 +390,7 @@ After presenting the database schema, apply `tasks#advanced-elicitation` protoco
 
 Adapt the structure based on project needs. For monorepos, show service separation. For serverless, show function organization. Include language-specific conventions.
 
-After presenting the structure, apply `tasks#advanced-elicitation` protocol to refine based on user feedback.]]
+After presenting the structure, apply `{root}/tasks/advanced-elicitation.md` protocol to refine based on user feedback.]]
 
 ```plaintext
 {{project-root}}/
@@ -433,7 +433,7 @@ project-root/
 @{/example}
 ```
 
-[[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]
+[[LLM: After presenting the source tree structure, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Infrastructure and Deployment
 
@@ -478,7 +478,7 @@ Get user input on deployment preferences and CI/CD tool choices.]]
 - **Trigger Conditions:** {{rollback_triggers}}
 - **Recovery Time Objective:** {{rto}}
 
-[[LLM: After presenting the infrastructure and deployment section, apply `tasks#advanced-elicitation` protocol]]
+[[LLM: After presenting the infrastructure and deployment section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Error Handling Strategy
 
@@ -529,7 +529,7 @@ This section guides both AI and human developers in consistent error handling.]]
 - **Compensation Logic:** {{compensation_patterns}}
 - **Idempotency:** {{idempotency_approach}}
 
-[[LLM: After presenting the error handling strategy, apply `tasks#advanced-elicitation` protocol]]
+[[LLM: After presenting the error handling strategy, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Coding Standards
 
@@ -590,7 +590,7 @@ Avoid obvious rules like "use SOLID principles" or "write clean code"]]
 
 ^^/CONDITION: has_language_specifics^^
 
-[[LLM: After presenting the coding standards, apply `tasks#advanced-elicitation` protocol]]
+[[LLM: After presenting the coding standards, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Test Strategy and Standards
 
@@ -603,7 +603,7 @@ Avoid obvious rules like "use SOLID principles" or "write clean code"]]
 5. Determine integration test infrastructure
 6. Plan for test data and external dependencies
 
-Note: Basic info goes in Coding Standards for dev agent. This detailed section is for QA agent and team reference. Apply `tasks#advanced-elicitation` after initial draft.]]
+Note: Basic info goes in Coding Standards for dev agent. This detailed section is for QA agent and team reference. Apply `{root}/tasks/advanced-elicitation.md` after initial draft.]]
 
 ### Testing Philosophy
 
@@ -664,7 +664,7 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
 - **Performance Tests:** {{perf_test_approach}}
 - **Security Tests:** {{security_test_approach}}
 
-[[LLM: After presenting the test strategy section, apply `tasks#advanced-elicitation` protocol]]
+[[LLM: After presenting the test strategy section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Security
 
@@ -728,7 +728,7 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
 - **DAST Tool:** {{dynamic_analysis}}
 - **Penetration Testing:** {{pentest_schedule}}
 
-[[LLM: After presenting the security section, apply `tasks#advanced-elicitation` protocol]]
+[[LLM: After presenting the security section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
 
 ## Checklist Results Report
 

package/bmad-core/templates/brainstorming-output-tmpl.md

@@ -0,0 +1,149 @@
+---
+defaultOutput: docs/brainstorming-session-results.md
+---
+
+# Brainstorming Session Results
+
+**Session Date:** [DATE]
+**Facilitator:** [Agent Role] [Agent Name]
+**Participant:** [USER NAME]
+
+## Executive Summary
+
+**Topic:** [SESSION TOPIC]
+
+**Session Goals:** [STATED GOALS]
+
+**Techniques Used:** [LIST OF TECHNIQUES AND DURATION]
+
+**Total Ideas Generated:** [NUMBER]
+
+**Key Themes Identified:**
+
+- [THEME 1]
+- [THEME 2]
+- [THEME 3]
+
+---
+
+## Technique Sessions
+
+### [TECHNIQUE NAME 1] - [DURATION]
+
+**Description:** [BRIEF DESCRIPTION OF TECHNIQUE]
+
+**Ideas Generated:**
+
+1. [USER IDEA 1]
+2. [USER IDEA 2]
+3. [USER IDEA 3]
+[etc.]
+
+**Insights Discovered:**
+
+- [INSIGHT 1]
+- [INSIGHT 2]
+
+**Notable Connections:**
+
+- [CONNECTION OR PATTERN IDENTIFIED]
+
+---
+
+### [TECHNIQUE NAME 2] - [DURATION]
+
+[Repeat format for each technique used]
+
+---
+
+## Idea Categorization
+
+### Immediate Opportunities
+
+*Ideas ready to implement now*
+
+1. **[IDEA NAME]**
+   - Description: [BRIEF DESCRIPTION]
+   - Why immediate: [RATIONALE]
+   - Resources needed: [BASIC REQUIREMENTS]
+
+### Future Innovations
+
+*Ideas requiring development/research*
+
+1. **[IDEA NAME]**
+   - Description: [BRIEF DESCRIPTION]
+   - Development needed: [WHAT'S REQUIRED]
+   - Timeline estimate: [ROUGH TIMEFRAME]
+
+### Moonshots
+
+*Ambitious, transformative concepts*
+
+1. **[IDEA NAME]**
+   - Description: [BRIEF DESCRIPTION]
+   - Transformative potential: [WHY IT'S A MOONSHOT]
+   - Challenges to overcome: [MAJOR OBSTACLES]
+
+### Insights & Learnings
+
+*Key realizations from the session*
+
+- [INSIGHT 1]: [DESCRIPTION AND IMPLICATIONS]
+- [INSIGHT 2]: [DESCRIPTION AND IMPLICATIONS]
+
+---
+
+## Action Planning
+
+### Top 3 Priority Ideas
+
+**#1 Priority: [IDEA NAME]**
+
+- Rationale: [WHY THIS IS TOP PRIORITY]
+- Next steps: [SPECIFIC ACTIONS TO TAKE]
+- Resources needed: [WHAT'S REQUIRED]
+- Timeline: [WHEN TO START/COMPLETE]
+
+**#2 Priority: [IDEA NAME]**
+
+- [Same format]
+
+**#3 Priority: [IDEA NAME]**
+
+- [Same format]
+
+---
+
+## Reflection & Follow-up
+
+### What Worked Well
+
+- [SUCCESSFUL ASPECT 1]
+- [SUCCESSFUL ASPECT 2]
+
+### Areas for Further Exploration
+
+- [AREA 1]: [WHY IT NEEDS MORE EXPLORATION]
+- [AREA 2]: [WHY IT NEEDS MORE EXPLORATION]
+
+### Recommended Follow-up Techniques
+
+- [TECHNIQUE 1]: [WHY IT WOULD BE HELPFUL]
+- [TECHNIQUE 2]: [WHY IT WOULD BE HELPFUL]
+
+### Questions That Emerged
+
+- [QUESTION 1]
+- [QUESTION 2]
+- [QUESTION 3]
+
+### Next Session Planning
+
+- **Suggested topics:** [FOLLOW-UP TOPICS]
+- **Recommended timeframe:** [WHEN TO RECONVENE]
+- **Preparation needed:** [WHAT TO RESEARCH/PREPARE]
+
+---
+
+*Session facilitated using the BMAD-METHOD brainstorming framework*