AIPM
Theme

AIPM package

Team Agent Orchestration

@affaan-m/team-agent-orchestration@1.0.0

Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.

Scanned · no issues · Nov 7, 2026

GitHub stars: ★ 299K

LinkedInPost

Install Skill

Pins this version in aipm.package.json and aipm-lock.json.

aipm add @affaan-m/team-agent-orchestration@1.0.0

Without project tracking

Writes the skill files only. Add --no-init to skip aipm.package.json and the lockfile.

aipm add @affaan-m/team-agent-orchestration@1.0.0 --no-init

How to use

Install the skill above, then run this in your AI tool:

/team-agent-orchestration <your description>

About

Use this skill when agents are being managed like a team rather than a single assistant. The purpose is to make team-based orchestration reliable: clear work items, explicit ownership, agent Kanban state, branch isolation, control pane visibility, and merge gates.

Source

What gets added to your project

Preview every file this package writes on install before you run the command above.

Summary

Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates. Use when coordinating multiple agents in parallel across branches or worktre...

Skill instructions

Team Agent Orchestration

Use this skill when agents are being managed like a team rather than a single assistant. The purpose is to make team-based orchestration reliable: clear work items, explicit ownership, agent Kanban state, branch isolation, control pane visibility, and merge gates.

When To Activate

  • The task spans multiple agents, tools, harnesses, branches, or worktrees.
  • The user mentions team orchestration, agent Kanban, squad, conductor, control pane, manager, desktop app, Zellij, tmux, Hermes, Devin, Codex, Claude Code, or multi-agent work.
  • A project needs shared workflow state across people and agents.
  • Existing agent fan-out is producing output but not mergeable product.

Operating Model

Treat every agent as a teammate with a narrow contract:

  • Owner: the person or agent accountable for the work item.
  • Scope: files, branch, tool surface, and forbidden areas.
  • State: backlog, ready, running, review, blocked, merged, or archived.
  • Evidence: tests, screenshots, logs, review notes, or eval reports.
  • Merge gate: the exact condition that allows integration.

Agent Kanban

Use agent Kanban when work must be visible across sessions.

ColumnMeaningExit Criteria
BacklogCandidate work item, not yet shapedAcceptance criteria written
ReadyShaped and assignableOwner and branch/worktree assigned
RunningAgent is actively workingHandoff artifact and changed files exist
ReviewWork is complete but not mergedTests, diff review, and risk check pass
BlockedNeeds external input or failed gateBlocker has owner and next action
MergedIntegrated into mainlinePR merged or local main updated
ArchivedNo longer relevantReason recorded

Each card should fit this schema:

json
{
  "id": "agent-card-001",
  "title": "Build dynamic workflow skill",
  "owner": "codex",
  "state": "running",
  "branch": "product/dynamic-workflow-team-orchestration",
  "worktree": ".",
  "acceptance": [
    "Skill exists",
    "Tests cover required concepts",
    "Content artifact contains video and article angles"
  ],
  "merge_gate": "lint, focused tests, and catalog check pass",
  "handoff": "path/to/handoff.md"
}

Team-Based Orchestration Flow

  1. Shape the board: convert fuzzy ambition into work items with owners and merge gates.
  2. Pick execution mode: single-agent, dynamic workflow mode, dmux/tmux, worktree fan-out, or external desktop orchestrator.
  3. Assign boundaries: one owner per card, clear file scope, and no overlapping writes without an integrator.
  4. Run agents: each agent writes evidence and handoff notes, not just code.
  5. Review in sequence: tests first, then diff review, then security/risk checks, then content/product polish.
  6. Merge deliberately: one integrator resolves conflicts and updates the control pane or status artifact.
  7. Extract reusable skill: if the card pattern repeats, promote it into skills/.

Control Pane Requirements

A useful control pane for team orchestration should show:

  • Active work items and their agent Kanban state.
  • Owner, harness, branch, worktree, and last heartbeat.
  • Links to handoff artifacts, tests, screenshots, and PRs.
  • Blockers grouped by owner and unblock action.
  • Merge readiness by gate, not vibes.
  • Reusable workflow candidates that should become shared skills.

