Agenthub

Agent Templates

When spawning with --template, agents follow a predefined iteration pattern:

Templates are defined in references/agent-templates.md.

When This Skill Activates

Trigger phrases:

• "try multiple approaches"
• "have agents compete"
• "parallel optimization"
• "spawn N agents"
• "compare different solutions"
• "fan-out" or "tournament"
• "generate content variations"
• "compare different drafts"
• "A/B test copy"
• "explore multiple strategies"

Coordinator Protocol

The main Claude Code session is the coordinator. It follows this lifecycle:

INIT → DISPATCH → MONITOR → EVALUATE → MERGE

1. Init

Run /hub:init to create a session. This generates:

• .agenthub/sessions/{session-id}/config.yaml — task config
• .agenthub/sessions/{session-id}/state.json — state machine
• .agenthub/board/ — message board channels

2. Dispatch

Run /hub:spawn to launch agents. For each agent 1..N:

• Post task assignment to .agenthub/board/dispatch/
• Spawn via Agent tool with isolation: "worktree"
• All agents launched in a single message (parallel)

3. Monitor

Run /hub:status to check progress:

• dag_analyzer.py --status --session {id} shows branch state
• Board progress/ channel has agent updates

4. Evaluate

Run /hub:eval to rank results:

• Metric mode: run eval command in each worktree, parse numeric result
• Judge mode: read diffs, coordinator ranks by quality
• Hybrid: metric first, LLM-judge for ties

5. Merge

Run /hub:merge to finalize:

• git merge --no-ff winner into base branch
• Tag losers: git tag hub/archive/{session}/agent-{i}
• Clean up worktrees
• Post merge summary to board

Agent Protocol

Each subagent receives this prompt pattern:

You are agent-{i} in hub session {session-id}.
Your task: {task description}

Instructions:
1. Read your assignment at .agenthub/board/dispatch/{seq}-agent-{i}.md
2. Work in your worktree — make changes, run tests, iterate
3. Commit all changes with descriptive messages
4. Write your result summary to .agenthub/board/results/agent-{i}-result.md
5. Exit when done

Agents do NOT see each other's work. They do NOT communicate with each other. They only write to the board for the coordinator to read.

DAG Model

Branch Naming

hub/{session-id}/agent-{N}/attempt-{M}

• Session ID: timestamp-based (YYYYMMDD-HHMMSS)
• Agent N: sequential (1 to agent-count)
• Attempt M: increments on retry (usually 1)

Frontier Detection

Frontier = branch tips with no child branches. Equivalent to AgentHub's "leaves" query.

python scripts/dag_analyzer.py --frontier --session {id}

Immutability

The DAG is append-only:

• Never rebase or force-push agent branches
• Never delete commits (only branch refs after archival)
• Every approach preserved via git tags

Message Board

Location: .agenthub/board/

Channels

Post Format

---