Three tools, one plan

The same example plan — “Refactor the billing module” — seen through each tool, so the difference is obvious. (Numbers are illustrative.)

/ork:visualize-plan· what does my code change do?
/dataviz· make my numbers a good chart
playground· let me fiddle & copy a result
/ork:visualize-plan

The plan itself

Job: turn a code change into a review picture — files, risk, order. It is not about charts or interactivity.

PLAN: Refactor billing module  ·  3 phases  ·  4 files  ·  +375 −175 lines  ·  Risk: Medium
Order: ① pricing-engine  →  ② invoice-service  →  ③ checkout-api + webhooks
[M]api/checkout.py+180 −40
[M]services/invoice.py+90 −120
[M]core/pricing.py+45 −10
[A]webhooks/billing.py+60 −5
/dataviz

The impact numbers, drawn right

Job: take numbers → a correct, colorblind-safe chart. Same data as above, but now it’s a chart — and the colors are the real dataviz palette that passed the validator.

Lines changed per component
Direct value labels on every bar — the accessibility relief the validator required.
Added Removed
$ node validate_palette.js "#2a78d6,#1baf7a,#eda100,…" --mode light → ALL CHECKS PASS · exit 0
playground

Now make it operable

Job: wrap it in something you can fiddle with and copy a result out of. Drag the slider — the chart above dims to what’s left, and the prompt rewrites live.

Medium

How they combine: visualize-plan draws the plan → the chart inside it is made the /dataviz way (validated colors) → the whole thing is a playground you can operate. Three jobs, one screen. dataviz isn’t a rival to visualize-plan — it’s the chart specialist visualize-plan can hand its numbers to.