Do not add more automation until the operator can answer: who owns this, what changed, what gate failed, and what can safely merge?

Dynamic Workflow Compatibility

When a card needs dynamic workflow mode:

  • Put the task-local harness under the card owner.
  • Store inputs and outputs on the card.
  • Require an eval before moving from Running to Review.
  • Promote the harness to a shared skill only after repeat use.

Failure Modes To Watch

  • Agent soup: many agents running, no owner or merge gate.
  • Invisible work: useful output exists only in a chat transcript.
  • Board theater: a Kanban board exists but cards have no acceptance criteria.
  • Overlapping writes: parallel agents edit the same files without worktrees.
  • No product artifact: the process produces docs but no runnable or publishable surface.

Output Standard

Finish each orchestration pass with:

  • Board/card changes.
  • Merged or pending branches.
  • Tests and eval evidence.
  • Blockers with owner and next action.
  • New shared skill candidates.

Loading package files…

Share this package

Add an Install with AIPM badge

Add this badge to a GitHub README so readers can open the package page and install the same version.

Install with AIPM
[![Install with AIPM](https://www.aipm-registry.com/install-with-aipm.svg)](https://www.aipm-registry.com/skills/affaan-m/team-agent-orchestration/1.0.0?utm_source=github&utm_medium=readme&utm_campaign=package_badge)

Publisher

Affaan Mustafa

This imported publisher has not claimed its AIPM account. A connected account confirms account control, but it does not guarantee that a package is safe.

AI assistant context

What this skill is for

@affaan-m/team-agent-orchestration@1.0.0 is an AIPM skill package for All tools. Use it when a project needs the reusable AI behavior described as: Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates. Use when coordinating multiple agents in parallel across branches or worktre...

Install
aipm add @affaan-m/team-agent-orchestration@1.0.0
Use after install
/team-agent-orchestration <your description>

Tool targets

Install command by target

Add --no-init to any of these when you want the skill files without aipm.package.json or aipm-lock.json.

cursor

Run this variant when you want to install the package into cursor.

aipm add @affaan-m/team-agent-orchestration@1.0.0 --target cursor --ci

claude

Run this variant when you want to install the package into claude.

aipm add @affaan-m/team-agent-orchestration@1.0.0 --target claude --ci

Discussion

Comments (0)

Loading comments…

Keep exploring

Affaan Mustafa/ui-canvas

Preview a UI component mockup in a local browser canvas where the human directly edits it (move, resize, edit text, delete, restyle), switches mobile/desktop/custom viewports, tests it, chats with you, and clicks Save and Finish. You the...

Published by Affaan Mustafa

skillScanned · no issues★ 308KImported · UnverifiedAll toolsNov 21, 2026, 1:11 AM6.61 KBMIT

Affaan Mustafa/yoruba-localization-testing

Test Yoruba (yo) and English bilingual interfaces for tone marks, underdots, Unicode normalization, translation fallback, and accessibility.

Published by Affaan Mustafa

skillScanned · no issues★ 306KImported · UnverifiedAll toolsNov 18, 2026, 1:19 AM3.43 KBMIT

Affaan Mustafa/web-perimeter-owasp-2025-audit

Passive, non-destructive web perimeter security auditing mapped to OWASP Top 10:2025 surface leads, CDN Unkeyed Header Web Cache Poisoning (X-Forwarded-Host), supply chain manifest exposure, git object dumping prevention (/.git/HEAD), cr...

Published by Affaan Mustafa

skillScanned · flagged★ 305KImported · UnverifiedAll toolsNov 17, 2026, 1:13 AM8.86 KBMIT

Package FAQ

Install and compatibility

How to install
Run aipm add @affaan-m/team-agent-orchestration@1.0.0 in a project that has AIPM initialized.
Supported tools
@affaan-m/team-agent-orchestration@1.0.0 supports All tools.

Before installing

AIPM skills can add files to your project. Review the package name, target, description, license, and publisher before installing. Use a clean branch when trying a new skill.