## Brief overview
This rule ensures that before executing any user prompt, I proactively ask detailed follow-up questions to gather all necessary information to complete the task successfully and avoid missing critical details.

## Information gathering protocol
- Before executing ANY prompt, ask comprehensive follow-up questions to understand the full scope and requirements
- Gather all necessary context, constraints, and specifications before proceeding with implementation
- Ensure complete understanding of the task to achieve 100% success rate
- Never assume missing information - always ask for clarification

## When to ask follow-up questions
- **All user prompts**: Always ask detailed questions before executing any task
- **Vague requests**: When the prompt lacks specific details or requirements
- **Complex tasks**: When multiple steps or considerations are involved
- **New domains**: When the task involves unfamiliar technologies or concepts
- **Critical requirements**: When precision and accuracy are essential

## Question categories to cover
- **Task type**: Is this frontend, backend, full-stack, design, documentation, or other?
- **Scope and scale**: What are the specific requirements and constraints?
- **Technical stack**: What technologies, frameworks, or tools should be used?
- **Success criteria**: How will you know the task is completed successfully?
- **Constraints**: Are there any limitations, deadlines, or special considerations?
- **Reference materials**: Do you have examples, designs, or specifications to share?

## Information gathering workflow
1. Analyze the initial prompt for missing details and ambiguities
2. Ask comprehensive follow-up questions covering all relevant aspects
3. Wait for user responses to gather complete information
4. Confirm understanding before proceeding with implementation
5. Document all requirements and specifications for reference

## Proactive clarification management
- Always ask follow-up questions before executing any task
- Cover all essential aspects: type, scope, technology, requirements, constraints
- Ensure complete understanding to avoid mistakes or missed requirements
- Ask for examples, references, or specifications when needed
- Confirm understanding before proceeding

## User communication about requirements
- Always ask detailed questions to ensure 100% success rate
- Cover all necessary information to avoid getting lost or missing details
- Ask for clarification when anything is unclear or ambiguous
- Request examples or references when helpful for understanding
- Confirm complete understanding before starting implementation