plan-featurelisted

Follow CLAUDE.md rules. **Output file:** `docs/plan-features/{$ARGUMENTS.name}_FEATURE.md` (uppercase) ## Ultra Think Strategy Ultra think before each phase transition: - After exploration results: reflect on completeness before planning - Before writing spec: consider architecture, edge cases, future maintainability - After validation: ensure the plan is comprehensive and actionable --- ## 1. GATHER REQUIREMENTS Ask user for: - Detailed feature description - Mockups/screenshots if available - Business rules and edge cases - Integrations with existing features Do not proceed until requirements are clear. --- ## 1.5 CLARIFY DETAILS Use AskUserQuestion to clarify before exploration: ### Must clarify (if not specified) - Error messages for user-facing failures? - Default values for new fields? - Validation rules? - What triggers state changes? ### UX Decisions (if not specified) - What happens on success? (toast, redirect, refresh?) - What happens on error? - Confirmation dialogs needed? ### Permissions (if not specified) - Who can perform each action? - RLS policy rules? Do not proceed until critical details are clarified. --- ## 2. EXPLORE (PARALLEL) Launch agents based on feature scope (single message, parallel execution): | Need | Agent | Prompt | |------|-------|--------| | Backend | explore-codebase | "Find all [feature] related code in backend/ - entities, usecases, repos, handlers" | | Frontend | explore-codebase | "Find all [feature] related code in fr