Agent Plugins Marketplace
← All plugins

fleet

v1.0.0

The fan-out lane: a backlog turned into parallel work across sessions and worktrees — the one thing a flow may never do. fleet-issue-sweep triages a repository's open issues for relevance and for collision with work in flight, proposes the stale ones for closure, and dispatches up to five independent worker sessions, one issue and one worktree each, then waits them out and writes the brief. fleet-resolve-issue is what each worker runs: one issue to a pull request when the change proves itself, or to a parked worktree with a handoff brief when a human has to look. fleet-morning-brief re-reads a past sweep from its manifest and worker result files. An L1 extension over delivery: it owns no flow and holds no gate, and trades Personal Validation for a pull request nobody merges unread.

Claude Code3 Skills

By Job SchepersLicense: MIT0 GitHub starsUpdated last week

Directory evidence

Runtimes
Claude Code
Parsed components
3 skill or MCP entries
Source updated
Sep 14, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install fleet for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install fleet-2@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/JSdotNet/ai-agent-stack

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/fleet/.

Plugin files

plugins/fleet/
├── .claude-plugin/plugin.json
├── skills/fleet-issue-sweep/SKILL.md
├── skills/fleet-morning-brief/SKILL.md
└── skills/fleet-resolve-issue/SKILL.md

Included Skills3

fleet-issue-sweepskills/fleet-issue-sweep/SKILL.md

Sweep a repository's open issues: judge which are still relevant, propose the stale ones for closure, skip anything colliding with work in flight, dispatch up to 5 parallel worker sessions that each resolve one issue in its own worktree, then wait for them and write the brief. Use when: sweeping or triaging a backlog of open issues, or running a scheduled issue sweep. DO NOT USE FOR: a single issue (use start-session-from-issue with a human present, fleet-resolve-issue without one); never start a sweep mid-task — only a user turn or a schedule's prompt may.

fleet-morning-briefskills/fleet-morning-brief/SKILL.md

Report what an overnight issue sweep actually did: read the sweep manifest and every worker result, and produce one brief covering the pull requests opened, the worktrees parked and waiting for validation, the closure proposals still unanswered, and everything that failed — each with the one command that acts on it.

fleet-resolve-issueskills/fleet-resolve-issue/SKILL.md

Resolve one open GitHub issue end to end, unattended: claim it, cut it a dedicated worktree and branch, run the resolve-issue Workflow script (scope, TDD implementation, build and test with bounded repair, multi-lens review), then open a pull request when the change proves itself or park the worktree with a handoff brief when a human must validate it. One issue per run. Use when: a sweep's worker session or a scheduled run asks for exactly one issue resolved unattended. DO NOT USE FOR: work a human is sitting with (use start-session-from-issue); never start it mid-task — only a user turn, a schedule, or a sweep's dispatch prompt may.

Plugin manifests1

plugins/fleet/.claude-plugin/plugin.json
{
  "name": "fleet",
  "version": "1.0.0",
  "description": "The fan-out lane: a backlog turned into parallel work across sessions and worktrees — the one thing a flow may never do. fleet-issue-sweep triages a repository's open issues for relevance and for collision with work in flight, proposes the stale ones for closure, and dispatches up to five independent worker sessions, one issue and one worktree each, then waits them out and writes the brief. fleet-resolve-issue is what each worker runs: one issue to a pull request when the change proves itself, or to a parked worktree with a handoff brief when a human has to look. fleet-morning-brief re-reads a past sweep from its manifest and worker result files. An L1 extension over delivery: it owns no flow and holds no gate, and trades Personal Validation for a pull request nobody merges unread.",
  "author": {
    "name": "Job Schepers"
  },
  "license": "MIT",
  "keywords": [
    "fleet",
    "fan-out",
    "delivery",
    "backlog",
    "triage",
    "issues",
    "worktree",
    "unattended",
    "parallel",
    "github",
    "sweep"
  ],
  "dependencies": [
    {
      "name": "delivery",
      "version": ">=1.0.0 <2.0.0",
      "marketplace": "jsdotnet"
    }
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[fleet on Agent Plugins Marketplace](https://pluginsmp.com/plugins/fleet-2)