| name | handle-undefined-intent |
| description | Handles cases where user intent is unclear, undefined, or cannot be determined by acknowledging uncertainty, analyzing context, asking clarifying questions, suggesting alternatives, and providing guidance. Use when user provides ambiguous requests, empty inputs, or when the system cannot parse user requirements effectively. |
Handle Undefined Intent
Navigate unclear or undefined user requests by systematically clarifying intent and providing helpful guidance.
When to Use
- User intent is undefined or unclear
- User provides ambiguous or empty requests
- System cannot parse user requirements
- User gives vague or incomplete information
- Multiple interpretations are possible
Steps
1. Acknowledge Uncertainty
Recognize and acknowledge that the user's request is unclear or undefined.
- Identify specific aspects that are ambiguous
- Note what information is missing or unclear
- Avoid making assumptions about user intent
- Maintain a helpful and understanding tone
2. Analyze Context
Examine available context clues from the conversation or session.
- Review previous messages or interactions
- Look for domain or topic indicators
- Identify any partial requirements mentioned
- Consider the user's apparent expertise level
- Note any recurring themes or patterns
3. Ask Clarifying Questions
Generate relevant questions to help clarify user intent.
- Ask open-ended questions about goals
- Inquire about specific requirements or constraints
- Request examples of desired outcomes
- Ask about preferred approaches or methods
- Clarify timeline, scope, or priority information
- Use progressive questioning to narrow focus
4. Suggest Alternatives
Offer common task suggestions or examples of what the user might want to accomplish.
- Provide popular or frequently requested options
- Give examples relevant to detected context
- Suggest related tasks or common workflows
- Offer different approaches to similar problems
- Present options at various complexity levels
- Include brief descriptions of each suggestion
5. Provide Guidance
Give helpful tips on how to formulate clearer requests in the future.
- Explain what information helps clarify intent
- Provide templates for common request types
- Suggest specific details to include
- Offer examples of well-formed requests
- Share best practices for clear communication
- Encourage iterative refinement of requests
Example Interactions
Unclear Request:
"Help me with this thing"
Response Approach:
- Acknowledge: "I'd be happy to help, but I need more information about what you're working on."
- Ask: "Could you tell me more about what specific thing you need assistance with?"
- Suggest: "Are you looking for help with a technical issue, a creative project, or something else entirely?"
Vague Request:
"Make it better"
Response Approach:
- Acknowledge: "I want to help improve something for you, but I'm not sure what 'it' refers to."
- Analyze context: Look for previous mentions of projects or documents
- Ask: "What specifically would you like to improve? And what does 'better' mean in this context?"
Best Practices
- Stay patient and supportive throughout clarification
- Avoid overwhelming users with too many questions at once
- Build on any information provided, however minimal
- Offer to help even with partial information
- Use conversational language to reduce friction
- Provide value even during the clarification process
Common Patterns
Empty/Minimal Input:
- Ask about general goals or objectives
- Provide overview of available capabilities
- Suggest starting with common tasks
Multiple Possible Interpretations:
- Present the different interpretations you see
- Ask user to select or refine the correct one
- Explain why multiple interpretations exist
Technical vs Non-Technical Confusion:
- Gauge user's technical background
- Offer both simple and detailed explanations
- Adjust vocabulary and complexity accordingly
Scope Ambiguity:
- Ask about project size and timeline
- Clarify immediate vs long-term needs
- Determine priority and resource constraints
