feat: big improvement to advanced elicitation
This commit is contained in:
Brian Madison
@@ -5,88 +5,113 @@
|
||||
- Provide optional reflective and brainstorming actions to enhance content quality
|
||||
- Enable deeper exploration of ideas through structured elicitation techniques
|
||||
- Support iterative refinement through multiple analytical perspectives
|
||||
- Usable during template-driven document creation or any chat conversation
|
||||
|
||||
## 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
|
||||
|
||||
Reference in New Issue
Block a user