enhanced-planning

# Enhanced Planning Skill

When planning non-trivial features, use this enhanced methodology instead of basic exploration.

## When to Use

Automatically apply this skill when:
- User requests a new feature that touches multiple files
- User asks to "plan" something complex
- You're about to enter plan mode for anything beyond a simple fix

## Enhanced Planning Workflow

### Phase 1: Parallel Research (run simultaneously)

Launch 3 research tasks in parallel using the Task tool:

```
Task 1: Codebase Pattern Analysis
- Scan ARCHITECTURE.md, README.md, CONTRIBUTING.md, CLAUDE.md
- Find similar implementations in the codebase (use Grep/Glob)
- Identify naming conventions, file organization patterns
- Check for existing utilities/helpers that could be reused
- Look at test patterns for similar features

Task 2: External Best Practices
- Use WebSearch for "[technology] [feature] best practices 2025"
- Use WebFetch to get official framework documentation
- Find examples from well-regarded open source projects
- Identify security considerations and common pitfalls

Task 3: Dependency/Framework Docs
- Identify which frameworks/libraries will be used
- Fetch current documentation for those dependencies
- Check for version-specific constraints or deprecations
- Find recommended patterns from official sources
```

### Phase 2: User Flow Analysis

After research completes, systematically analyze:

**Happy Paths:**
- Primary user journey from start to finish
- All entry points to the feature
- Success states and confirmations

**Edge Cases & Error States:**
- What happens when X fails?
- Network errors, timeouts, rate limits
- Invalid input, missing data
- Permission denied scenarios
- Concurrent user actions

**User Variations:**
- First-time vs returning user
- Different user roles/permissions
- Mobile vs desktop considerations
- Offline/slow connection handling

**State Management:**
- What state needs to persist?
- How does user resume if interrupted?
- Cleanup on cancellat