$ loading_
Coordinate multi-agent teamwork with ownership, Kanban flow, merge gates, and handoffs.
The material indicates a prompt-only/process-orchestration skill with no required secrets, no declared remote endpoints, and no described local code execution or data read/write capability. Combined with its open-source GitHub source and very high community adoption, the overall risk is low, though the missing license and unknown maintenance status warrant some supply-chain attention.
The material explicitly states that no keys or environment variables are required; the README does not request logins, tokens, or authentication to external services, and no direct credential collection or abuse pattern is evident.
Both the system checks and the material show no remote endpoints; the content is primarily team workflow and Kanban guidance, with no described transmission of user data to external services.
This item is classified as a prompt-only skill. Although the README mentions concepts such as branches, worktrees, and tmux, it does not provide executable installation steps, scripts, or any stated ability to spawn local processes.
The material does not declare any ability to read, modify, or persist local files, databases, or API resources; references such as 'handoff' and 'changed files' are workflow abstractions rather than actual granted access.
The source is an open-source GitHub repository with very high community adoption (about 210k stars), both of which are strong risk-reducing signals. However, the license is unspecified and maintenance status is unknown, so the current repository contents and activity should still be verified before reuse.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "team-agent-orchestration" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/team-agent-orchestration/SKILL.md 2. Save it as ~/.claude/skills/team-agent-orchestration/SKILL.md 3. Reload skills and tell me it's ready
Design a collaboration workflow for a team of four AI agents: requirements analyst, backend developer, frontend developer, and tester. Break work into items, define ownership, Kanban states, handoff conditions, and merge gate rules, then output an executable weekly sprint plan.
A multi-agent sprint orchestration plan with task breakdown, ownership, status flow, handoff rules, and merge checkpoints.
Create a unified handoff mechanism for product, design, development, and QA agents. Define control-pane handoff fields, definition of done, blocker escalation paths, and the Kanban flow from backlog to release so each agent knows when to take over or send work back.
A standardized agent handoff protocol describing workflow stages, handoff data, escalation paths, and rollback conditions.
Design a merge gate workflow for a scenario where multiple coding agents submit code together, including task ownership, branching strategy, automated test triggers, code review owners, and rework routing when gates fail.
A merge gate plan for multi-agent development covering branches, reviews, testing, and rework flow.
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.
Treat every agent as a teammate with a narrow contract:
Use agent Kanban when work must be visible across sessions.
| Column | Meaning | Exit Criteria |
|---|---|---|
| Backlog | Candidate work item, not yet shaped | Acceptance criteria written |
| Ready | Shaped and assignable | Owner and branch/worktree assigned |
| Running | Agent is actively working | Handoff artifact and changed files exist |
| Review | Work is complete but not merged | Tests, diff review, and risk check pass |
| Blocked | Needs external input or failed gate | Blocker has owner and next action |
| Merged | Integrated into mainline | PR merged or local main updated |
| Archived | No longer relevant | Reason recorded |
Each card should fit this schema:
{
"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"
}
skills/.A useful control pane for team orchestration should show:
Do not add more automation until the operator can answer: who owns this, what changed, what gate failed, and what can safely merge?
When a card needs dynamic workflow mode:
…
Handle returns, refunds, fraud checks, and warranty claim decisions efficiently.
Use Bun for runtime, bundling, testing, packages, and Node migration decisions.
Use the correct Ethereum Keccak-256 hashing in Node.js and TypeScript.
Apply Nuxt 4 patterns for SSR safety, performance, and data fetching.
Generate images, videos, and audio with one unified AI media workflow.
Design Quarkus 3 backend patterns for messaging, APIs, data, and async workflows.
Coordinate multiple AI agents in one Git repo and prevent conflicts early.
Orchestrate multiple AI agents in real time and monitor tasks and artifacts.
Coordinate multiple AI models and personas for review, debate, and ideation.
Lets AI check a team's decision ledger before acting on past decisions.
Operate long-running agent workloads with monitoring, security, and lifecycle control.
Turn goals into task DAGs and orchestrate TypeScript-native multi-agent workflows.