build-fleet

Dispatches parallel worktree agents to implement plan backlogs and open pull requests.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentics-kit --skill build-fleet-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-fleet
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/plan-agent/skills/build-fleet
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill build-fleet-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing a backlog of plans one at a time is slow and serial; this Skill ships multiple plans concurrently by spawning one isolated git worktree agent per plan, each building its plan and opening its own pull request. ## Core Features & Use Cases - Parallel plan dispatch: Discovers every status: todo plan in the plans directory and launches one background subagent per selected plan, each in its own git worktree. - Mandatory confirmation gate: Presents a multi-select picker before dispatching, since every selected plan opens a real pull request against the shared remote. - Verified reporting: Cross-checks each agent's reported PR with gh pr view before marking it green, and stops at open PRs rather than auto-merging. - Use Case: You have five status: todo plan specs in docs/plans/. Run the fleet with --max 3 to ship the three newest plans simultaneously, each on its own branch with its own PR, then merge them yourself oldest-first. ## Quick Start Ask the agent to run the build fleet over the plans directory with a maximum of three concurrent plans and confirm which plans to ship.

Frequently Asked Questions about build-fleet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement multiple plans in parallel with Claude Code?▼

Run the build-fleet skill over your plans directory. It discovers every plan with status todo, asks you to confirm a selection, then dispatches one background worktree agent per plan that builds the plan and opens a pull request.

How do I limit the number of concurrent plan agents?▼

Pass the --max flag, for example --max 5. The default is 3, because more concurrent agents on one repository tend to produce more merge conflicts than saved time, and the subagent pool queues past its concurrency cap anyway.

Does build-fleet merge the pull requests it opens?▼

No. The fleet deliberately stops at green open pull requests because a background agent cannot answer the merge gate and auto-merging sibling PRs has no cheap undo. You merge them yourself afterward, oldest first.

Why is a plan with status in-progress not picked up by the fleet?▼

Discovery only selects plans with status todo. An in-progress plan usually already has a branch and partial work, and a fleet agent would fork a second branch from the base and redo it. Name the plan explicitly to override.

What happens if my repository uses master instead of main?▼

The skill resolves the remote's default branch via git symbolic-ref on origin/HEAD and passes the resolved name to every agent prompt. It never hardcodes main, so master or develop repositories work correctly.