preparing-hackathon-submission

name	preparing-hackathon-submission
description	Prepares the hackathon submission package, demo assets, and judge-facing materials, and is used when Diverge needs a polished final presentation.

Turns the build into a clear, credible, submission-ready story for judges.

Use this skill when

• The product is close to demo-ready.
• README, architecture diagram, Devpost copy, and demo script must be created.
• GCP proof and submission checklist need to be assembled.
• The team wants to maximize judging clarity, not just technical completeness.

Capabilities

• Writes a clean README for a public repo.
• Defines the architecture diagram content.
• Drafts a short, compelling demo video script.
• Prepares Devpost-friendly product copy.
• Organizes proof of Google Cloud deployment.
• Creates a final checklist so nothing is missed.

Workflow

1. Choose one polished demo path. Do not try to show every possible branch.
2. Write the README.
   • what Diverge is
   • why it is novel
   • how the 8-agent system works
   • stack used
   • setup steps
   • live demo/deployment link
3. Create the architecture diagram.
   • user input
   • FastAPI backend
   • ADK orchestrator
   • 8 agents
   • Cloud Storage
   • React frontend
   • Cloud Run deployment
4. Draft the demo video script.
   • hook
   • emotional intake
   • one strong story branch
   • meaningful choice
   • multimodal scene with AI-generated GIF panels showing real motion
   • ending
   • quick architecture explanation
5. Write Devpost text.
   • problem / opportunity
   • solution
   • technical stack
   • what makes it innovative
   • what was challenging
   • what comes next
6. Gather proof of GCP deployment.
7. Run the final checklist.

README outline

• Project title and one-sentence pitch
• Actual GIF panel examples showing real motion (the key differentiator)
• Why this matters
• Tech stack
• Architecture
• Local setup
• Deployment
• Demo link
• Challenge alignment

Demo video structure

Aim for under 4 minutes:

1. 15 sec — hook and emotional premise
2. 45 sec — intake and setup
3. 90 sec — scene and choice moment
4. 30 sec — ending
5. 30 sec — architecture + Google Cloud proof
6. 15 sec — closing

Submission checklist

• Public repo is clean
• README is understandable
• Demo video is uploaded
• Devpost text is polished
• Architecture diagram exists
• Cloud Run proof is captured
• Live link works
• No secrets in repo

Guardrails

• Judges reward clarity. Do not bury the story experience under technical detail.
• Show story quality and multimodal UX first; architecture second.
• Make sure the demo actually works end to end before polishing copy.

Project references

• AGENTS.md — judging priorities, user context, system architecture, MVP focus.
• docs/PRD.md — product vision, narrative uniqueness, multimodal storytelling approach.
• docs/roadmap.md — required submission deliverables and MVP scope.