One-Page Hack Spec

Fill every field. If you can't fill a field in a single sentence, the answer is "it's not clear enough yet" — go back to Phase 1 and tighten the itch.

Rules:

• No field may be left blank.
• "Demo moment" must be stage directions, not a concept.
• "What's in" is capped at 3 items. Not 4. Not "3 plus one small thing". Three.
• "What's out" must name the real temptations — the things you'd add if given a fifth hour.

---

Goal

One sentence. No jargon. What does this hack do for whom?

---

User

Who specifically benefits? Name a role, not an abstraction. "Backend engineer tuning Anthropic API costs" is a role; "developers" is not.

---

Demo moment

The single 60-second thing the judges will watch. Write it as stage directions.

Judge does: ____________________ Our system does: ____________________ Judge sees: ____________________

What's in (max 3)

1. ---

2. ---

3. ---

What's out

Name the temptations. The things you'll want to add at hour 14. Writing them down now is how you resist them later.

• ❌ __________________________________________________
• ❌ __________________________________________________
• ❌ __________________________________________________

Success in 24h

Tick-box definition. All three must be achievable.

• Working demo that runs end-to-end on stage
• No blocker in the golden path
• Pitch dry-run at least once with a timer

Red flags

What would kill this hack? Name them now so you can watch for them.

• ⚠️ __________________________________________________
• ⚠️ __________________________________________________

---

Once this page is filled, sign it off: "Spec locked. Moving to Phase 3."

If you can't sign it off, the hack isn't ready. Don't lie to yourself — loop back.