ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: WIP create-docv2

Browse Source
This commit is contained in:
Brian Madison
2025-07-06 00:10:00 -05:00
parent be9453f234
commit c107af0598
16 changed files with 4064 additions and 1916 deletions
Download Patch File Download Diff File Expand all files Collapse all files

525
dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt vendored
View File

@@ -104,7 +104,7 @@ commands:
- exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
dependencies:
tasks:
- brainstorming-techniques
- facilitate-brainstorming-session
- create-deep-research-prompt
- create-doc
- advanced-elicitation
@@ -113,8 +113,10 @@ dependencies:
- project-brief-tmpl
- market-research-tmpl
- competitor-analysis-tmpl
- brainstorming-output-tmpl
data:
- bmad-kb
- brainstorming-techniques
utils:
- template-format
```
@@ -443,246 +445,144 @@ dependencies:
```
==================== END: agents#game-sm ====================
==================== START: tasks#brainstorming-techniques ====================
# Brainstorming Techniques Task
==================== START: tasks#facilitate-brainstorming-session ====================
---
docOutputLocation: docs/brainstorming-session-results.md
template: brainstorming-output-tmpl
---
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.
# Facilitate Brainstorming Session Task
Facilitate interactive brainstorming sessions with users. Be creative and adaptive in applying techniques.
## Process
### 1. Session Setup
### Step 1: Session Setup
[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
Ask 4 context questions (don't preview what happens next):
1. **Establish Context**
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)
- Understand the problem space or opportunity area
- Identify any constraints or parameters
- Determine session goals (divergent exploration vs. focused ideation)
### Step 2: Present Approach Options
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)
After getting answers to Step 1, present 4 approach options (numbered):
### 2. Core Brainstorming Techniques
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)
#### Creative Expansion Techniques
### Step 3: Execute Techniques Interactively
1. **"What If" Scenarios**
[[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
**KEY PRINCIPLES:**
- 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?
- **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
2. **Analogical Thinking**
[[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
**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).
- "How might this work like [X] but for [Y]?"
- Nature-inspired solutions (biomimicry)
- Cross-industry pattern matching
- Historical precedent analysis
**Technique Execution:**
3. **Reversal/Inversion**
[[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
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
- 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
**Output Capture (if requested):**
For each technique used, capture:
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?
- Technique name and duration
- Key ideas generated by user
- Insights and patterns identified
- User's reflections on the process
#### Structured Ideation Frameworks
### Step 4: Session Flow
1. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
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
- **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?
### Step 5: Document Output (if requested)
2. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]]
Generate structured document with these sections:
- 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
**Executive Summary**
3. **Mind Mapping**
[[LLM: Create text-based mind maps with clear hierarchical structure.]]
- Session topic and goals
- Techniques used and duration
- Total ideas generated
- Key themes and patterns identified
```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
```
**Technique Sections** (for each technique used)
#### Collaborative Techniques
- Technique name and description
- Ideas generated (user's own words)
- Insights discovered
- Notable connections or patterns
1. **"Yes, And..." Building**
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
**Idea Categorization**
- Accept the premise of each idea
- Add to it with "Yes, and..."
- Build chains of connected ideas
- Explore tangents freely
- **Immediate Opportunities** - Ready to implement now
- **Future Innovations** - Requires development/research
- **Moonshots** - Ambitious, transformative concepts
- **Insights & Learnings** - Key realizations from session
2. **Brainwriting/Round Robin**
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
**Action Planning**
- Generate ideas from stakeholder perspectives
- Build on previous ideas in rounds
- Combine unrelated ideas
- Cross-pollinate concepts
- Top 3 priority ideas with rationale
- Next steps for each priority
- Resources/research needed
- Timeline considerations
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
**Reflection & Follow-up**
#### 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
- What worked well in this session
- Areas for further exploration
- Recommended follow-up techniques
- Suggested research areas
- Questions that emerged for future sessions
## Important Notes
## Key Principles
- Maintain energy and momentum throughout the session
- Defer judgment - all ideas are valid during generation
- Quantity leads to quality - aim for many ideas
- **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 - even "silly" ideas can spark breakthroughs
- Take breaks if energy flags
- End with clear next actions
==================== END: tasks#brainstorming-techniques ====================
- 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
==================== END: tasks#facilitate-brainstorming-session ====================
==================== START: tasks#create-deep-research-prompt ====================
# Create Deep Research Prompt Task
@@ -2311,6 +2211,158 @@ These replace the standard elicitation options when working on market research d
These replace the standard elicitation options when working on competitive analysis documents.]]
==================== END: templates#competitor-analysis-tmpl ====================
==================== START: templates#brainstorming-output-tmpl ====================
---
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*
==================== END: templates#brainstorming-output-tmpl ====================
==================== START: data#bmad-kb ====================
# Game Development BMad Knowledge Base
@@ -2568,6 +2620,45 @@ game-project/
This knowledge base provides the foundation for effective game development using the BMad-Method framework with specialized focus on 2D game creation using Phaser 3 and TypeScript.
==================== END: data#bmad-kb ====================
==================== START: data#brainstorming-techniques ====================
# 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
==================== END: data#brainstorming-techniques ====================
==================== START: utils#template-format ====================
# Template Format Conventions
@@ -3224,14 +3315,10 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
### 1. Check Plan Existence
[[LLM: When any agent starts or task begins, check if a workflow plan exists]]
```
Check for workflow plan:
1. Look for docs/workflow-plan.md (default location)
2. Check core-config.yaml for custom plan location
3. Return plan status (exists/not exists)
```
2. Return plan status to user (exists/not exists) - if not exists then HALT.
### 2. Parse Plan Status
@@ -3272,7 +3359,7 @@ Check for workflow plan:
**Warning Templates:**
```
```text
SEQUENCE WARNING:
The workflow plan shows you should complete "{expected_step}" next.
You're attempting to: "{requested_action}"
@@ -3306,7 +3393,7 @@ In flexible mode: Allow with confirmation
**For Agents (startup sequence)**:
```
```text
1. Check if plan exists using this utility
2. If exists:
- Parse current status
@@ -3317,7 +3404,7 @@ In flexible mode: Allow with confirmation
**For Tasks (pre-execution)**:
```
```text
1. Check if plan exists
2. If exists:
- Verify this task aligns with plan
@@ -3333,7 +3420,7 @@ In flexible mode: Allow with confirmation
[[LLM: Standard format for showing plan status]]
```
```text
📋 Workflow Plan Status
━━━━━━━━━━━━━━━━━━━━
Workflow: {workflow_name}
@@ -3386,7 +3473,7 @@ If user wants to abandon plan:
### Example 1: Agent Startup Check
```
```text
BMad Master starting...
[Check for plan]
@@ -3400,7 +3487,7 @@ Use *agent pm to switch, or *plan-status to see full progress.
### Example 2: Task Sequence Warning
```
```text
User: *task create-next-story
[Plan check triggered]
@@ -3416,7 +3503,7 @@ Would you like to:
### Example 3: Automatic Plan Update
```
```text
[After completing create-doc task for PRD]
✅ Plan Updated: Marked "Create PRD" as complete

143
dist/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.txt vendored
View File

@@ -1328,91 +1328,116 @@ Embedded knowledge (automatic):
- 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
## Usage Scenarios
### Scenario 1: Template Document Creation
After outputting a section during document creation:
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
### Scenario 2: General Chat Elicitation
User can request advanced elicitation on any agent output:
- User says "do advanced elicitation" or similar
- Agent selects 9 relevant methods for the context
- Same simple 0-9 selection process
## Task Instructions
### 1. Section Context and Review
### 1. Intelligent Method Selection
[[LLM: When invoked after outputting a section:
**Context Analysis**: Before presenting options, analyze:
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.")
- **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
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.")
**Method Selection Strategy**:
3. If the section contains multiple distinct items (like multiple components, multiple patterns, etc.), inform the user they can apply elicitation actions to:
1. **Always Include Core Methods** (choose 3-4):
- Expand or Contract for Audience
- Critique and Refine
- Identify Potential Risks
- Assess Alignment with Goals
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
3. **Always Include**: "Proceed / No Further Actions" as option 9
### 2. Section Context and Review
When invoked after outputting a section:
1. **Provide Context Summary**: Give a brief 1-2 sentence summary of what the user should look for in the section just presented
2. **Explain Visual Elements**: If the section contains diagrams, explain them briefly before offering elicitation options
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)
4. Then present the action list as specified below.]]
### 3. Present Elicitation Options
### 2. Ask for Review and Present Action List
**Review Request Process:**
[[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.]]
- 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
**Present the numbered list (0-9) with this exact format:**
**Action List Presentation Format:**
```text
**Advanced Reflective, Elicitation & Brainstorming Actions**
Choose an action (0-9 - 9 to bypass - HELP for explanation of these options):
**Advanced Elicitation Options**
Choose a number (0-8) or 9 to proceed:
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
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
```
### 2. Processing Guidelines
**Response Handling:**
**Do NOT show:**
- **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
- 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
### 4. Method Execution Framework
**After user selection from the list:**
**Execution Process:**
- 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
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
## Action Definitions
**Execution Guidelines:**
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.]]
- **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
==================== END: tasks#advanced-elicitation ====================
==================== START: tasks#create-deep-research-prompt ====================