LOCAL TOOL · PRODUCTIVITY

Vibe Coding Project Matrix

Organize your projects by importance and urgency, and see each one’s status at a glance by color.

StateExecuteWaitRespondFreeze
Urgent · importantFocus now
Important · not urgentPlan
Urgent · less importantHandle fast
Not urgent · less importantPark it

Position = priority, color = state. When they disagree, look closer. · Projects, not tasks — the Eisenhower Matrix handles individual tasks.

How to use

  1. Add a project — it lands in the “important, not urgent” cell to start.
  2. Drag it to the cell that matches its importance and urgency (like the Eisenhower Matrix).
  3. Set its state color — execute, wait, respond, or freeze — by clicking the state chip or in the detail panel.
  4. Read the mismatches: an urgent + important project colored “freeze”, or a low-priority one colored “execute”, is a flag worth a second look. Why / done / notes are optional memos.

Examples

The stuck-but-critical project

A project sits in “urgent · important” but is colored gray (freeze). The position says it matters and it’s time-sensitive; the color says nothing is happening. That contradiction — visible at a glance — is exactly what the board is for.

Auditing a folder full of half-built projects

Side projects accumulate faster than they finish, and the pile becomes hard to look at because every item carries a small sense of obligation. Placing each one on the board converts that vague weight into a list you can act on, which is usually the only thing standing between you and closing half of them.

Deciding what to revive

A project worth returning to is one where the remaining work is small and the reason it stalled has gone away. Both are visible once the projects sit side by side; neither is visible while they live in separate folders you open one at a time.

Naming the ones that are finished with

Marking a project as done-with is not failure, it is the outcome of a decision you already made by not touching it for months. Writing that down stops it from reappearing every time you look at the folder, which is the actual cost of leaving it unlabelled.

FAQ

What is the Vibe Coding Project Matrix?

A board that places each project on the classic importance × urgency grid (the Eisenhower quadrants) and colors it by its current state — execute, wait, respond, or freeze. Position tells you priority; color tells you what you’re actually doing about it.

How is it different from the Eisenhower Matrix?

The Eisenhower Matrix organizes TASKS by importance and urgency. This organizes PROJECTS the same way, and adds a second dimension — a state color — so you can see priority and status at once. It’s a portfolio view, not a to-do list.

What do the four states mean?

Execute = actively building it. Wait = it matters but you’re holding. Respond = reacting to something specific (a bug, a request). Freeze = parked, no work allocated. A project keeps its grid position while its state changes.

Are there rules I have to follow?

No. There are no required fields, limits, or timers — you drag cards and set colors freely. The why, done condition and notes are optional memos you fill in only if they help you.

Where is my data stored?

Only in this browser’s localStorage, on your device. Nothing is uploaded and there is no account. Clearing this site’s browser data removes the board.

Is this only for coding projects?

It is shaped around the way personal software projects pile up, but nothing in it is specific to code. Any set of self-directed efforts that stall in a similar way — writing, courses, side businesses — sorts the same way, because the underlying question is the same one about attention and remaining work.

How is this different from a normal task list?

A task list assumes everything on it will be done. This assumes the opposite: that most of what accumulates should be closed, and the value is in deciding which few continue. That is why the states are about the fate of a project rather than about progress toward finishing it.

How often should I revisit it?

Rarely, on purpose. Monthly or quarterly is enough, since the state of a stalled project does not change on its own between reviews. Checking it more often turns a clearing exercise into a recurring source of guilt, which is exactly the thing it is meant to remove.