🚀Intent-Driven Hackathon Team (5 Roles Total)

🚀Intent-Driven Hackathon Team (5 Roles Total)

🧭 1. Delivery Lead + Demo Owner

(DM + Demo combined)

Owns:

• Business outcome

• StoryMap vision (from your intent.md)

• Final demo narrative

Responsibilities:

• Anchor the problem:

“This is for real estate developers to tell location stories visually”

• Decide:

• What features MUST work (anchor, markers, POI, export)

• Control scope (critical for hackathon)

• Drive final demo

Deliverables:

• Demo script

• Final walkthrough

• “Why this matters” story

⸻

🧠 2. Solution Architect + Intent Owner (You)

(SA + Intent Architect combined)

Owns:

• The intent.md interpretation

• System architecture

• Guardrails

Responsibilities:

• Translate intent.md → system design:

• React + Leaflet structure

• Data flow (LocalStorage, Overpass, GeoJSON)

• Guide team:

• “We follow the intent exactly—no feature creep”

• Define:

• Component boundaries

• Data contracts (markers, layers, etc.)

Your Key Move:

“We are not designing screens—we are executing intent.”

Deliverables:

• Architecture sketch (mental or quick diagram)

• Clear dev breakdown

• Real-time decision authority

⸻

⚙️ 3. Tech Lead + Compiler Engineer

(Tech Lead + Intent Compiler hybrid)

Owns:

• Turning intent into working code via Claude

Responsibilities:

• Run Claude Code using:

• your intent.md

• Break into prompts:

• Phase 1 → setup

• Phase 2 → geocoding

• Phase 3 → markers

• Ensure:

• Code consistency

• Correct use of libraries (Leaflet, Overpass)

Key Behavior:

• Doesn’t overthink—iterates fast with Claude

• Fixes and refines generated code

Deliverables:

• Working React app skeleton

• Feature-by-feature completion

⸻

💻 4. Full Stack Engineer (UI + Map + Integration)

(Frontend + Integration combined)

Owns:

• The actual user experience + map behavior

Responsibilities:

• Implement:

• Leaflet map rendering

• Click-to-add markers

• Sidebar UI

• Integrate:

• Nominatim (search)

• Overpass API (POIs)

• Handle:

• LocalStorage persistence

• Marker rendering

This is your “make it real” role

Deliverables:

• Functional UI

• Map interactions working live

⸻

🧪 5. QA + Runtime + Scrum Master

(QA + Runtime + SM combined)

Owns:

• Flow, testing, and stability

Responsibilities:

• Run mini standups:

• “What’s blocked?”

• “What’s next?”

• Test continuously:

• Does geocoding work?

• Are markers saving?

• Does export function?

• Fix:

• Runtime issues

• Browser bugs

• Keep team moving fast

Key Mindset:

“If it doesn’t run, it doesn’t count.”

Deliverables:

• Stable demo app

• No broken flows

• Time management

⸻

⚙️ How Your Team Executes (Using intent.md)

🔥 Golden Rule (Reinforce This Hard)

“intent.md is the source of truth — not opinions.”

⸻

🟦 Phase 1 (Hour 1–2) — Foundation

• Architect + Tech Lead:

• Feed Claude:

“Read intent.md and build Phase 1”

• Output:

• React + Leaflet + CartoDB map running

⸻

🟨 Phase 2 (Hour 2–4) — Anchor + Markers

• Add:

• Geocoding (Nominatim)

• Golden property marker

• Click-to-add markers (LocalStorage)

⸻

🟩 Phase 3 (Hour 4–6) — Data Layers

• Integrate:

• Overpass API (POIs)

• Crime heatmap (GeoJSON mock)

⸻

🟥 Phase 4 (Hour 6–7) — Export

• Add:

• Print/export (leaflet-browser-print)

• Clean print view

⸻

🟪 Phase 5 (Hour 7–8) — Demo Polish

• Clean UI

• Tighten story

• Remove bugs

⸻

🧠 Clean Role Mapping (Simple Table)

Combined Role Covers Focus

Delivery Lead DM + Demo Story + outcome

Architect SA + Intent Design + intent control

Tech Lead Lead + Compiler Claude-driven build

Full Stack Dev FE + Integration UI + map + APIs

QA / SM QA + Scrum + Runtime Stability + flow

⸻

🎯 What Makes This Powerful (Your Differentiator)

Other teams:

“We built a map app”

Your team:

“We gave Claude an intent… and the system built itself.”

⸻