feat: big improvement to advanced elicitation
This commit is contained in:
@@ -1,31 +1,36 @@
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
|
||||
1. **What If Scenarios**: Ask one provocative question, get their response, then ask another
|
||||
2. **Analogical Thinking**: Give one example analogy, ask them to find 2-3 more
|
||||
3. **Reversal/Inversion**: Pose the reverse question, let them work through it
|
||||
4. **First Principles Thinking**: Ask "What are the fundamentals?" and guide them to break it down
|
||||
|
||||
## Structured Frameworks
|
||||
|
||||
5. **SCAMPER Method**: Go through one letter at a time, wait for their ideas before moving to next
|
||||
6. **Six Thinking Hats**: Present one hat, ask for their thoughts, then move to next hat
|
||||
7. **Mind Mapping**: Start with central concept, ask them to suggest branches
|
||||
|
||||
## Collaborative Techniques
|
||||
|
||||
8. **"Yes, And..." Building**: They give idea, you "yes and" it, they "yes and" back - alternate
|
||||
9. **Brainwriting/Round Robin**: They suggest idea, you build on it, ask them to build on yours
|
||||
10. **Random Stimulation**: Give one random prompt/word, ask them to make connections
|
||||
|
||||
## Deep Exploration
|
||||
|
||||
11. **Five Whys**: Ask "why" and wait for their answer before asking next "why"
|
||||
12. **Morphological Analysis**: Ask them to list parameters first, then explore combinations together
|
||||
13. **Provocation Technique (PO)**: Give one provocative statement, ask them to extract useful ideas
|
||||
|
||||
## Advanced Techniques
|
||||
|
||||
14. **Forced Relationships**: Connect two unrelated concepts and ask them to find the bridge
|
||||
15. **Assumption Reversal**: Challenge their core assumptions and ask them to build from there
|
||||
16. **Role Playing**: Ask them to brainstorm from different stakeholder perspectives
|
||||
17. **Time Shifting**: "How would you solve this in 1995? 2030?"
|
||||
18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
|
||||
19. **Metaphor Mapping**: Use extended metaphors to explore solutions
|
||||
20. **Question Storming**: Generate questions instead of answers first
|
||||
20. **Question Storming**: Generate questions instead of answers first
|
||||
|
||||
134
bmad-core/data/elicitation-methods.md
Normal file
134
bmad-core/data/elicitation-methods.md
Normal file
@@ -0,0 +1,134 @@
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
|
||||
**Expand or Contract for Audience**
|
||||
- Ask whether to 'expand' (add detail, elaborate) or 'contract' (simplify, clarify)
|
||||
- Identify specific target audience if relevant
|
||||
- Tailor content complexity and depth accordingly
|
||||
|
||||
**Explain Reasoning (CoT Step-by-Step)**
|
||||
- Walk through the step-by-step thinking process
|
||||
- Reveal underlying assumptions and decision points
|
||||
- Show how conclusions were reached from current role's perspective
|
||||
|
||||
**Critique and Refine**
|
||||
- Review output for flaws, inconsistencies, or improvement areas
|
||||
- Identify specific weaknesses from role's expertise
|
||||
- Suggest refined version reflecting domain knowledge
|
||||
|
||||
## Structural Analysis Methods
|
||||
|
||||
**Analyze Logical Flow and Dependencies**
|
||||
- Examine content structure for logical progression
|
||||
- Check internal consistency and coherence
|
||||
- Identify and validate dependencies between elements
|
||||
- Confirm effective ordering and sequencing
|
||||
|
||||
**Assess Alignment with Overall Goals**
|
||||
- Evaluate content contribution to stated objectives
|
||||
- Identify any misalignments or gaps
|
||||
- Interpret alignment from specific role's perspective
|
||||
- Suggest adjustments to better serve goals
|
||||
|
||||
## Risk and Challenge Methods
|
||||
|
||||
**Identify Potential Risks and Unforeseen Issues**
|
||||
- Brainstorm potential risks from role's expertise
|
||||
- Identify overlooked edge cases or scenarios
|
||||
- Anticipate unintended consequences
|
||||
- Highlight implementation challenges
|
||||
|
||||
**Challenge from Critical Perspective**
|
||||
- Adopt critical stance on current content
|
||||
- Play devil's advocate from specified viewpoint
|
||||
- Argue against proposal highlighting weaknesses
|
||||
- Apply YAGNI principles when appropriate (scope trimming)
|
||||
|
||||
## Creative Exploration Methods
|
||||
|
||||
**Tree of Thoughts Deep Dive**
|
||||
- Break problem into discrete "thoughts" or intermediate steps
|
||||
- Explore multiple reasoning paths simultaneously
|
||||
- Use self-evaluation to classify each path as "sure", "likely", or "impossible"
|
||||
- Apply search algorithms (BFS/DFS) to find optimal solution paths
|
||||
|
||||
**Hindsight is 20/20: The 'If Only...' Reflection**
|
||||
- Imagine retrospective scenario based on current content
|
||||
- Identify the one "if only we had known/done X..." insight
|
||||
- Describe imagined consequences humorously or dramatically
|
||||
- Extract actionable learnings for current context
|
||||
|
||||
## Multi-Persona Collaboration Methods
|
||||
|
||||
**Agile Team Perspective Shift**
|
||||
- Rotate through different Scrum team member viewpoints
|
||||
- Product Owner: Focus on user value and business impact
|
||||
- Scrum Master: Examine process flow and team dynamics
|
||||
- Developer: Assess technical implementation and complexity
|
||||
- QA: Identify testing scenarios and quality concerns
|
||||
|
||||
**Stakeholder Round Table**
|
||||
- Convene virtual meeting with multiple personas
|
||||
- Each persona contributes unique perspective on content
|
||||
- Identify conflicts and synergies between viewpoints
|
||||
- Synthesize insights into actionable recommendations
|
||||
|
||||
**Meta-Prompting Analysis**
|
||||
- Step back to analyze the structure and logic of current approach
|
||||
- Question the format and methodology being used
|
||||
- Suggest alternative frameworks or mental models
|
||||
- Optimize the elicitation process itself
|
||||
|
||||
## Advanced 2025 Techniques
|
||||
|
||||
**Self-Consistency Validation**
|
||||
- Generate multiple reasoning paths for same problem
|
||||
- Compare consistency across different approaches
|
||||
- Identify most reliable and robust solution
|
||||
- Highlight areas where approaches diverge and why
|
||||
|
||||
**ReWOO (Reasoning Without Observation)**
|
||||
- Separate parametric reasoning from tool-based actions
|
||||
- Create reasoning plan without external dependencies
|
||||
- Identify what can be solved through pure reasoning
|
||||
- Optimize for efficiency and reduced token usage
|
||||
|
||||
**Persona-Pattern Hybrid**
|
||||
- Combine specific role expertise with elicitation pattern
|
||||
- Architect + Risk Analysis: Deep technical risk assessment
|
||||
- UX Expert + User Journey: End-to-end experience critique
|
||||
- PM + Stakeholder Analysis: Multi-perspective impact review
|
||||
|
||||
**Emergent Collaboration Discovery**
|
||||
- Allow multiple perspectives to naturally emerge
|
||||
- Identify unexpected insights from persona interactions
|
||||
- Explore novel combinations of viewpoints
|
||||
- Capture serendipitous discoveries from multi-agent thinking
|
||||
|
||||
## Game-Based Elicitation Methods
|
||||
|
||||
**Red Team vs Blue Team**
|
||||
- Red Team: Attack the proposal, find vulnerabilities
|
||||
- Blue Team: Defend and strengthen the approach
|
||||
- Competitive analysis reveals blind spots
|
||||
- Results in more robust, battle-tested solutions
|
||||
|
||||
**Innovation Tournament**
|
||||
- Pit multiple alternative approaches against each other
|
||||
- Score each approach across different criteria
|
||||
- Crowd-source evaluation from different personas
|
||||
- Identify winning combination of features
|
||||
|
||||
**Escape Room Challenge**
|
||||
- Present content as constraints to work within
|
||||
- Find creative solutions within tight limitations
|
||||
- Identify minimum viable approach
|
||||
- Discover innovative workarounds and optimizations
|
||||
|
||||
## Process Control
|
||||
|
||||
**Proceed / No Further Actions**
|
||||
- Acknowledge choice to finalize current work
|
||||
- Accept output as-is or move to next step
|
||||
- Prepare to continue without additional elicitation
|
||||
Reference in New Issue
Block a user