dos-goal-fleet

Coordinate parallel goal execution with wave-based worker launches and verified completion.

18|4|Updated Jun 10, 2026

Search Tags:#parallel execution #git safety #dos #worker orchestration #goal fleet #witness verification #file tree arbitration

Ready to run

npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-goal-fleet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dos-goal-fleet
Source: https://github.com/anthony-chaudhary/dos-kernel/tree/main/claude-plugin/skills/dos-goal-fleet
Command: npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-goal-fleet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It coordinates multiple independent objectives so they can run in parallel without colliding, lying about completion, or overloading the available worker seats.

Core Features & Use Cases

Wave-based launch planning: Splits a mixed set of goals into safe batches that fit the available seat pool.
File-tree collision avoidance: Uses arbitration to keep same-wave workers from writing overlapping paths.
Witnessed completion and rollup: Verifies claimed ships with git-backed evidence and independent read-backs before folding results into a final report.
Use case: Launch several repo tasks at once, let each worker stop only when its goal is grounded, and produce a verified summary of what actually landed.

Quick Start

Use dos-goal-fleet to turn this set of independent objectives into safe waves of workers, with arbitration, witness-gated stopping, and a verified rollup at the end.

Frequently Asked Questions about dos-goal-fleet

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

FAQPage Schema

How do I run parallel git tasks safely without file tree collisions?▼

Parallel git task execution requires wave-based worker orchestration with file tree arbitration to prevent overlapping path writes. This approach batches independent goals to fit available worker seats while keeping same-wave workers isolated.

What is the best way to verify parallel worker completion in a task fleet?▼

Witness verification confirms task fleet completion by requiring git-backed ship evidence and independent read-backs before folding results. This ensures workers only stop when their goal is grounded and prevents false completion claims.

How do I batch independent repository goals to respect a limited worker seat pool?▼

Batching independent repository goals involves wave-based launch planning that decomposes tasks to fit the available worker seat pool. This prevents system overload by safely distributing independent objectives across manageable execution waves.

When do I need file tree arbitration for parallel worker execution?▼

File tree arbitration is needed for parallel worker execution when multiple independent goals risk writing to overlapping repository paths. It ensures same-wave workers are isolated to prevent collisions and maintain git safety.

How does witnessed rollup work for parallel repository task fleets?▼

Witnessed rollup aggregates parallel repository task results by verifying claimed ships with git-backed evidence before folding them into a final report. This process guarantees that only independently verified outcomes land in the summary.