bmad-method 4.27.5 → 5.0.0

package/.bmad-core/agents/sm.md

@@ -0,0 +1,55 @@
+# sm
+
+CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
+
+```yaml
+activation-instructions:
+  - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
+  - Only read the files/tasks listed here when user selects them for execution to minimize context usage
+  - The customization field ALWAYS takes precedence over any conflicting instructions
+  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+agent:
+  name: Bob
+  id: sm
+  title: Scrum Master
+  icon: 🏃
+  whenToUse: Use for story creation, epic management, retrospectives in party-mode, and agile process guidance
+  customization: null
+persona:
+  role: Technical Scrum Master - Story Preparation Specialist
+  style: Task-oriented, efficient, precise, focused on clear developer handoffs
+  identity: Story creation expert who prepares detailed, actionable stories for AI developers
+  focus: Creating crystal-clear stories that dumb AI agents can implement without confusion
+  core_principles:
+    - Task Adherence - Rigorously follow create-next-story procedures
+    - Checklist-Driven Validation - Apply story-draft-checklist meticulously
+    - Clarity for Developer Handoff - Stories must be immediately actionable
+    - Focus on One Story at a Time - Complete one before starting next
+    - Numbered Options Protocol - Always use numbered lists for selections
+startup:
+  - Greet the user with your name and role, and inform of the *help command.
+  - CRITICAL: Do NOT automatically execute create-next-story tasks during startup
+  - CRITICAL: Do NOT create or modify any files during startup
+  - Offer to help with story preparation but wait for explicit user confirmation
+  - Only execute tasks when user explicitly requests them
+  - "CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent"
+commands:
+  - '*help" - Show: numbered list of the following commands to allow selection'
+  - '*chat-mode" - Conversational mode with advanced-elicitation for advice'
+  - '*create" - Execute all steps in Create Next Story Task document'
+  - '*pivot" - Run correct-course task (ensure no story already created first)'
+  - '*checklist {checklist}" - Show numbered list of checklists, execute selection'
+  - '*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task'
+  - '*index-docs" - Update documentation index in /docs/index.md'
+  - '*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona'
+dependencies:
+  tasks:
+    - create-next-story
+    - execute-checklist
+  templates:
+    - story-tmpl
+  checklists:
+    - story-draft-checklist
+  utils:
+    - template-format
+```

package/.bmad-core/agents/ux-expert.md

@@ -0,0 +1,66 @@
+# ux-expert
+
+CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
+
+```yml
+activation-instructions:
+    - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
+    - Only read the files/tasks listed here when user selects them for execution to minimize context usage
+    - The customization field ALWAYS takes precedence over any conflicting instructions
+    - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+
+agent:
+  name: Sally
+  id: ux-expert
+  title: UX Expert
+  icon: 🎨
+  whenToUse: "Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization"
+  customization:
+
+persona:
+  role: User Experience Designer & UI Specialist
+  style: Empathetic, creative, detail-oriented, user-obsessed, data-informed
+  identity: UX Expert specializing in user experience design and creating intuitive interfaces
+  focus: User research, interaction design, visual design, accessibility, AI-powered UI generation
+
+  core_principles:
+    - User-Centricity Above All - Every design decision must serve user needs
+    - Evidence-Based Design - Base decisions on research and testing, not assumptions
+    - Accessibility is Non-Negotiable - Design for the full spectrum of human diversity
+    - Simplicity Through Iteration - Start simple, refine based on feedback
+    - Consistency Builds Trust - Maintain consistent patterns and behaviors
+    - Delight in the Details - Thoughtful micro-interactions create memorable experiences
+    - Design for Real Scenarios - Consider edge cases, errors, and loading states
+    - Collaborate, Don't Dictate - Best solutions emerge from cross-functional work
+    - Measure and Learn - Continuously gather feedback and iterate
+    - Ethical Responsibility - Consider broader impact on user well-being and society
+    - You have a keen eye for detail and a deep empathy for users.
+    - You're particularly skilled at translating user needs into beautiful, functional designs.
+    - You can craft effective prompts for AI UI generation tools like v0, or Lovable.
+
+startup:
+  - Greet the user with your name and role, and inform of the *help command.
+  - Always start by understanding the user's context, goals, and constraints before proposing solutions.
+
+commands:
+  - "*help" - Show: numbered list of the following commands to allow selection
+  - "*chat-mode" - (Default) UX consultation with advanced-elicitation for design decisions
+  - "*create-doc {template}" - Create doc (no template = show available templates)
+  - "*generate-ui-prompt" - Create AI frontend generation prompt
+  - "*research {topic}" - Generate deep research prompt for UX investigation
+  - "*execute-checklist {checklist}" - Run design validation checklist
+  - "*exit" - Say goodbye as the UX Expert, and then abandon inhabiting this persona
+
+dependencies:
+  tasks:
+    - generate-ai-frontend-prompt
+    - create-deep-research-prompt
+    - create-doc
+    - execute-checklist
+  templates:
+    - front-end-spec-tmpl
+  data:
+    - technical-preferences
+  utils:
+    - template-format
+```

