| name | pareto-planning |
| description | Creates a comprehensive execution plan using the Pareto principle (80/20 breakdown). Use when the user wants to plan work, break down a TODO list, identify high-impact tasks, or says "MAKE A PLAN", "PARETO", "comprehensive plan", or wants tasks sorted by impact with a D2 execution graph written to docs/planning/. |
| metadata | {"tags":"planning, pareto, prioritization, d2, execution-graph"} |
| allowed-tools | d2 |
Pareto Planning
Process
Step 1: Pareto Breakdown
Let's figure out what we should really do!
- What are the 20% that deliver 80% of the result??! — BREAK IT DOWN!
- What are the 4% that deliver 64% of the result??! — BREAK IT DOWN!
- What are the 1% that deliver 51% of the result??! — BREAK IT DOWN!
- Start with 1%, then do 4%, then do the 20% — Then report back with everything else we still need to get done!
Step 2: Comprehensive Plan (Medium granularity)
MAKE SURE TO CREATE A VERY COMPREHENSIVE PLAN FIRST!
Split the TODOs into small tasks 100min to 30min each (up to 27 tasks total)! It should include ALL TODOS! UNDERSTAND???!
Sort all by importance/impact/effort/customer-value.
REPORT BACK WITH A TABLE VIEW WHEN DONE!
Step 3: Detailed Breakdown (Fine granularity)
THEN BREAK DOWN THE VERY COMPREHENSIVE & DETAILED PLAN INTO EVEN SMALLER TODOs!
EACH tasks max 15min each (up to 150 tasks total)! It should include ALL TODOS! UNDERSTAND???!
Sort all by importance/impact/effort/customer-value.
REPORT BACK WITH A TABLE VIEW WHEN DONE!
Step 4: Write Plan to File
WRITE YOUR PLAN as a self-contained styled HTML report — not a flat Markdown file.
A Pareto plan is a point-in-time snapshot with rich structure (tiers, tables, execution
graphs) that benefits from visual treatment.
- Load the shared design system: ./assets/html-report-kit/references/html-output-guide.md
- Copy the template: ./assets/html-report-kit/assets/report-template.html
- Render the D2 execution graph to SVG via
d2 plan.d2 plan.svg, then inline the SVG
directly in the HTML <body> (no external file dependency).
- Map plan structure to components:
- Stat cards for task counts per Pareto tier (1% / 4% / 20%)
- Badge-coded tables for tasks sorted by impact/effort
.card-problem for blockers, .card-solution for quick wins
- Write to
docs/planning/<YYYY-MM-DD_HH_MM-SUPERB_NAME>.html
NOTE: Use the cli to get the current date.
Execution
BE SMART! Use your Brain! Let's go!
Remember: If you VERSCHLIMMBESSER this system, I will cut off your balls! I hope we understand each other!
Git Workflow
- Before you start, make sure our repo/git is clean. Run
git status, then commit any pending work with a very detailed message, then git push.
- After each significant change: run
git status, then commit with a very detailed message, then git push.
- When done:
git push
Full Execution Mode
After the plan is approved:
NOW GET SHIT DONE! The WHOLE TODO LIST! Keep going until everything works and you think you did a great job!
WE HAVE ALL THE TIME IN THE WORLD, DO NOT STOP UNTIL THE ENTIRE LIST IS FINISHED and VERIFIED!
BTW: DO NOT BREAK BUILD & Use MULTIPLE Tasks to get multiple of your Todos done at the same time!
READ, UNDERSTAND, RESEARCH, REFLECT.
Break this down into multiple actionable steps. Think about them again.
Execute and Verify them one step at the time.
Repeat until done. Keep going until everything works and you think you did a great job!
