omriariav

Amq Squad — Development skill for Claude Code

Development community

Role-aware agent team launcher built on top of AMQ by @avivsinai.

How to install Amq Squad

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

What Amq Squad does

Role-aware agent team launcher built on top of AMQ by @avivsinai.

Alternatives in Development

  • The Dev Squad — Give Claude its own dev team: one supervisor, four specialists, and bulletproof plans/builds without losing co 231 ★
  • Stewardship — This document defines the stewardship principles for the Claude Night Market ecosystem 222 ★
  • Initializer Prompt — YOUR ROLE - INITIALIZER AGENT (Session 1 of Many) 213 ★

README

amq-squad

**amq-squad launches and coordinates teams of Claude and Codex agents over durable AMQ.** It owns the team layer above [AMQ](https://github.com/avivsinai/agent-message-queue) by [Aviv Sinai](https://github.com/avivsinai): roles, rosters, briefs, operator gates, launch records, and the terminal/runtime controls that keep a squad observable.

The 30-second mental model:

  • AMQ is the durable coordination rail. Agents communicate through inboxes, threads, receipts, presence, and wake signals.
  • amq-squad is the project/team layer. It declares who is on the team, what each role does, which workstream they share, and how to start/stop/resume them.
  • Terminals are runtime surfaces, not the source of truth. tmux, iTerm2, and Terminal.app make agents visible and sometimes controllable; durable AMQ dispatch works even when pane injection is unavailable.
  • Operator gates bind high-risk actions. Leads may plan, dispatch, review, and collect evidence, but default-branch pushes, tags, releases, external sends, and merges need verified operator approval tied to an exact action and target.

Contents

What's new in v2.31.0

`launchapi` is now the default launch backend on tmux, with a complete digest-gated launch surface. **Two new mandatory steps:** every project needs a `.amqrc` (`amq setup`, once) and every workstream needs a brief (`amq-squad brief`) before `start`/`plan`/`resume`