Hermes BibleUnofficial Docs
← All flows Flow / Orchestration

How to Dominate Projects with the Hermes Agent Kanban Board

One agent is the wrong unit once work grows teeth. This field manual shows how to use Hermes Kanban — boards, tasks, claims, blocks, schedules, and receipts — to give long-running multi-agent work durable coordination that survives a dead shell.

Hermes Agentdominateprojectskanbanboardwronggrowsteeth.
Category
Orchestration
Level
Community
Author
Tony
Reading time
5 min

One agent is the wrong unit once work grows teeth. This field manual shows how to use Hermes Kanban — boards, tasks, claims, blocks, schedules, and receipts — to give long-running multi-agent work durable co...

Community flow by Tony. View source

Flow sections

Section outline mirrored from the public community flow. Use the source page for full prose and examples.

Upstream outline

  1. One agent is the wrong unit
  2. The context window isn't a manager
  3. Build the board like you mean it
  4. Small contracts beat giant prompts
  5. Claim, block, schedule, then stop improvising
  6. Receipts beat vibes
  7. The three dumb failures that keep eating afternoons
  8. When NOT to use a board
  9. The operator still owns judgment
  10. Wrapping up

Section map

One agent is the wrong unit

Frames one agent is the wrong unit for this Orchestration workflow, including the operating context to verify in the source page.

The context window isn't a manager

Frames the context window isn't a manager for this Orchestration workflow, including the operating context to verify in the source page.

Build the board like you mean it

Frames build the board like you mean it for this Orchestration workflow, including the operating context to verify in the source page.

Small contracts beat giant prompts

Frames small contracts beat giant prompts for this Orchestration workflow, including the operating context to verify in the source page.

Claim, block, schedule, then stop improvising

Frames claim, block, schedule, then stop improvising for this Orchestration workflow, including the operating context to verify in the source page.

Receipts beat vibes

Frames receipts beat vibes for this Orchestration workflow, including the operating context to verify in the source page.

The three dumb failures that keep eating afternoons

Frames the three dumb failures that keep eating afternoons for this Orchestration workflow, including the operating context to verify in the source page.

When NOT to use a board

Frames when not to use a board for this Orchestration workflow, including the operating context to verify in the source page.

Implementation notes

  • Use this Orchestration flow as a pattern library entry: start from the summary, then inspect the linked source before copying any commands, schedules, or account wiring.
  • Primary decision areas: One agent is the wrong unit, The context window isn't a manager, Build the board like you mean it, Small contracts beat giant prompts, Claim, block, schedule, then stop improvising. Treat those sections as checkpoints for scope, cost, orchestration, and human review.
  • Useful search signals for this flow: dominate, projects, kanban, board, wrong. These are derived from the public title and summary, not from private runtime data.

Decision table

Best fitOrchestration workflow pattern

Use when the summary outcome matches your own workflow and one agent is the wrong unit is relevant to your setup.

Verify firstAccounts, models, schedules, and tool access

Open the source sections for One agent is the wrong unit and The context window isn't a manager before wiring credentials or automation.

Review boundaryHuman approval point

Keep human approval for merges, spending, external messages, credentials, and unattended execution.

Verification checklist

  1. Confirm the workflow outcome matches your use case: One agent is the wrong unit once work grows teeth. This field manual shows how to use Hermes Kanban — boards, tasks, claims, blocks, schedules, and receipts — to give long-running multi-agent work durable coordination that survives a dead shell.
  2. Open the source section for One agent is the wrong unit before copying commands, prompts, or schedules.
  3. List every credential, account, model, and external service the flow would touch.
  4. Define the human approval step before spending money, sending messages, trading, merging, or running unattended.
  5. Run a small dry run and compare the result with the source sections for One agent is the wrong unit and The context window isn't a manager.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • One agent is the wrong unit once work grows teeth. This field manual shows how to use Hermes Kanban
  • boards, tasks, claims, blocks, schedules
  • to give long-running multi-agent work durable coordination that survives a dead shell.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page