planning-frameworklisted

# Planning Framework ## When to Use Before starting ANY significant coding task: - New features (> 50 lines of code) - Refactoring existing components - Architectural changes - Debugging complex issues ## Musk's 5-Step Algorithm ### Step 1: Make Requirements Less Dumb **Question everything:** - Who requested this feature? Why? - What problem does it actually solve? - Is there a simpler way to achieve the same outcome? - What happens if we don't build this? **Portfolio Buddy 2 Example**: > **Request**: "Add sortable columns to metrics table" > > **Questions**: > - Why? Users want to find best/worst performing strategies quickly > - Simpler solution? Just default sort by Sharpe Ratio (most important metric) > - Alternative? Add "Top 3" and "Bottom 3" highlight sections > > **Decision**: Implemented full multi-column sorting via `useSorting` hook because: > - Different users care about different metrics (Sharpe vs Sortino vs Max DD) > - Sorting is O(n log n) - negligible for <100 strategies > - Reusable hook can be used in future tables ### Step 2: Delete the Part or Process **What can we eliminate?** - Remove features that serve no clear purpose - Cut unnecessary steps in workflows - Simplify data structures - Delete unused dependencies **Rule**: If you don't add back 10% of what you deleted, you didn't delete enough. **Portfolio Buddy 2 Example**: > **Discovery**: Recharts library (11.5KB) installed but never imported > > **Questions**: > - Is it used anywhere? NO - sea