fleet-init

Your objective is to initialize a CocoFleet manifest.

Before proceeding, verify that .cocoplus/ exists. If not: output "CocoPlus not initialized in this directory. Run $pod init to begin." Then stop.

Parse argument: $fleet init [fleet-name] If no fleet-name: output "Usage: $fleet init [fleet-name] — e.g., $fleet init data-pipeline-fleet" Then stop.

Check if coco is available (cross-platform):

On Windows: run where coco via the Bash tool
On Mac/Linux: run which coco via the Bash tool
Alternatively: run coco --version and check the exit code

If coco is not found, output: "ERROR: 'coco' CLI not found in PATH. CocoFleet requires the Coco CLI to be installed and accessible. Install it and ensure it is in your PATH before using CocoFleet." Then stop.

Create directory: .cocoplus/fleet/

Write .cocoplus/fleet/[fleet-name]-manifest.json:

{
  "id": "[fleet-name]",
  "name": "[fleet-name]",
  "version": "1.0",
  "created_at": "[ISO 8601 timestamp]",
  "defaults": {
    "persona": "data-engineer",
    "model": "claude-sonnet-4-20250514",
    "coco_flags": "--no-interactive",
    "timeout_minutes": 60
  },
  "instances": [
    {
      "_comment": "Each instance is an independent Coco process. task_file must be self-contained.",
      "id": "instance-001",
      "name": "Example Instance",
      "persona": "data-engineer",
      "task_file": ".cocoplus/fleet/instance-001/task.md",
      "output_dir": ".cocoplus/fleet/instance-001/",
      "depends_on": [],
      "checkpoints": [".cocoplus/fleet/instance-001/done"]
    },
    {
      "_comment": "Remove this second instance or use it as a template for a dependent stage.",
      "id": "instance-002",
      "name": "Example Dependent Instance",
      "persona": "analytics-engineer",
      "task_file": ".cocoplus/fleet/instance-002/task.md",
      "output_dir": ".cocoplus/fleet/instance-002/",
      "depends_on": ["instance-001"],
      "checkpoints": [".cocoplus/fleet/instance-002/done"]
    }
  ]
}

Output:

CocoFleet manifest created: .cocoplus/fleet/[fleet-name]-manifest.json

To add instances:
  Edit the manifest JSON to add instance definitions.
  Each instance requires:
  - id: unique identifier (e.g., instance-001)
  - task_file: path to a self-contained task.md file
  - checkpoints: glob patterns that must exist when the instance is done

IMPORTANT: Each instance's task_file must be completely self-contained.
The instance runs in a separate Coco process with no shared context.
Document all required inputs, schemas, and context within the task file itself.

Maximum 10 instances per fleet manifest.
Run `$fleet run [fleet-name]` to execute the fleet.

Anti-Rationalization

Shortcut / Temptation	Why It Fails
Create a manifest without verifying `coco` is in PATH	Fleet execution requires the `coco` CLI; a manifest without a working CLI is not executable
Pre-populate instances with real tasks inline	Each instance's task_file must be self-contained in its own file; inlining tasks bypasses the isolation contract
Skip creating the `.cocoplus/fleet/` directory	`$fleet run` expects this directory to exist; missing it causes the first run to fail

Exit Criteria

.cocoplus/fleet/[fleet-name]-manifest.json exists with valid id, defaults, and instances fields
.cocoplus/fleet/ directory exists
coco CLI is confirmed available in PATH before the manifest is written
Output confirms manifest path and explains how to add real instances

About this skill

Anti-Rationalization

Exit Criteria