implement-fleet

Executes independent approved implementation slices in parallel using worktree-isolated workers.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill implement-fleet-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-fleet
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/implement-fleet
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill implement-fleet-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an approved implementation plan contains multiple independent slices, running them one at a time wastes wall-clock time. This Skill parallelizes slice execution by computing dependency waves from the plan, dispatching isolated workers per slice, and gating each wave with a build, typecheck, and test integration check. ## Core Features & Use Cases - Wave computation: Parses Scope and Depends-on fields from IMPLEMENTATION_PLAN.md, builds the slice DAG, and groups slices into parallelizable waves with pairwise-disjoint file scopes. - Worktree-isolated workers: Dispatches one git worktree worker per slice, each executing the implement-approved-slice contract confined to its declared scope files. - Integration gate: Merges each wave's worktrees and runs a mandatory build, typecheck, and test pass before opening the next wave. - Use Case: A task has an approved plan with six slices, three of which touch disjoint file sets. The Skill runs those three concurrently in one wave, merges them, verifies the build, then proceeds to the dependent slices. ## Quick Start Run implement-fleet on the active task to execute the approved multi-slice plan in parallel waves.

Frequently Asked Questions about implement-fleet

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

FAQPage Schema
How do I run approved implementation slices in parallel?▼

Use implement-fleet on a task whose IMPLEMENTATION_PLAN.md declares Scope and Depends-on per slice. It computes dependency waves, dispatches one worktree-isolated worker per slice, and merges each wave after a build, typecheck, and test gate passes.

When should I use implement-fleet instead of implement-approved-slice?▼

Use implement-fleet only when the approved plan's execution waves include at least one wave of size two or more. If the slice DAG is a pure chain, the task is single-slice, or slices are unapproved, use implement-approved-slice sequentially instead.

What happens if two slices touch the same files?▼

Slices whose Scope file sets overlap, or that share a coupling artifact like a migration, lockfile, codegen output, or barrel export, are placed in separate waves and run sequentially. Parallel dispatch only occurs after the disjointness and coupling checks pass.

What happens when a parallel worker fails or exceeds its scope?▼

The wave is not merged. The failing slice is surfaced and routed to sequential implement-approved-slice, while other worktrees are held until the wave can complete cleanly. Worker partials are persisted so the run remains resumable.

Does implement-fleet work across multiple repositories?▼

Yes, when SOURCE_OF_TRUTH.md declares a Repositories section, the fleet runs per repo with its own product repo, base ref, waves, and integration gate. Slices are not parallelized across repos in one run unless their scopes are disjoint per repo.