Hackathon Team Coordinator

Hackathon Team Coordinator

A portable Agent Skill for small teams building under a hard deadline.

It gives humans and coding agents a shared way to divide work, create safe branches, hand off checked commits, integrate changes, and preserve accurate contributor credit. It works with Cursor, Claude, Codex, OpenCode, and other tools that support the Agent Skills format.

Why this exists

Hackathon teams rarely lose time because nobody can write code. They lose it when two people edit the same file, an agent works on the wrong branch, a handoff has no commit, or testing starts after the submission deadline.

This skill adds just enough coordination to prevent those failures. It does not choose your product, write your feature, or replace your existing engineering skills.

For one person doing one bounded task, it stays out of the way. For a simple two-person split, it uses a lightweight mode: separate ownership, personal branches, one checked handoff each, and one integration owner.

What it produces

• A one-page coordination contract
• Exclusive repository and file ownership
• A personal branch plan for each active editor
• Bounded task packets for Cursor, Claude, Codex, OpenCode, or another agent
• Short claim, handoff, blocker, and ready messages
• A time-aware integration, QA, and submission plan
• A contributor ledger that separates authorship from review and consulting

How it works with other skills

Hackathon Team Coordinator owns the team workflow. Specialist skills still own their technical phase.

Situation	Compatible skill
Requirements or MVP are unclear	Agentic PRD
The repository needs agent instructions	Create AGENTS.md
The build is getting too large	Ponytail
The team wants test-first development	TDD
A branch needs spec and standards review	Code Review
The contribution needs a release gate	Final QA
The user wants a broad audit or post-hack backlog	Ponytail Audit or Ticket Backlog
Wo