Team Agent Orchestration
Run agent squads like a team with Muse: work items with owners and merge gates, agent Kanban state, branch isolation, control pane visibility, and failure modes to watch.
- What
- Run agent squads like a team with Muse: work items with owners and merge gates, agent Kanban state, branch isolation, control pane visibility, and failure modes to watch.
- Cost
- Free
- Needs
- Use "Team Agent Orchestration" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: team-based orchestration that makes Muse manage agents like a team rather than a single assistant, so parallel agent output becomes mergeable product instead of chaos. Every agent gets a narrow contract: an owner accountable for the work item, a scope (files, branch, forbidden areas), a Kanban state (backlog, ready, running, review, blocked, merged, archived), evidence (tests, screenshots, logs, review notes), and a merge gate (the exact condition allowing integration). The flow runs in seven steps: shape the board from fuzzy ambition into work items with merge gates, pick the execution mode (single-agent, dynamic workflow, dmux/tmux, worktree fan-out), assign boundaries with one owner per card and no overlapping writes, run agents that write evidence and handoff notes, review in sequence (tests, diff, security, polish), merge deliberately through one integrator, and promote repeating card patterns into shared skills. Includes a card schema, control pane requirements (owners, heartbeats, blockers by owner, merge readiness by gate not vibes), dynamic workflow compatibility rules, and failure modes to watch: agent soup, invisible work that lives only in chat transcripts, board theater, overlapping writes, and process that produces docs but no runnable surface. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: this is process discipline, it only works if agents actually follow contracts and write evidence; a board without acceptance criteria is theater, the skill says so itself. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Team Agent Orchestration" with your Muse. Prerequisites: none to install. Pure guidance; a multi-agent setup (branches or worktrees) helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/team-agent-orchestration/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Shape this work into an agent Kanban board: [describe the project]. Give each card an owner, scope, acceptance criteria, and merge gate." 3. Ask it to flag failure modes as they appear: agent soup, overlapping writes, cards without acceptance criteria. Tip: ask "what can safely merge right now, by gate, not by vibes?" Safety: a skill is plain-text instructions; it runs nothing by itself. Keep one integrator for conflict resolution.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.