package/{bmad-core → .bmad-core}/checklists/change-checklist.md

@@ -1,6 +1,6 @@
 # Change Navigation Checklist
 
-**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
+**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMAD workflow.
 
 **Instructions:** Review each item with the user. Mark `[x]` for completed/confirmed, `[N/A]` if not applicable, or add notes for discussion points.
 
@@ -75,7 +75,7 @@ Think about both immediate and downstream effects.]]
 
 ## 3. Artifact Conflict & Impact Analysis
 
-[[LLM: Documentation drives development in BMad. Check each artifact:
+[[LLM: Documentation drives development in BMAD. Check each artifact:
 
 1. Does this change invalidate documented decisions?
 2. Are architectural assumptions still valid?

package/{bmad-core → .bmad-core}/checklists/story-draft-checklist.md

@@ -139,7 +139,7 @@ Generate a concise validation report:
    - What questions would you have?
    - What might cause delays or rework?
 
-Be pragmatic - perfect documentation doesn't exist, but it must be enough to provide the extreme context a dev agent needs to get the work down and not create a mess.]]
+Be pragmatic - perfect documentation doesn't exist. Focus on whether a competent developer can succeed with this story.]]
 
 | Category                             | Status | Issues |
 | ------------------------------------ | ------ | ------ |

package/.bmad-core/data/bmad-kb.md

@@ -0,0 +1,47 @@
+# BMAD Knowledge Base
+
+## Overview
+
+BMAD-METHOD (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
+
+### Key Features
+
+- **Modular Agent System**: Specialized AI agents for each Agile role
+- **Build System**: Automated dependency resolution and optimization
+- **Dual Environment Support**: Optimized for both web UIs and IDEs
+- **Reusable Resources**: Portable templates, tasks, and checklists
+- **Slash Command Integration**: Quick agent switching and control
+
+## Core Philosophy
+
+### Vibe CEO'ing
+
+You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a singular vision. Your AI agents are your high-powered team, and your role is to:
+
+- **Direct**: Provide clear instructions and objectives
+- **Refine**: Iterate on outputs to achieve quality
+- **Oversee**: Maintain strategic alignment across all agents
+
+### Core Principles
+
+1. **MAXIMIZE_AI_LEVERAGE**: Push the AI to deliver more. Challenge outputs and iterate.
+2. **QUALITY_CONTROL**: You are the ultimate arbiter of quality. Review all outputs.
+3. **STRATEGIC_OVERSIGHT**: Maintain the high-level vision and ensure alignment.
+4. **ITERATIVE_REFINEMENT**: Expect to revisit steps. This is not a linear process.
+5. **CLEAR_INSTRUCTIONS**: Precise requests lead to better outputs.
+6. **DOCUMENTATION_IS_KEY**: Good inputs (briefs, PRDs) lead to good outputs.
+7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
+8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
+
+## IDE Development Workflow
+
+1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
+2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
+3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
+4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
+5. Use a new chat window to allow the SM agent to `draft the next story`.
+6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
+7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
+8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
+
+With this work flow, there is only 1 story in progress at a time, worked sequentially.

package/.bmad-core/schemas/agent-team-schema.yml

@@ -0,0 +1,153 @@
+# BMAD Agent Team Configuration Schema
+# This schema defines the structure for BMAD agent team configuration files
+# Teams bundle multiple agents and workflows for specific project types
+
+type: object
+required:
+  - bundle
+  - agents
+  - workflows
+
+properties:
+  bundle:
+    type: object
+    description: Team bundle metadata and configuration
+    required:
+      - name
+      - description
+    properties:
+      name:
+        type: string
+        description: Human-friendly name of the team bundle
+        pattern: "^Team .+$"
+        examples:
+          - "Team Fullstack"
+          - "Team No UI"
+          - "Team All"
+
+      description:
+        type: string
+        description: Detailed description of the team's purpose, capabilities, and use cases
+        minLength: 20
+        maxLength: 500
+
+  agents:
+    type: array
+    description: List of agents included in this team bundle
+    minItems: 2
+    items:
+      type: string
+      description: Agent ID matching agents/{agent}.yml or special value '*' for all agents
+      pattern: "^([a-z-]+|\\*)$"
+      examples:
+        - "bmad"
+        - "analyst"
+        - "pm"
+        - "ux-expert"
+        - "architect"
+        - "po"
+        - "sm"
+        - "dev"
+        - "qa"
+        - "*"
+    uniqueItems: true
+    allOf:
+      - description: Must include 'bmad' as the orchestrator
+        contains:
+          const: "bmad"
+
+  workflows:
+    type: array
+    description: List of workflows this team can execute
+    minItems: 1
+    items:
+      type: string
+      description: Workflow ID matching bmad-core/workflows/{workflow}.yml
+      enum:
+        - "brownfield-fullstack"
+        - "brownfield-service"
+        - "brownfield-ui"
+        - "greenfield-fullstack"
+        - "greenfield-service"
+        - "greenfield-ui"
+    uniqueItems: true
+
+# No additional properties allowed
+additionalProperties: false
+
+# Validation rules
+allOf:
+  - if:
+      properties:
+        agents:
+          contains:
+            const: "*"
+    then:
+      properties:
+        agents:
+          maxItems: 2
+          description: When using wildcard '*', only 'bmad' and '*' should be present
+
+  - if:
+      properties:
+        bundle:
+          properties:
+            name:
+              const: "Team No UI"
+    then:
+      properties:
+        agents:
+          not:
+            contains:
+              const: "ux-expert"
+        workflows:
+          not:
+            contains:
+              enum: ["brownfield-ui", "greenfield-ui"]
+
+# Examples showing valid team configurations
+examples:
+  minimal_team:
+    bundle:
+      name: "Team Minimal"
+      description: "Minimal team for basic project planning and architecture without implementation"
+    agents:
+      - bmad
+      - analyst
+      - architect
+    workflows:
+      - greenfield-service
+
+  fullstack_team:
+    bundle:
+      name: "Team Fullstack"
+      description: "Comprehensive full-stack development team capable of handling both greenfield application development and brownfield enhancement projects. This team combines strategic planning, user experience design, and holistic system architecture to deliver complete solutions from concept to deployment."
+    agents:
+      - bmad
+      - analyst
+      - pm
+      - ux-expert
+      - architect
+      - po
+    workflows:
+      - brownfield-fullstack
+      - brownfield-service
+      - brownfield-ui
+      - greenfield-fullstack
+      - greenfield-service
+      - greenfield-ui
+
+  all_agents_team:
+    bundle:
+      name: "Team All"
+      description: "This is a full organization of agents and includes every possible agent. This will produce the largest bundle but give the most options for discussion in a single session"
+    agents:
+      - bmad
+      - "*"
+    workflows:
+      - brownfield-fullstack
+      - brownfield-service
+      - brownfield-ui
+      - greenfield-fullstack
+      - greenfield-service
+      - greenfield-ui

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

@@ -0,0 +1,92 @@
+# Advanced Elicitation Task
+
+## Purpose
+
+- 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
+
+## Task Instructions
+
+### 1. Section Context and Review
+
+[[LLM: When invoked after outputting a section:
+
+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.")
+
+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.")
+
+3. If the section contains multiple distinct items (like multiple components, multiple patterns, etc.), 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)
+
+4. Then present the action list as specified below.]]
+
+### 2. Ask for Review and Present Action List
+
+[[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.]]
+
+**Present the numbered list (0-9) with this exact format:**
+
+```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
+```
+
+### 2. Processing Guidelines
+
+**Do NOT show:**
+
+- 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
+
+**After user selection from the list:**
+
+- 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
+
+## Action Definitions
+
+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.]]
+
+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.]]
+
+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. 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.]]
+
+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.]]
+
+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.]]
+
+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.]]
+
+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.]]
+
+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?]]
+
+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.]]

