A project tracker where answering the gate is the dispatch

Decisions for the human were sentences buried in files

Every decision that needed human eyes arrived as a half-flagged sentence somewhere in a repo — a ten-minute hunt to reach a ten-second call. The fix had to be structural: one fixed surface, one fixed format, and the decision buttons attached.

A Phase Zero pack before any product code

Twelve task packets, a status machine, a breadcrumb after every session, and 32 logged decisions define the project before the module's first line of code. A feature run is seven declared steps — brainstorm, staging, plan, execute, code-review, verify, finish — three of them gated on a human.

The workflow encodes the superpowers discipline

The steps carry the skill set the fleet already works by — brainstorming, writing-plans, subagent-driven-development, verification-before-completion — as data a dispatcher reads, not prose an agent is trusted to remember. Each step is a one-shot agent session, and each step's artifact is the next step's input.

A front end where the human gate is the whole point

A gate is a walk: one question at a time, option cards with one recommended and why, always a write-in, Mark for revision or Confirm, then a summary whose two buttons are Dispatch and Send for revision. Built from a Claude Design handoff through a fidelity contract — 54 interactive elements classified, 22 gaps ruled one line each — so nothing ships that looks functional and isn't.

A poller turns the answer into an agent session

A Hermes cron poller claims the answered record on an idempotent key — a dispatch stamp plus an exclusive lock, so a double-click cannot double-run — probes the claude login before spending anything, then writes the brief with the human's answers verbatim and spawns the session detached. A dead login token becomes a state on the record — needs-login, with a Telegram notice and a Retry button — rather than a silent failure.