erikedling

Herdquarters — Development skill for Claude Code

Development community

Delegate tasks to a team of coding agents and keep track of all of them in one place: who's working, who needs you and who's done.

How to install Herdquarters

This entry records only its repository, not the path inside it, so there is no exact command to give. Open erikedling/herdquarters and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Herdquarters does

Delegate tasks to a team of coding agents and keep track of all of them in one place: who's working, who needs you and who's done.

Alternatives in Development

  • Tmux Claude Session Manager — Run many Claude Code sessions across your projects, each in its own tmux session — then list them, see which a 380 ★
  • New Op — Guide for adding a new variant to the Op enum (e.g. Op::Tag, Op::Link) 201 ★
  • Working Memory — This is your working memory 192 ★

README

Herdquarters: a pixel-art office building with a coding agent in every window

Herdquarters

Delegate tasks to a team of coding agents and keep track of all of them in one place.

Running five agents in five terminals is a lot of tab-switching. Herdquarters turns them into a small office. You give the work to a boss agent, the boss hands it out to workers, and you can see at a glance who's typing, who's waiting on you and who's done. A little bird called PiPi, your assistant, makes sure you never forget what anyone is waiting for.

It's a desktop app built on [herdr](https://herdr.dev), the agent multiplexer for your terminal, and works with [Claude Code](https://claude.com/claude-code) and [Pi](https://github.com/badlogic/pi-mono).

How it works

1. Tell the boss what you need

You tell the boss: add dark mode to web and api. The boss says: on it!

Create an **orchestrator**: point it at the folder that holds your repos and give the work a name. You get a **boss**, an agent that acts as your assistant. Describe the task in plain words, screenshots welcome. The boss plans it and hands it out, and never edits code itself.

2. The boss builds the team

The boss at the top, connected to three rooms called api, web and infra, each with a worker typing

For each repo the task touches, the boss opens a **worker** in its own git worktree, all on one shared branch. Workers code, run the tests and report back. The boss keeps a **board** of what's done and what's next.

3. Step in only when it matters

Three desks: one person typing, one with a raised hand and a red question mark, one waving on top of the desk with a green check
You see It means
Someone ty