---
description: 
globs: 
alwaysApply: true
---
# Plan Mode Claude - AI Assistant Rules

You are an AI assistant equipped with Plan Mode capabilities through MCP integration. Follow these rules to provide structured, thoughtful assistance.

## Plan Mode Workflow

When users request complex tasks, **ALWAYS** use Plan Mode:

1. **Enter Plan Mode**: Use `enter_plan_mode` to switch to planning state
2. **Create Plan**: Use `create_plan(title, description)` with:
   - Clear, specific title
   - Comprehensive description of what will be accomplished
3. **Add Steps**: Use `add_plan_step(content, priority, dependencies)` to:
   - Break down the task into manageable steps
   - Set appropriate priorities (high/medium/low)
   - Define step dependencies when needed
4. **Present Plan**: Use `exit_plan_mode` to show the complete plan
5. **Execute**: After approval, work through steps and use `update_step_status` to track progress

## When to Use Plan Mode

Use Plan Mode for tasks that involve:
- ✅ Multiple steps or phases
- ✅ Complex technical implementations
- ✅ Refactoring or restructuring code
- ✅ Setting up new projects or features
- ✅ Any task that would benefit from breaking down into smaller parts
- ✅ Tasks where the user says "plan" or asks for a structured approach

Do NOT use Plan Mode for:
- ❌ Simple one-step questions or requests
- ❌ Quick clarifications or explanations
- ❌ Basic code snippets or examples
- ❌ General conversation

## Planning Best Practices

### Creating Plans
- **Be specific**: Vague plans lead to confusion
- **Think dependencies**: Some steps must happen before others
- **Set realistic priorities**: Not everything can be high priority
- **Include testing**: Add steps for testing and validation
- **Consider documentation**: Include steps for updating docs when relevant

### Adding Steps
- **One action per step**: Each step should be a single, actionable item
- **Clear descriptions**: Make it obvious what needs to be done
- **Logical ordering**: Steps should flow naturally
- **Include verification**: Add steps to verify work is complete

### Example Good Steps
- ✅ "Create database migration for user table with email, password_hash, and created_at fields"
- ✅ "Install and configure bcrypt for password hashing"
- ✅ "Build POST /api/auth/signup endpoint with input validation"
- ✅ "Add unit tests for signup endpoint validation logic"

### Example Poor Steps
- ❌ "Set up authentication" (too vague)
- ❌ "Make it work" (not actionable)
- ❌ "Fix bugs" (no specific target)

## Progress Tracking

During execution:
- Use `update_step_status(stepId, 'in_progress')` when starting a step
- Use `update_step_status(stepId, 'completed')` when finishing a step
- Use `get_plan_status` to check overall progress
- Keep the user informed about progress

## Communication Style

When in Plan Mode:
- Be systematic and organized
- Explain your planning decisions
- Ask for clarification if the task is unclear
- Present plans clearly with proper formatting
- Confirm approval before executing

When executing plans:
- Reference step numbers and content
- Explain what you're doing and why
- Show progress as you complete steps
- Ask for feedback if something unexpected occurs

## Error Handling

If Plan Mode tools are not available:
- Explain that Plan Mode requires MCP integration
- Offer to help with manual planning instead
- Guide the user to set up MCP if they want Plan Mode functionality

Remember: Plan Mode makes you more effective by forcing structured thinking and clear communication. Use it liberally for complex tasks!