Hackathon-Builder-Grok_Bot

Not six chat tabs. An AI team that ships.
Live Pages · 2-min demo · Live-run proof · MIT

---

Open kit + live proof that a Grok Bot group can take a vague objective → research → PRD → shipped PR without the human as router.

Handoffs are visible in the group room. Notion/GitHub are the source of truth. The PR trail is the demo.

Submitted & pitched

Status: Submitted to the Grok Bot Hackathon form (Notion confirmed receipt) and pitched live at Grok Bot Manila Meetup — Friday, September 4, 2026 — RealPage, X Philippines.

Entry: Mark Szn · Demo: Live Pages · Repo: Iron-Mark/Hackathon-Builder-Grok_Bot · License: MIT

GIF preview — 3:32 public-project walkthrough on Pages · mp4 (Pages + GitHub artifacts; no live Grok-room footage)

Why this exists

Most “multi-agent” demos are six ChatGPT tabs with a human as the router. This kit shows the opposite:

quadrantChart
    title Where the work actually lives
    x-axis Chat tabs --> Shared SoT
    y-axis Human as router --> Bots own handoffs
    quadrant-1 "Spec-to-Ship (this kit)"
    quadrant-2 "Fragile autonomy"
    quadrant-3 "Six chat tabs"
    quadrant-4 "Manual pipelines"
    "Six ChatGPT tabs": [0.18, 0.22]
    "One mega-agent": [0.35, 0.55]
    "Zapier-style pipeline": [0.62, 0.28]
    "Grok Bot Spec-to-Ship": [0.82, 0.86]

Loading

One chatbot / one agent	This kit
You paste context between tabs	Bots @ each other with owner + DoD
Memory is the source of truth	Notion / GitHub / Drive are SoT
Endless debate	One Reviewer pass, then escalate
Slide deck for the demo	Live room + Pages + PR trail

Built for the Grok Bot Hackathon (X Philippines): one real task, public/non-sensitive data, public GitHub, ≥1 Grok Bot.

What's in the box

pie showData
    title Kit surface area
    "bots/ profiles" : 5
    "protocol rules" : 1
    "templates" : 2
    "live-run proof" : 6
    "demo + Pages" : 2

Loading

Path	Deliverable
bots/	Paste-ready profiles — Orchestrator, Researcher, Product Design, Engineer, Reviewer
protocol/operating-rules.md	Ownership, handoff, anti-loop, escalation, completion
templates/	Notion + GitHub templates (research DB, PRD, decision log, PR checklist)
examples/live-run/	Artifacts from this crew’s first Spec-to-Ship
demo/SCRIPT.md	2-minute Showcase cut
docs/	GitHub Pages landing + docs/assets/ (hero, OG, video slot, pitch/)

Quick start

1. Create five Grok Bots; paste each file from bots/ into the Bot description.
2. Create a group chat with those five Bots.
3. Paste the kickoff from demo/SCRIPT.md.
4. Watch: plan once → @ lanes → research/PRD → public PR → one Reviewer pass → one human judgment.

Demo (2 min)

Present from Pages + the group room — not a slide deck.

gantt
    title Showcase cut (≈2 min)
    dateFormat  mm:ss
    axisFormat  %M:%S
    section Beats
    Objective in group room           :a1, 00:00, 20s
    Visible @ handoffs                :a2, after a1, 30s
    README + bots/ + Pages hero       :a3, after a2, 30s
    examples/live-run/ proof          :a4, after a3, 25s
    PR trail + protocol as product    :a5, after a4, 15s

Loading

Time	Beat
0:00	Mark: one objective in the group
0:20	Visible @ handoffs (owner / deliverable / SoT / DoD)
0:50	Cut to README + bots/
1:20	examples/live-run/ proof
1:45	PR trail + protocol/ — not six chat tabs

Full script: demo/SCRIPT.md · Presenter cues: examples/live-run/06-presenter-cues.md

Video: docs/assets/video/showcase-2min.mp4 (shot list in docs/assets/ASSETS.md).

How the crew works

flowchart TD
    H[Human — judgment only] --> O[Orchestrator\nplan once · assign · escalate]
    O --> R[Researcher]
    O --> P[Product Design]
    R --> E[Engineer\npublic PR / repo]
    P --> E
    E --> V[Reviewer\none pass vs SoT]
    V --> O
    O -->|irreversible / preference| H

Loading

Rules that keep the room useful: one owner, one deliverable, one SoT, one DoD per task. Room posts = assignment / handoff / blocker / verdict only. Full protocol: protocol/operating-rules.md.

Live-run proof

This repo is the first Spec-to-Ship:

flowchart LR
    A[01 Capabilities] --> B[02 One-pager]
    B --> C[03 Decisions]
    C --> D[04 Sources]
    D --> E[05 Reviewer PASS]
    E --> F[06 Presenter cues]

Loading

1. Capabilities — confirmed Grok Bot facts
2. Product one-pager
3. Decision log
4. Sources
5. Reviewer pass
6. Presenter cues

Assets

File	Use
docs/assets/hero-handoff.svg	Pages hero + README banner
docs/assets/og-card.svg	Social / OG preview
docs/assets/video/	Showcase recording slot
docs/assets/pitch/	12s GIF preview of the showcase storyboard
docs/assets/ASSETS.md	Shot list + asset map

License

MIT — see LICENSE.