siesa-agents 2.1.2 → 2.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +83 -83
- package/bin/install.js +400 -400
- package/bin/prepare-publish.js +26 -26
- package/bin/restore-folders.js +26 -26
- package/bmad-core/agent-teams/team-all.yaml +15 -15
- package/bmad-core/agent-teams/team-fullstack.yaml +19 -19
- package/bmad-core/agent-teams/team-ide-minimal.yaml +11 -11
- package/bmad-core/agent-teams/team-no-ui.yaml +14 -14
- package/bmad-core/agents/analyst.md +84 -84
- package/bmad-core/agents/architect.md +94 -94
- package/bmad-core/agents/backend-agent.md +189 -189
- package/bmad-core/agents/bmad-master.md +110 -110
- package/bmad-core/agents/bmad-orchestrator.md +147 -147
- package/bmad-core/agents/dev.md +81 -81
- package/bmad-core/agents/frontend-agent.md +168 -168
- package/bmad-core/agents/pm.md +84 -84
- package/bmad-core/agents/po.md +79 -79
- package/bmad-core/agents/qa.md +91 -91
- package/bmad-core/agents/sm.md +65 -65
- package/bmad-core/agents/ux-expert.md +69 -69
- package/bmad-core/checklists/architect-checklist.md +440 -440
- package/bmad-core/checklists/backend-checklist.md +142 -142
- package/bmad-core/checklists/change-checklist.md +184 -184
- package/bmad-core/checklists/frontend-checklist.md +105 -105
- package/bmad-core/checklists/pm-checklist.md +372 -372
- package/bmad-core/checklists/po-master-checklist.md +434 -434
- package/bmad-core/checklists/story-dod-checklist.md +96 -96
- package/bmad-core/checklists/story-draft-checklist.md +155 -155
- package/bmad-core/core-config.yaml +22 -22
- package/bmad-core/data/backend-standards.md +439 -439
- package/bmad-core/data/bmad-kb.md +809 -809
- package/bmad-core/data/brainstorming-techniques.md +38 -38
- package/bmad-core/data/elicitation-methods.md +156 -156
- package/bmad-core/data/frontend-standards.md +323 -323
- package/bmad-core/data/technical-preferences.md +5 -5
- package/bmad-core/data/test-levels-framework.md +148 -148
- package/bmad-core/data/test-priorities-matrix.md +174 -174
- package/bmad-core/enhanced-ide-development-workflow.md +248 -248
- package/bmad-core/install-manifest.yaml +230 -230
- package/bmad-core/tasks/advanced-elicitation.md +119 -119
- package/bmad-core/tasks/apply-qa-fixes.md +150 -150
- package/bmad-core/tasks/brownfield-create-epic.md +162 -162
- package/bmad-core/tasks/brownfield-create-story.md +149 -149
- package/bmad-core/tasks/correct-course.md +72 -72
- package/bmad-core/tasks/create-brownfield-story.md +314 -314
- package/bmad-core/tasks/create-component.md +102 -102
- package/bmad-core/tasks/create-deep-research-prompt.md +280 -280
- package/bmad-core/tasks/create-doc.md +103 -103
- package/bmad-core/tasks/create-entity.md +132 -132
- package/bmad-core/tasks/create-feature.md +90 -90
- package/bmad-core/tasks/create-next-story.md +114 -114
- package/bmad-core/tasks/create-service.md +117 -117
- package/bmad-core/tasks/create-use-case.md +140 -140
- package/bmad-core/tasks/document-project.md +345 -345
- package/bmad-core/tasks/execute-checklist.md +88 -88
- package/bmad-core/tasks/facilitate-brainstorming-session.md +138 -138
- package/bmad-core/tasks/generate-ai-frontend-prompt.md +53 -53
- package/bmad-core/tasks/index-docs.md +175 -175
- package/bmad-core/tasks/kb-mode-interaction.md +77 -77
- package/bmad-core/tasks/nfr-assess.md +345 -345
- package/bmad-core/tasks/qa-gate.md +163 -163
- package/bmad-core/tasks/review-story.md +316 -316
- package/bmad-core/tasks/risk-profile.md +355 -355
- package/bmad-core/tasks/scaffold-backend.md +110 -110
- package/bmad-core/tasks/scaffold-frontend.md +78 -78
- package/bmad-core/tasks/shard-doc.md +187 -187
- package/bmad-core/tasks/test-design.md +176 -176
- package/bmad-core/tasks/trace-requirements.md +266 -266
- package/bmad-core/tasks/validate-next-story.md +136 -136
- package/bmad-core/templates/architecture-tmpl.yaml +662 -662
- package/bmad-core/templates/brainstorming-output-tmpl.yaml +156 -156
- package/bmad-core/templates/brownfield-architecture-tmpl.yaml +477 -477
- package/bmad-core/templates/brownfield-prd-tmpl.yaml +281 -281
- package/bmad-core/templates/competitor-analysis-tmpl.yaml +307 -307
- package/bmad-core/templates/front-end-architecture-tmpl.yaml +258 -258
- package/bmad-core/templates/front-end-spec-tmpl.yaml +350 -350
- package/bmad-core/templates/fullstack-architecture-tmpl.yaml +824 -824
- package/bmad-core/templates/market-research-tmpl.yaml +253 -253
- package/bmad-core/templates/prd-tmpl.yaml +203 -203
- package/bmad-core/templates/project-brief-tmpl.yaml +222 -222
- package/bmad-core/templates/qa-gate-tmpl.yaml +103 -103
- package/bmad-core/templates/story-tmpl.yaml +138 -138
- package/bmad-core/user-guide.md +530 -530
- package/bmad-core/utils/bmad-doc-template.md +327 -327
- package/bmad-core/utils/workflow-management.md +71 -71
- package/bmad-core/workflows/brownfield-fullstack.yaml +298 -298
- package/bmad-core/workflows/brownfield-service.yaml +188 -188
- package/bmad-core/workflows/brownfield-ui.yaml +198 -198
- package/bmad-core/workflows/greenfield-fullstack.yaml +241 -241
- package/bmad-core/workflows/greenfield-service.yaml +207 -207
- package/bmad-core/workflows/greenfield-ui.yaml +236 -236
- package/bmad-core/working-in-the-brownfield.md +606 -606
- package/claude/commands/BMad/agents/backend.md +187 -187
- package/claude/commands/BMad/agents/frontend.md +150 -150
- package/github/b-mad-expert.md +742 -742
- package/github/chatmodes/analyst.chatmode.md +89 -89
- package/github/chatmodes/architect.chatmode.md +97 -97
- package/github/chatmodes/backend.chatmode.md +194 -194
- package/github/chatmodes/bmad-master.chatmode.md +115 -115
- package/github/chatmodes/bmad-orchestrator.chatmode.md +152 -152
- package/github/chatmodes/dev.chatmode.md +86 -86
- package/github/chatmodes/frontend.chatmode.md +157 -157
- package/github/chatmodes/pm.chatmode.md +89 -89
- package/github/chatmodes/po.chatmode.md +84 -84
- package/github/chatmodes/qa.chatmode.md +96 -96
- package/github/chatmodes/sm.chatmode.md +70 -70
- package/github/chatmodes/ux-expert.chatmode.md +74 -74
- package/index.js +9 -9
- package/package.json +37 -37
- package/vscode/mcp.json +11 -11
- package/vscode/settings.json +12 -12
|
@@ -1,38 +1,38 @@
|
|
|
1
|
-
<!-- Powered by BMAD™ Core -->
|
|
2
|
-
|
|
3
|
-
# Brainstorming Techniques Data
|
|
4
|
-
|
|
5
|
-
## Creative Expansion
|
|
6
|
-
|
|
7
|
-
1. **What If Scenarios**: Ask one provocative question, get their response, then ask another
|
|
8
|
-
2. **Analogical Thinking**: Give one example analogy, ask them to find 2-3 more
|
|
9
|
-
3. **Reversal/Inversion**: Pose the reverse question, let them work through it
|
|
10
|
-
4. **First Principles Thinking**: Ask "What are the fundamentals?" and guide them to break it down
|
|
11
|
-
|
|
12
|
-
## Structured Frameworks
|
|
13
|
-
|
|
14
|
-
5. **SCAMPER Method**: Go through one letter at a time, wait for their ideas before moving to next
|
|
15
|
-
6. **Six Thinking Hats**: Present one hat, ask for their thoughts, then move to next hat
|
|
16
|
-
7. **Mind Mapping**: Start with central concept, ask them to suggest branches
|
|
17
|
-
|
|
18
|
-
## Collaborative Techniques
|
|
19
|
-
|
|
20
|
-
8. **"Yes, And..." Building**: They give idea, you "yes and" it, they "yes and" back - alternate
|
|
21
|
-
9. **Brainwriting/Round Robin**: They suggest idea, you build on it, ask them to build on yours
|
|
22
|
-
10. **Random Stimulation**: Give one random prompt/word, ask them to make connections
|
|
23
|
-
|
|
24
|
-
## Deep Exploration
|
|
25
|
-
|
|
26
|
-
11. **Five Whys**: Ask "why" and wait for their answer before asking next "why"
|
|
27
|
-
12. **Morphological Analysis**: Ask them to list parameters first, then explore combinations together
|
|
28
|
-
13. **Provocation Technique (PO)**: Give one provocative statement, ask them to extract useful ideas
|
|
29
|
-
|
|
30
|
-
## Advanced Techniques
|
|
31
|
-
|
|
32
|
-
14. **Forced Relationships**: Connect two unrelated concepts and ask them to find the bridge
|
|
33
|
-
15. **Assumption Reversal**: Challenge their core assumptions and ask them to build from there
|
|
34
|
-
16. **Role Playing**: Ask them to brainstorm from different stakeholder perspectives
|
|
35
|
-
17. **Time Shifting**: "How would you solve this in 1995? 2030?"
|
|
36
|
-
18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
|
|
37
|
-
19. **Metaphor Mapping**: Use extended metaphors to explore solutions
|
|
38
|
-
20. **Question Storming**: Generate questions instead of answers first
|
|
1
|
+
<!-- Powered by BMAD™ Core -->
|
|
2
|
+
|
|
3
|
+
# Brainstorming Techniques Data
|
|
4
|
+
|
|
5
|
+
## Creative Expansion
|
|
6
|
+
|
|
7
|
+
1. **What If Scenarios**: Ask one provocative question, get their response, then ask another
|
|
8
|
+
2. **Analogical Thinking**: Give one example analogy, ask them to find 2-3 more
|
|
9
|
+
3. **Reversal/Inversion**: Pose the reverse question, let them work through it
|
|
10
|
+
4. **First Principles Thinking**: Ask "What are the fundamentals?" and guide them to break it down
|
|
11
|
+
|
|
12
|
+
## Structured Frameworks
|
|
13
|
+
|
|
14
|
+
5. **SCAMPER Method**: Go through one letter at a time, wait for their ideas before moving to next
|
|
15
|
+
6. **Six Thinking Hats**: Present one hat, ask for their thoughts, then move to next hat
|
|
16
|
+
7. **Mind Mapping**: Start with central concept, ask them to suggest branches
|
|
17
|
+
|
|
18
|
+
## Collaborative Techniques
|
|
19
|
+
|
|
20
|
+
8. **"Yes, And..." Building**: They give idea, you "yes and" it, they "yes and" back - alternate
|
|
21
|
+
9. **Brainwriting/Round Robin**: They suggest idea, you build on it, ask them to build on yours
|
|
22
|
+
10. **Random Stimulation**: Give one random prompt/word, ask them to make connections
|
|
23
|
+
|
|
24
|
+
## Deep Exploration
|
|
25
|
+
|
|
26
|
+
11. **Five Whys**: Ask "why" and wait for their answer before asking next "why"
|
|
27
|
+
12. **Morphological Analysis**: Ask them to list parameters first, then explore combinations together
|
|
28
|
+
13. **Provocation Technique (PO)**: Give one provocative statement, ask them to extract useful ideas
|
|
29
|
+
|
|
30
|
+
## Advanced Techniques
|
|
31
|
+
|
|
32
|
+
14. **Forced Relationships**: Connect two unrelated concepts and ask them to find the bridge
|
|
33
|
+
15. **Assumption Reversal**: Challenge their core assumptions and ask them to build from there
|
|
34
|
+
16. **Role Playing**: Ask them to brainstorm from different stakeholder perspectives
|
|
35
|
+
17. **Time Shifting**: "How would you solve this in 1995? 2030?"
|
|
36
|
+
18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
|
|
37
|
+
19. **Metaphor Mapping**: Use extended metaphors to explore solutions
|
|
38
|
+
20. **Question Storming**: Generate questions instead of answers first
|
|
@@ -1,156 +1,156 @@
|
|
|
1
|
-
<!-- Powered by BMAD™ Core -->
|
|
2
|
-
|
|
3
|
-
# Elicitation Methods Data
|
|
4
|
-
|
|
5
|
-
## Core Reflective Methods
|
|
6
|
-
|
|
7
|
-
**Expand or Contract for Audience**
|
|
8
|
-
|
|
9
|
-
- Ask whether to 'expand' (add detail, elaborate) or 'contract' (simplify, clarify)
|
|
10
|
-
- Identify specific target audience if relevant
|
|
11
|
-
- Tailor content complexity and depth accordingly
|
|
12
|
-
|
|
13
|
-
**Explain Reasoning (CoT Step-by-Step)**
|
|
14
|
-
|
|
15
|
-
- Walk through the step-by-step thinking process
|
|
16
|
-
- Reveal underlying assumptions and decision points
|
|
17
|
-
- Show how conclusions were reached from current role's perspective
|
|
18
|
-
|
|
19
|
-
**Critique and Refine**
|
|
20
|
-
|
|
21
|
-
- Review output for flaws, inconsistencies, or improvement areas
|
|
22
|
-
- Identify specific weaknesses from role's expertise
|
|
23
|
-
- Suggest refined version reflecting domain knowledge
|
|
24
|
-
|
|
25
|
-
## Structural Analysis Methods
|
|
26
|
-
|
|
27
|
-
**Analyze Logical Flow and Dependencies**
|
|
28
|
-
|
|
29
|
-
- Examine content structure for logical progression
|
|
30
|
-
- Check internal consistency and coherence
|
|
31
|
-
- Identify and validate dependencies between elements
|
|
32
|
-
- Confirm effective ordering and sequencing
|
|
33
|
-
|
|
34
|
-
**Assess Alignment with Overall Goals**
|
|
35
|
-
|
|
36
|
-
- Evaluate content contribution to stated objectives
|
|
37
|
-
- Identify any misalignments or gaps
|
|
38
|
-
- Interpret alignment from specific role's perspective
|
|
39
|
-
- Suggest adjustments to better serve goals
|
|
40
|
-
|
|
41
|
-
## Risk and Challenge Methods
|
|
42
|
-
|
|
43
|
-
**Identify Potential Risks and Unforeseen Issues**
|
|
44
|
-
|
|
45
|
-
- Brainstorm potential risks from role's expertise
|
|
46
|
-
- Identify overlooked edge cases or scenarios
|
|
47
|
-
- Anticipate unintended consequences
|
|
48
|
-
- Highlight implementation challenges
|
|
49
|
-
|
|
50
|
-
**Challenge from Critical Perspective**
|
|
51
|
-
|
|
52
|
-
- Adopt critical stance on current content
|
|
53
|
-
- Play devil's advocate from specified viewpoint
|
|
54
|
-
- Argue against proposal highlighting weaknesses
|
|
55
|
-
- Apply YAGNI principles when appropriate (scope trimming)
|
|
56
|
-
|
|
57
|
-
## Creative Exploration Methods
|
|
58
|
-
|
|
59
|
-
**Tree of Thoughts Deep Dive**
|
|
60
|
-
|
|
61
|
-
- Break problem into discrete "thoughts" or intermediate steps
|
|
62
|
-
- Explore multiple reasoning paths simultaneously
|
|
63
|
-
- Use self-evaluation to classify each path as "sure", "likely", or "impossible"
|
|
64
|
-
- Apply search algorithms (BFS/DFS) to find optimal solution paths
|
|
65
|
-
|
|
66
|
-
**Hindsight is 20/20: The 'If Only...' Reflection**
|
|
67
|
-
|
|
68
|
-
- Imagine retrospective scenario based on current content
|
|
69
|
-
- Identify the one "if only we had known/done X..." insight
|
|
70
|
-
- Describe imagined consequences humorously or dramatically
|
|
71
|
-
- Extract actionable learnings for current context
|
|
72
|
-
|
|
73
|
-
## Multi-Persona Collaboration Methods
|
|
74
|
-
|
|
75
|
-
**Agile Team Perspective Shift**
|
|
76
|
-
|
|
77
|
-
- Rotate through different Scrum team member viewpoints
|
|
78
|
-
- Product Owner: Focus on user value and business impact
|
|
79
|
-
- Scrum Master: Examine process flow and team dynamics
|
|
80
|
-
- Developer: Assess technical implementation and complexity
|
|
81
|
-
- QA: Identify testing scenarios and quality concerns
|
|
82
|
-
|
|
83
|
-
**Stakeholder Round Table**
|
|
84
|
-
|
|
85
|
-
- Convene virtual meeting with multiple personas
|
|
86
|
-
- Each persona contributes unique perspective on content
|
|
87
|
-
- Identify conflicts and synergies between viewpoints
|
|
88
|
-
- Synthesize insights into actionable recommendations
|
|
89
|
-
|
|
90
|
-
**Meta-Prompting Analysis**
|
|
91
|
-
|
|
92
|
-
- Step back to analyze the structure and logic of current approach
|
|
93
|
-
- Question the format and methodology being used
|
|
94
|
-
- Suggest alternative frameworks or mental models
|
|
95
|
-
- Optimize the elicitation process itself
|
|
96
|
-
|
|
97
|
-
## Advanced 2025 Techniques
|
|
98
|
-
|
|
99
|
-
**Self-Consistency Validation**
|
|
100
|
-
|
|
101
|
-
- Generate multiple reasoning paths for same problem
|
|
102
|
-
- Compare consistency across different approaches
|
|
103
|
-
- Identify most reliable and robust solution
|
|
104
|
-
- Highlight areas where approaches diverge and why
|
|
105
|
-
|
|
106
|
-
**ReWOO (Reasoning Without Observation)**
|
|
107
|
-
|
|
108
|
-
- Separate parametric reasoning from tool-based actions
|
|
109
|
-
- Create reasoning plan without external dependencies
|
|
110
|
-
- Identify what can be solved through pure reasoning
|
|
111
|
-
- Optimize for efficiency and reduced token usage
|
|
112
|
-
|
|
113
|
-
**Persona-Pattern Hybrid**
|
|
114
|
-
|
|
115
|
-
- Combine specific role expertise with elicitation pattern
|
|
116
|
-
- Architect + Risk Analysis: Deep technical risk assessment
|
|
117
|
-
- UX Expert + User Journey: End-to-end experience critique
|
|
118
|
-
- PM + Stakeholder Analysis: Multi-perspective impact review
|
|
119
|
-
|
|
120
|
-
**Emergent Collaboration Discovery**
|
|
121
|
-
|
|
122
|
-
- Allow multiple perspectives to naturally emerge
|
|
123
|
-
- Identify unexpected insights from persona interactions
|
|
124
|
-
- Explore novel combinations of viewpoints
|
|
125
|
-
- Capture serendipitous discoveries from multi-agent thinking
|
|
126
|
-
|
|
127
|
-
## Game-Based Elicitation Methods
|
|
128
|
-
|
|
129
|
-
**Red Team vs Blue Team**
|
|
130
|
-
|
|
131
|
-
- Red Team: Attack the proposal, find vulnerabilities
|
|
132
|
-
- Blue Team: Defend and strengthen the approach
|
|
133
|
-
- Competitive analysis reveals blind spots
|
|
134
|
-
- Results in more robust, battle-tested solutions
|
|
135
|
-
|
|
136
|
-
**Innovation Tournament**
|
|
137
|
-
|
|
138
|
-
- Pit multiple alternative approaches against each other
|
|
139
|
-
- Score each approach across different criteria
|
|
140
|
-
- Crowd-source evaluation from different personas
|
|
141
|
-
- Identify winning combination of features
|
|
142
|
-
|
|
143
|
-
**Escape Room Challenge**
|
|
144
|
-
|
|
145
|
-
- Present content as constraints to work within
|
|
146
|
-
- Find creative solutions within tight limitations
|
|
147
|
-
- Identify minimum viable approach
|
|
148
|
-
- Discover innovative workarounds and optimizations
|
|
149
|
-
|
|
150
|
-
## Process Control
|
|
151
|
-
|
|
152
|
-
**Proceed / No Further Actions**
|
|
153
|
-
|
|
154
|
-
- Acknowledge choice to finalize current work
|
|
155
|
-
- Accept output as-is or move to next step
|
|
156
|
-
- Prepare to continue without additional elicitation
|
|
1
|
+
<!-- Powered by BMAD™ Core -->
|
|
2
|
+
|
|
3
|
+
# Elicitation Methods Data
|
|
4
|
+
|
|
5
|
+
## Core Reflective Methods
|
|
6
|
+
|
|
7
|
+
**Expand or Contract for Audience**
|
|
8
|
+
|
|
9
|
+
- Ask whether to 'expand' (add detail, elaborate) or 'contract' (simplify, clarify)
|
|
10
|
+
- Identify specific target audience if relevant
|
|
11
|
+
- Tailor content complexity and depth accordingly
|
|
12
|
+
|
|
13
|
+
**Explain Reasoning (CoT Step-by-Step)**
|
|
14
|
+
|
|
15
|
+
- Walk through the step-by-step thinking process
|
|
16
|
+
- Reveal underlying assumptions and decision points
|
|
17
|
+
- Show how conclusions were reached from current role's perspective
|
|
18
|
+
|
|
19
|
+
**Critique and Refine**
|
|
20
|
+
|
|
21
|
+
- Review output for flaws, inconsistencies, or improvement areas
|
|
22
|
+
- Identify specific weaknesses from role's expertise
|
|
23
|
+
- Suggest refined version reflecting domain knowledge
|
|
24
|
+
|
|
25
|
+
## Structural Analysis Methods
|
|
26
|
+
|
|
27
|
+
**Analyze Logical Flow and Dependencies**
|
|
28
|
+
|
|
29
|
+
- Examine content structure for logical progression
|
|
30
|
+
- Check internal consistency and coherence
|
|
31
|
+
- Identify and validate dependencies between elements
|
|
32
|
+
- Confirm effective ordering and sequencing
|
|
33
|
+
|
|
34
|
+
**Assess Alignment with Overall Goals**
|
|
35
|
+
|
|
36
|
+
- Evaluate content contribution to stated objectives
|
|
37
|
+
- Identify any misalignments or gaps
|
|
38
|
+
- Interpret alignment from specific role's perspective
|
|
39
|
+
- Suggest adjustments to better serve goals
|
|
40
|
+
|
|
41
|
+
## Risk and Challenge Methods
|
|
42
|
+
|
|
43
|
+
**Identify Potential Risks and Unforeseen Issues**
|
|
44
|
+
|
|
45
|
+
- Brainstorm potential risks from role's expertise
|
|
46
|
+
- Identify overlooked edge cases or scenarios
|
|
47
|
+
- Anticipate unintended consequences
|
|
48
|
+
- Highlight implementation challenges
|
|
49
|
+
|
|
50
|
+
**Challenge from Critical Perspective**
|
|
51
|
+
|
|
52
|
+
- Adopt critical stance on current content
|
|
53
|
+
- Play devil's advocate from specified viewpoint
|
|
54
|
+
- Argue against proposal highlighting weaknesses
|
|
55
|
+
- Apply YAGNI principles when appropriate (scope trimming)
|
|
56
|
+
|
|
57
|
+
## Creative Exploration Methods
|
|
58
|
+
|
|
59
|
+
**Tree of Thoughts Deep Dive**
|
|
60
|
+
|
|
61
|
+
- Break problem into discrete "thoughts" or intermediate steps
|
|
62
|
+
- Explore multiple reasoning paths simultaneously
|
|
63
|
+
- Use self-evaluation to classify each path as "sure", "likely", or "impossible"
|
|
64
|
+
- Apply search algorithms (BFS/DFS) to find optimal solution paths
|
|
65
|
+
|
|
66
|
+
**Hindsight is 20/20: The 'If Only...' Reflection**
|
|
67
|
+
|
|
68
|
+
- Imagine retrospective scenario based on current content
|
|
69
|
+
- Identify the one "if only we had known/done X..." insight
|
|
70
|
+
- Describe imagined consequences humorously or dramatically
|
|
71
|
+
- Extract actionable learnings for current context
|
|
72
|
+
|
|
73
|
+
## Multi-Persona Collaboration Methods
|
|
74
|
+
|
|
75
|
+
**Agile Team Perspective Shift**
|
|
76
|
+
|
|
77
|
+
- Rotate through different Scrum team member viewpoints
|
|
78
|
+
- Product Owner: Focus on user value and business impact
|
|
79
|
+
- Scrum Master: Examine process flow and team dynamics
|
|
80
|
+
- Developer: Assess technical implementation and complexity
|
|
81
|
+
- QA: Identify testing scenarios and quality concerns
|
|
82
|
+
|
|
83
|
+
**Stakeholder Round Table**
|
|
84
|
+
|
|
85
|
+
- Convene virtual meeting with multiple personas
|
|
86
|
+
- Each persona contributes unique perspective on content
|
|
87
|
+
- Identify conflicts and synergies between viewpoints
|
|
88
|
+
- Synthesize insights into actionable recommendations
|
|
89
|
+
|
|
90
|
+
**Meta-Prompting Analysis**
|
|
91
|
+
|
|
92
|
+
- Step back to analyze the structure and logic of current approach
|
|
93
|
+
- Question the format and methodology being used
|
|
94
|
+
- Suggest alternative frameworks or mental models
|
|
95
|
+
- Optimize the elicitation process itself
|
|
96
|
+
|
|
97
|
+
## Advanced 2025 Techniques
|
|
98
|
+
|
|
99
|
+
**Self-Consistency Validation**
|
|
100
|
+
|
|
101
|
+
- Generate multiple reasoning paths for same problem
|
|
102
|
+
- Compare consistency across different approaches
|
|
103
|
+
- Identify most reliable and robust solution
|
|
104
|
+
- Highlight areas where approaches diverge and why
|
|
105
|
+
|
|
106
|
+
**ReWOO (Reasoning Without Observation)**
|
|
107
|
+
|
|
108
|
+
- Separate parametric reasoning from tool-based actions
|
|
109
|
+
- Create reasoning plan without external dependencies
|
|
110
|
+
- Identify what can be solved through pure reasoning
|
|
111
|
+
- Optimize for efficiency and reduced token usage
|
|
112
|
+
|
|
113
|
+
**Persona-Pattern Hybrid**
|
|
114
|
+
|
|
115
|
+
- Combine specific role expertise with elicitation pattern
|
|
116
|
+
- Architect + Risk Analysis: Deep technical risk assessment
|
|
117
|
+
- UX Expert + User Journey: End-to-end experience critique
|
|
118
|
+
- PM + Stakeholder Analysis: Multi-perspective impact review
|
|
119
|
+
|
|
120
|
+
**Emergent Collaboration Discovery**
|
|
121
|
+
|
|
122
|
+
- Allow multiple perspectives to naturally emerge
|
|
123
|
+
- Identify unexpected insights from persona interactions
|
|
124
|
+
- Explore novel combinations of viewpoints
|
|
125
|
+
- Capture serendipitous discoveries from multi-agent thinking
|
|
126
|
+
|
|
127
|
+
## Game-Based Elicitation Methods
|
|
128
|
+
|
|
129
|
+
**Red Team vs Blue Team**
|
|
130
|
+
|
|
131
|
+
- Red Team: Attack the proposal, find vulnerabilities
|
|
132
|
+
- Blue Team: Defend and strengthen the approach
|
|
133
|
+
- Competitive analysis reveals blind spots
|
|
134
|
+
- Results in more robust, battle-tested solutions
|
|
135
|
+
|
|
136
|
+
**Innovation Tournament**
|
|
137
|
+
|
|
138
|
+
- Pit multiple alternative approaches against each other
|
|
139
|
+
- Score each approach across different criteria
|
|
140
|
+
- Crowd-source evaluation from different personas
|
|
141
|
+
- Identify winning combination of features
|
|
142
|
+
|
|
143
|
+
**Escape Room Challenge**
|
|
144
|
+
|
|
145
|
+
- Present content as constraints to work within
|
|
146
|
+
- Find creative solutions within tight limitations
|
|
147
|
+
- Identify minimum viable approach
|
|
148
|
+
- Discover innovative workarounds and optimizations
|
|
149
|
+
|
|
150
|
+
## Process Control
|
|
151
|
+
|
|
152
|
+
**Proceed / No Further Actions**
|
|
153
|
+
|
|
154
|
+
- Acknowledge choice to finalize current work
|
|
155
|
+
- Accept output as-is or move to next step
|
|
156
|
+
- Prepare to continue without additional elicitation
|