Index of every page on this site: llms.txt
All skills
Run it yourself

Plan and run coding work with many Claude Code agents through Claude DevFleet. Each agent works in its own Git worktree. Review the plan, track work, and read clear reports.

  • 1 file
  • 4.7 KB
  • Updated 3 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/agenticluke/parallel-code-fleet-plus/skill

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈45 tokens for metadata: the name and description. ≈1.1k when used: this file.

Description uses 2.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈191 characters, or 2.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Claude DevFleet

Community skill. Full credit goes to the original author.

When to Use

Use this skill when a coding job has parts that agents can do at the same time.

Good tasks include:

  • Building separate app parts
  • Adding code and tests
  • Fixing bugs in different files
  • Reviewing a large change

Do not use it for a small task that one agent can finish fast.

Each agent works in its own Git worktree. DevFleet can merge finished work.

Setup

A Claude DevFleet server must be running at port 18801.

Add it to Claude Code:

claude mcp add devfleet --transport http http://localhost:18801/mcp

If the server cannot be reached, stop and tell the user. Do not start work outside DevFleet unless the user agrees.

Main Flow

User asks for a project
  |
  v
plan_project(prompt)
  |
  v
Show the plan and ask for approval
  |
  v
dispatch_mission(first_mission_id)
  |
  v
Watch each mission
  |
  v
Read each report
  |
  v
Check merge results and tell the user

Tools

Tool What it does
plan_project(prompt) Makes a project and a list of linked missions. Returns a project_id.
create_project(name, path?, description?) Makes a project by hand. Returns a project_id.
create_mission(project_id, title, prompt, depends_on?, auto_dispatch?) Adds a mission. depends_on is a list of mission ID strings. Set auto_dispatch=true to start it after all needed missions pass.
dispatch_mission(mission_id, model?, max_turns?) Starts one mission.
cancel_mission(mission_id) Stops a mission that is still running.
wait_for_mission(mission_id, timeout_seconds?) Waits for a mission. A timeout does not mean the mission failed.
get_mission_status(mission_id) Checks a mission without waiting.
get_report(mission_id) Gets the final report, such as changed files, work done, errors, and next steps.
get_dashboard() Shows active agents and system totals.
list_projects() Lists all projects.
list_missions(project_id, status?) Lists missions in one project. You may filter by status.

Steps

  1. Call plan_project with the full task.
  2. Check that each mission has one clear goal.
  3. Check all links between missions.
  4. Show the plan to the user.
  5. Get approval before you start agents.
  6. Start missions that have no unmet needs.
  7. Use get_mission_status to check progress.
  8. Use get_report after each mission ends.
  9. Confirm that merges passed.
  10. Tell the user what changed, what failed, and what is left.

Safety Rules

  • Do not start agents before the user approves the plan.
  • Do not run two missions at once if they edit the same files.
  • Put shared setup work in an early mission.
  • Use depends_on when one mission needs code from another.
  • Use auto_dispatch=true only when the next mission is safe to start on its own.
  • Set a fair max_turns for work that could run too long.
  • Do not cancel a mission just because wait_for_mission timed out. Check its status first.
  • If a mission fails, read its report before trying again.
  • Do not start missions that depend on a failed mission.
  • If a merge fails, stop new linked work. Report the conflict.
  • If an agent changes files outside its task, report those files.
  • Never hide errors or claim that unfinished work is done.
  • Do not add web calls, tracking, analytics, or telemetry.

Example

The user asks:

Build a REST API with login and tests.

First, make a plan:

plan_project(
  prompt="Build a REST API with user login, token checks, input checks, and tests. Keep API code and test code in separate missions when safe."
)

Show the returned missions. Ask the user to approve them.

A good plan may look like this:

M1: Add the API base and data model
M2: Add login and token checks
    depends_on: [M1]
M3: Add API tests
    depends_on: [M2]

After approval, start the first mission:

dispatch_mission(
  mission_id="M1",
  max_turns=20
)

Check it without blocking:

get_mission_status(mission_id="M1")

When it ends, read the report:

get_report(mission_id="M1")

If M1 passed and merged, start M2. If later missions use auto_dispatch=true, confirm they started only after their needs passed.

At the end, report:

Done:
- Added the API base.
- Added login and token checks.
- Added tests.

Checks:
- All missions passed.
- All merges passed.
- Tests passed.

Files changed:
- src/api.py
- src/auth.py
- tests/test_api.py

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 9caede2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 3 months ago
origin
community

README badge

README badge for agenticluke/parallel-code-fleet-plus