Ext Ops Panel
Open dashboard
Comparison

next-task vs agent-team

next-task is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). agent-team is a plugin bundle for AI coding tools published by JsonLee. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacenext-taskagent-team
Claude Code: claude-plugins-community Listed
Version: 17ee856
Forks (GitHub): 2 (last published figure)
Stars (GitHub): 7 (last published figure)
Not marked · First seen
Not listed
Community marketplace jsonlee12138/agent-team Not listed Listed
Version: 2.0.1
Forks (GitHub): 4
Stars (GitHub): 33
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

next-task vs agent-team
Factnext-taskagent-team
Marketplaces that list it11
Stars (GitHub) (differs)7 (last published figure)33
Forks (GitHub) (differs)2 (last published figure)4
Last release (differs)2026-10-27Not published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published23
LicenceMITMIT
Repository (differs)github.com/agent-sh/next-taskgithub.com/jsonlee12138/agent-team
Changes in the last 7 days (differs)62
First seen (differs)2026-10-112026-10-24

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

next-task

In its own words, on Claude Code: claude-plugins-community:

Autonomous workflow orchestrator that takes a task from discovery to production through 12 coordinated phases — exploration, planning, implementation, multi-agent review, and shipping. Pick a task from GitHub/GitLab/local sources, approve a plan, and the rest runs autonomously: git worktree creation, code generation, deslop, agnix, audit-project review loop, sync-docs, gate-and-ship. Two-file state management lets you `--resume` from any phase across session boundaries. 8 specialist agents with model selection (opus for exploration/planning, sonnet for review/CI, haiku for mechanical execution) keep token costs predictable. Workflow enforcement gates prevent skipping reviews or tests.

agent-team

In its own words, on Community GitHub marketplaces:

AI team role and worker manager for multi-agent development workflows. Includes role creation, worker management, task assignment, and git worktree integration with WezTerm/Tmux support.

How to run each

next-task As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install next-task@claude-community

agent-team As a Claude Code plugin

Claude Code
/plugin marketplace add jsonlee12138/agent-team
/plugin install agent-team@agent-team

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: next-task · What it can do: agent-team · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built