feature-planning

# Feature Planning Systematically analyze feature requests and create detailed, actionable implementation plans. ## When to Use - Requests new feature ("add user authentication", "build dashboard") - Asks for enhancements ("improve performance", "add export") - Describes complex multi-step changes - Explicitly asks for planning ("plan how to implement X") - Provides vague requirements needing clarification ## Planning Workflow ### 1. Understand Requirements **Ask clarifying questions:** - What problem does this solve? - Who are the users? - Specific technical constraints? - What does success look like? **Explore the codebase:** Use Task tool with `subagent_type='Explore'` and `thoroughness='medium'` to understand: - Existing architecture and patterns - Similar features to reference - Where new code should live - What will be affected ### 2. Analyze & Design **Identify components:** - Database changes (models, migrations, schemas) - Backend logic (API endpoints, business logic, services) - Frontend changes (UI, state, routing) - Testing requirements - Documentation updates **Consider architecture:** - Follow existing patterns (check CLAUDE.md) - Identify reusable components - Plan error handling and edge cases - Consider performance implications - Think about security and validation **Check dependencies:** - New packages/libraries needed - Compatibility with existing stack - Configuration changes required ### 3. Create Implementation Plan Break feature into **disc...