Claude Dispatcher — Development skill for Claude Code

Claude Dispatcher

**A terminal cockpit for running a factory of Claude Code sessions across all your repos.** Dispatch work to many repositories at once, then see — at a glance, on one screen — what's working, what shipped, and the one thing that's actually blocked waiting on you.

It sits **above** your repos, not inside any one of them. Every dispatcher is a real `claude` session in its own tmux; the cockpit is a fast, keyboard-driven viewer over all of them.


---

Why

You can run ten Claude Code sessions. You can't watch ten terminals. The cockpit collapses the whole fleet into one triage surface: it surfaces the blocked and the finished, keeps the busy ones out of your way, and hands the terminal straight to tmux when you want to jump in.

• One screen, the whole factory — dispatchers, PRs, deploys, backlog, usage and velocity across every repo and product.
• Real data, live — dispatch records + git + gh + Linear + Azure Boards, refreshed on an fsnotify watch and a poll. Nothing is mocked.
• Keyboard-first — six lenses on the number keys, one key per action, a : command palette, and ? for the map.
• Done means live — a feature stays open until it's actually deployed, not merely merged.
• Tokens, not dollars — built for a Claude subscription; usage speaks in tokens and effort.

Six lenses

Switch with the number keys. Each lens is a different question about the same factory.

	lens	the question it answers
1	triage	what is blocked, claims done, or waiting on me right now?
2	products	how is each product (many repos) doing? enter opens one
3	backlog	GitHub Issues · Linear · Azure Boards, in one list
4	usage	5-hour and weekly consumption vs my learned limits
5	decisions	ADRs, and the decision sections written in each repo's own markdown
6	*