Runbook Zero
Generates the first draft of a runbook by reading your deploy scripts. Built for Cold Open — build a tool that helps someone do the very first step of a task they have been avoiding. Script parsing and markdown output. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Runbook Zero — main view
Runbook Zero — result state
On the clock
What shipped, what didn't
Completed in time
Script parsing and markdown output.
Unfinished / faked
No validation that the runbook is correct.
Obstacles
Underestimated the parsing work. Cut a whole feature to protect the demo.
Lessons learned
Test the demo path once at minute 25. I didn't, and it showed.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Runbook Zero data model before writing any interface code. Full prompt log is in the repository under /prompts.
Fairness
Disclosures
Declared by the builder at submission time, visible to judges before scoring.
Reused a personal utility file for date formatting (~40 lines), linked in the repo README.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Elena Voss
VP of Engineering, Harbor Compute
The concept is interesting but not enough shipped to evaluate it fairly. Scope down harder next time — pick one screen and finish it.
Hana Kobayashi
Principal Research Engineer, Independent
The concept is interesting but not enough shipped to evaluate it fairly. Scope down harder next time — pick one screen and finish it.
Tomas Eriksen
Developer Advocate, Independent
The concept is interesting but not enough shipped to evaluate it fairly. Scope down harder next time — pick one screen and finish it.
Discussion
0 comments
No comments yet.