Mission Control — a dependency-aware task board

A single-file, zero-dependency task board you drop into any project. Two owners (e.g. you vs your coding agent), each with one consolidated plate, plus a map view that draws the whole project as a transit map — one line per track, converging on a terminus (GO LIVE), each line's current bottleneck pulsing.

"Ready" is never stored — it's derived. Every task lists its deps; a task is blocked until all of them are done. Complete one and anything it unblocks animates into Up now.

No build. No framework. No npm install. It's one HTML file that runs from file://.

Grab it and go:

curl -O https://raw.githubusercontent.com/rockthemike712/mission-control-board/main/board.html
open board.html   # then edit the  block to make it yours

What it looks like

Tap any station and the map answers back — completing a task ripples through its dependents, and the 🔓 toast names exactly what just unblocked:

The whole project on one screen — one line per track, cross-track dependencies as connectors, everything converging on the GO LIVE terminus:

Each owner's plate: Up now (tap the ring to complete), then Waiting and Done. The Lines view — each track as a subway diagram; ⛓ chips jump to the blocker.

Light theme is built in (tap ◐):

The screenshots use the included examples/nabshift.seed.json — a scrubbed, real-world board. Your own board is whatever you put in the seed.

open board.html          # macOS
# or
xdg-open board.html      # Linux
# or serve it
npx serve .

Out of the box board.html shows a small demo project so you can click around. Then you make it yours by editing one thing: the seed.

Make it yours

Everything project-specific lives in a single JSON block near the bottom of board.html:

{ "config": {...}, "rev": 1, "tracks": [...], "tasks": [...] }

Edit that block, save, refresh. The engine above it (the , the map module, and the main ) is generic and never needs touching.

Two ways to work:

1. No build — copy board.html into your project, edit the inline seed by hand. Done.
2. Optional builder — keep your seed in its own file and inject it:

   node build.js my-project.seed.json > board.html
   

   Zero dependencies; purely a convenience fo