T-minus, the control room for people shipping too many things at once. I run 20+ hackathon and contest entries at the same time. Every one has a different deadline, a different rubric, a different set of deliverables and a different thing blocking it. The tools that exist all assume you are working on one project: a kanban board does not know a deadline is nine hours out, a calendar does not know the demo video is the only thing missing, and neither can tell me which entry to abandon tonight so the other four survive. So I kept rebuilding it badly in markdown files. T-minus is that file, designed properly. Nine screens: a Launch board ranking every live entry by time to death, Entry detail splitting required from bonus deliverables, Deliverable detail, a Rubric map showing how many points sit inside one unstarted task, Tonight (one task, one countdown, everything else stripped off the screen), Blockers sorted by how many entries each one frees, a Submission gate, a Ledger of what scored and what paid, and an Intake that turns a challenge URL into a deliverables checklist. Every screen was generated through the Flowstep MCP server from Claude Code. I wrote the design system once, nine hex tokens each with a rule about where it is allowed to appear, Inter for UI and JetBrains Mono for every countdown and figure, pushed it with update-design-guidelines, and every screen inherited it. That is why the nine screens look like one product instead of nine prompts. The interface is near monochrome on purpose. The only saturated color is #FF4D2E, reserved for countdowns under 24 hours, at-risk rows and primary actions. If something is orange, it is about to fail. Everything else stays quiet. The Submission gate is the honest one. It refuses to say ready until each check has produced real output, which is the rule I hold my own projects to and break constantly. Building it in Flowstep is the closest I have ever come to shipping it. Prototype: https://app.flowstep.ai/file?activeFileId=18d339fd-fb9a-46fd-8ac1-ad842eac8c8c