Skip to main content

Scope

Five minutes. Company, industry, pain point — the Scoping agent turns that into a 60-minute build spec: a one-sentence use case, exactly three justified primitives, your Worker name, a paste-ready prompt for your own coding agent, and a wrangler.jsonc snippet. This is the hardest 20 minutes of any hackathon, compressed to five.

Or just ask your agent​

The same spec is available as an MCP tool — once Arm Your Agent is wired up to the agenthack MCP server:

Scope my project. Company: <your company>. Industry: <your track>. Pain point: <what's broken>.

What to do with the output​

  1. Copy the prompt and paste it, unedited, into your own coding agent (Claude Code, Cursor, Codex, OpenCode — whichever you armed in the last step). It already assumes agents-starter and keeps your existing chat agent working.
  2. Your Worker name is fixed. Eight teams share one Cloudflare account today — always deploy with the exact name the spec gives you, prefix included, or you'll collide with another team.
  3. Pick one of the three primitives, not all three. The spec lists three because that's what the matching industry playbook justifies for your track — the build task only asks for one.
  4. The approval gate is a bonus, not a requirement — but it's worth rubric points (see Submit) and it's the whole theme of today.

If the agent isn't reachable​

Nothing about starting your build depends on this page loading. The page falls back to a link straight to your matching playbook in the Industry Playbooks section of the sidebar — same three primitives, same paste-ready prompt, written out ahead of time.

Next: Build — the clock starts here.