# Elicitation Methods for Advanced Content Enhancement This file contains structured elicitation methods used by the advanced-elicitation task to enhance content quality through multiple analytical perspectives. ## Core Methods (Always Available) ### Expand or Contract for Audience **Purpose**: Adjust content depth and complexity for different audiences **Execution**: - Identify the current audience level - Suggest expanding for more technical audiences or contracting for less technical - Provide specific recommendations for what to add/remove - Consider different stakeholder perspectives ### Critique and Refine **Purpose**: Systematic critique to identify improvement opportunities **Execution**: - Analyze content for clarity, completeness, and accuracy - Identify gaps, inconsistencies, or unclear areas - Suggest specific refinements and improvements - Consider alternative approaches or phrasings ### Identify Potential Risks **Purpose**: Proactive risk identification and mitigation **Execution**: - Analyze content for potential implementation risks - Identify dependencies that could cause problems - Consider what could go wrong with the proposed approach - Suggest risk mitigation strategies ### Assess Alignment with Goals **Purpose**: Ensure content aligns with stated objectives **Execution**: - Review content against stated goals and objectives - Identify any misalignment or scope creep - Suggest adjustments to improve goal alignment - Consider whether objectives need refinement ## Technical Content Methods ### Tree of Thoughts **Purpose**: Systematic exploration of multiple solution paths **Execution**: - Generate 3-4 different approaches to the technical challenge - Explore each path systematically with pros/cons - Identify the most promising paths forward - Consider hybrid approaches combining best elements ### ReWOO (Reasoning WithOut Observation) **Purpose**: Step back and reason about the problem without getting lost in details **Execution**: - Abstract the core problem from implementation details - Reason about fundamental principles and constraints - Generate high-level solution approaches - Return to specifics with clearer direction ### Meta-Prompting **Purpose**: Improve prompts and instructions for AI systems **Execution**: - Analyze existing prompts for clarity and completeness - Identify ambiguities that could lead to misinterpretation - Suggest improvements for more effective AI interaction - Consider edge cases and error handling ## User-Facing Content Methods ### Agile Team Perspective **Purpose**: Review content from various agile team member perspectives **Execution**: - **Product Owner**: Does this deliver user value? Are requirements clear? - **Developer**: Is this implementable? Are technical details sufficient? - **QA**: How will this be tested? What are the acceptance criteria? - **Scrum Master**: Does this fit our process? Any blockers identified? ### Stakeholder Roundtable **Purpose**: Simulate feedback from different project stakeholders **Execution**: - **End Users**: How does this impact user experience? - **Business Stakeholders**: Does this align with business objectives? - **Technical Leadership**: Are architectural concerns addressed? - **Support Team**: How will this affect support and maintenance? ## Creative Content Methods ### Innovation Tournament **Purpose**: Generate multiple creative alternatives and compete them **Execution**: - Generate 4-5 alternative creative approaches - Set up criteria for evaluation (feasibility, impact, originality) - "Compete" approaches against each other - Select winning elements from multiple approaches ### Escape Room Challenge **Purpose**: Find creative solutions to constraints and limitations **Execution**: - Identify all constraints and limitations in current approach - Challenge each constraint - is it really necessary? - Find creative ways to work within or around constraints - Generate "escape routes" from apparent dead ends ## Strategic Content Methods ### Red Team vs Blue Team **Purpose**: Adversarial analysis to stress-test ideas **Execution**: - **Blue Team**: Defend and optimize the current approach - **Red Team**: Attack and find flaws in the approach - Identify strongest attacks and best defenses - Synthesize learnings into improved approach ### Hindsight Reflection **Purpose**: Imagine future perspectives to identify current blind spots **Execution**: - Imagine this project 6 months from now - what went wrong? - What would future-you wish current-you had considered? - What assumptions might prove incorrect over time? - What would a post-mortem reveal about current decisions? ## Analysis and Research Methods ### Five Whys Deep Dive **Purpose**: Get to root causes and fundamental drivers **Execution**: - Start with surface-level statement or requirement - Ask "why" five times in succession - Explore different branches of causation - Identify root causes and fundamental needs ### Assumption Mapping **Purpose**: Make implicit assumptions explicit and test them **Execution**: - Identify all assumptions underlying the content - Categorize assumptions by risk level and testability - Suggest ways to validate critical assumptions - Consider what happens if key assumptions are wrong ### Evidence Assessment **Purpose**: Evaluate the quality and sufficiency of supporting evidence **Execution**: - Identify claims that need supporting evidence - Assess quality of current evidence - Identify gaps where stronger evidence is needed - Suggest additional research or validation needed ## Process and Implementation Methods ### Implementation Sequence Analysis **Purpose**: Optimize the order and dependencies of implementation steps **Execution**: - Map out current proposed sequence - Identify dependencies and potential bottlenecks - Suggest alternative sequences that might be more efficient - Consider parallel workstreams and resource optimization ### Change Impact Analysis **Purpose**: Understand ripple effects of proposed changes **Execution**: - Map all systems, processes, and people affected by changes - Assess magnitude of impact on each area - Identify potential resistance or adoption challenges - Suggest change management strategies ### Resource Reality Check **Purpose**: Ensure proposals are realistic given available resources **Execution**: - Estimate realistic resource requirements (time, people, budget) - Compare against available resources - Identify potential resource constraints or bottlenecks - Suggest phasing or prioritization strategies ## Communication and Documentation Methods ### Clarity Audit **Purpose**: Ensure content is clear and unambiguous **Execution**: - Identify jargon, technical terms, or unclear language - Look for ambiguous statements that could be misinterpreted - Suggest clearer, more precise language - Consider different reading levels and backgrounds ### Completeness Check **Purpose**: Ensure all necessary information is included **Execution**: - Create checklist of information typically needed for this content type - Identify any missing pieces - Assess whether level of detail is appropriate - Suggest additional information that would be helpful ### Action Orientation Review **Purpose**: Ensure content leads to clear, actionable next steps **Execution**: - Identify what actions readers should take after consuming content - Assess whether these actions are clear and achievable - Suggest more specific or actionable language - Consider what tools or resources might be needed for action ## Usage Guidelines ### Method Selection Criteria - **Technical Content**: Prefer Tree of Thoughts, ReWOO, Meta-Prompting - **User Stories**: Use Agile Team Perspective, Stakeholder Roundtable - **Strategic Decisions**: Apply Red Team vs Blue Team, Hindsight Reflection - **Creative Challenges**: Use Innovation Tournament, Escape Room Challenge - **Complex Analysis**: Apply Five Whys, Assumption Mapping, Evidence Assessment ### Execution Best Practices - Always explain which perspective you're taking - Be specific and actionable in suggestions - Focus on the most impactful improvements - Consider the broader context and constraints - Maintain focus on the original objectives ### Integration with Workflow - Methods work best when applied iteratively - Multiple methods can be combined for deeper analysis - Results should feed back into content improvement - Track which methods prove most valuable for different content types