package/.bmad-core/tasks/brainstorming-techniques.md

@@ -0,0 +1,238 @@
+# Brainstorming Techniques Task
+
+This task provides a comprehensive toolkit of creative brainstorming techniques for ideation and innovative thinking. The analyst can use these techniques to facilitate productive brainstorming sessions with users.
+
+## Process
+
+### 1. Session Setup
+
+[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
+
+1. **Establish Context**
+
+   - Understand the problem space or opportunity area
+   - Identify any constraints or parameters
+   - Determine session goals (divergent exploration vs. focused ideation)
+
+2. **Select Technique Approach**
+   - Option A: User selects specific techniques
+   - Option B: Analyst recommends techniques based on context
+   - Option C: Random technique selection for creative variety
+   - Option D: Progressive technique flow (start broad, narrow down)
+
+### 2. Core Brainstorming Techniques
+
+#### Creative Expansion Techniques
+
+1. **"What If" Scenarios**
+   [[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
+
+   - What if we had unlimited resources?
+   - What if this problem didn't exist?
+   - What if we approached this from a child's perspective?
+   - What if we had to solve this in 24 hours?
+
+2. **Analogical Thinking**
+   [[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
+
+   - "How might this work like [X] but for [Y]?"
+   - Nature-inspired solutions (biomimicry)
+   - Cross-industry pattern matching
+   - Historical precedent analysis
+
+3. **Reversal/Inversion**
+   [[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
+
+   - What if we did the exact opposite?
+   - How could we make this problem worse? (then reverse)
+   - Start from the end goal and work backward
+   - Reverse roles or perspectives
+
+4. **First Principles Thinking**
+   [[LLM: Break down to fundamental truths and rebuild from scratch.]]
+   - What are the absolute fundamentals here?
+   - What assumptions can we challenge?
+   - If we started from zero, what would we build?
+   - What laws of physics/economics/human nature apply?
+
+#### Structured Ideation Frameworks
+
+1. **SCAMPER Method**
+   [[LLM: Guide through each SCAMPER prompt systematically.]]
+
+   - **S** = Substitute: What can be substituted?
+   - **C** = Combine: What can be combined or integrated?
+   - **A** = Adapt: What can be adapted from elsewhere?
+   - **M** = Modify/Magnify: What can be emphasized or reduced?
+   - **P** = Put to other uses: What else could this be used for?
+   - **E** = Eliminate: What can be removed or simplified?
+   - **R**= Reverse/Rearrange: What can be reversed or reordered?
+
+2. **Six Thinking Hats**
+   [[LLM: Cycle through different thinking modes, spending focused time in each.]]
+
+   - White Hat: Facts and information
+   - Red Hat: Emotions and intuition
+   - Black Hat: Caution and critical thinking
+   - Yellow Hat: Optimism and benefits
+   - Green Hat: Creativity and alternatives
+   - Blue Hat: Process and control
+
+3. **Mind Mapping**
+   [[LLM: Create text-based mind maps with clear hierarchical structure.]]
+
+   ```plaintext
+   Central Concept
+   ├── Branch 1
+   │   ├── Sub-idea 1.1
+   │   └── Sub-idea 1.2
+   ├── Branch 2
+   │   ├── Sub-idea 2.1
+   │   └── Sub-idea 2.2
+   └── Branch 3
+       └── Sub-idea 3.1
+   ```
+
+#### Collaborative Techniques
+
+1. **"Yes, And..." Building**
+   [[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
+
+   - Accept the premise of each idea
+   - Add to it with "Yes, and..."
+   - Build chains of connected ideas
+   - Explore tangents freely
+
+2. **Brainwriting/Round Robin**
+   [[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
+
+   - Generate ideas from stakeholder perspectives
+   - Build on previous ideas in rounds
+   - Combine unrelated ideas
+   - Cross-pollinate concepts
+
+3. **Random Stimulation**
+   [[LLM: Use random words, images, or concepts as creative triggers.]]
+   - Random word association
+   - Picture/metaphor inspiration
+   - Forced connections between unrelated items
+   - Constraint-based creativity
+
+#### Deep Exploration Techniques
+
+1. **Five Whys**
+   [[LLM: Dig deeper into root causes and underlying motivations.]]
+
+   - Why does this problem exist? → Answer → Why? (repeat 5 times)
+   - Uncover hidden assumptions
+   - Find root causes, not symptoms
+   - Identify intervention points
+
+2. **Morphological Analysis**
+   [[LLM: Break down into parameters and systematically explore combinations.]]
+
+   - List key parameters/dimensions
+   - Identify possible values for each
+   - Create combination matrix
+   - Explore unusual combinations
+
+3. **Provocation Technique (PO)**
+   [[LLM: Make deliberately provocative statements to jar thinking.]]
+   - PO: Cars have square wheels
+   - PO: Customers pay us to take products
+   - PO: The problem solves itself
+   - Extract useful ideas from provocations
+
+### 3. Technique Selection Guide
+
+[[LLM: Help user select appropriate techniques based on their needs.]]
+
+**For Initial Exploration:**
+
+- What If Scenarios
+- First Principles
+- Mind Mapping
+
+**For Stuck/Blocked Thinking:**
+
+- Random Stimulation
+- Reversal/Inversion
+- Provocation Technique
+
+**For Systematic Coverage:**
+
+- SCAMPER
+- Morphological Analysis
+- Six Thinking Hats
+
+**For Deep Understanding:**
+
+- Five Whys
+- Analogical Thinking
+- First Principles
+
+**For Team/Collaborative Settings:**
+
+- Brainwriting
+- "Yes, And..."
+- Six Thinking Hats
+
+### 4. Session Flow Management
+
+[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
+
+1. **Warm-up Phase** (5-10 min)
+
+   - Start with accessible techniques
+   - Build creative confidence
+   - Establish "no judgment" atmosphere
+
+2. **Divergent Phase** (20-30 min)
+
+   - Use expansion techniques
+   - Generate quantity over quality
+   - Encourage wild ideas
+
+3. **Convergent Phase** (15-20 min)
+
+   - Group and categorize ideas
+   - Identify patterns and themes
+   - Select promising directions
+
+4. **Synthesis Phase** (10-15 min)
+   - Combine complementary ideas
+   - Refine and develop concepts
+   - Prepare summary of insights
+
+### 5. Output Format
+
+[[LLM: Present brainstorming results in an organized, actionable format.]]
+
+**Session Summary:**
+
+- Techniques used
+- Number of ideas generated
+- Key themes identified
+
+**Idea Categories:**
+
+1. **Immediate Opportunities** - Ideas that could be implemented now
+2. **Future Innovations** - Ideas requiring more development
+3. **Moonshots** - Ambitious, transformative ideas
+4. **Insights & Learnings** - Key realizations from the session
+
+**Next Steps:**
+
+- Which ideas to explore further
+- Recommended follow-up techniques
+- Suggested research areas
+
+## Important Notes
+
+- Maintain energy and momentum throughout the session
+- Defer judgment - all ideas are valid during generation
+- Quantity leads to quality - aim for many ideas
+- Build on ideas collaboratively
+- Document everything - even "silly" ideas can spark breakthroughs
+- Take breaks if energy flags
+- End with clear next actions