fleet-plan
Fleet Plan
Analyze work, pick the right fleet type, generate fleet.json + worker prompts. You plan — the fleet skills execute.
Step 0: Discover available fleet types
Before planning, read the fleet index to know what's available:
- Find the index:
Globfor**/fleet/FLEET-INDEX.md(or look in the same parent dir as this skill) - Read
FLEET-INDEX.md— it has a table of all fleet types with one-liner hints on when to use each - Based on the hints, pick the best fleet type for the user's task
- Then read ONLY the chosen fleet's
SKILL.mdfor the full schema:Globfor**/<chosen-fleet>/SKILL.md
This is a two-step lookup: cheap index first (one small file), full schema second (one SKILL.md). Never read all fleet SKILL.md files — that wastes context.
Step 0.5: Verify prerequisites
Before generating the fleet, warn the user if any prerequisite is missing:
More from quickcall-dev/skills
doc
Create and manage structured documentation — experiments, plans, findings, checkpoints, research, learnings. Config-driven, parallel-safe.
30worktree-fleet
Independence-validated parallel fleet that runs each worker (claude -p, codex exec, or pi -p) in its own git worktree. Use when tasks touch non-overlapping files and you need merge-safe isolation (each worker on its own branch). For DAG-ordered one-shot workers with budgets, use dag-fleet. For headless iteration with a reviewer loop, use iterative-fleet.
30dag-fleet
Persistent, budgeted, DAG-ordered runner for parallel `claude -p`, `codex exec`, or `pi -p` workers in tmux. Use ONLY when you need persistence across sessions, per-worker budget caps, dependency ordering, or mixed models/providers per worker. For ad-hoc parallel sub-agents inside a live conversation, use Claude Code's built-in Agent tool instead.
29iterative-fleet
Reviewer-gated iterative fleet for headless `claude -p`, `codex exec`, or `pi -p` workers that run in cycles until a designated reviewer approves the output. Use when the work needs multiple rounds of iteration with a quality gate — a reviewer worker reads all worker logs, writes a verdict (lgtm | iterate | escalate), and the orchestrator decides whether to continue, pause, or stop. NEVER kills or restarts workers automatically; the operator owns all kill/pause decisions.
29autoresearch-fleet
Karpathy-inspired autonomous research loop. Agent edits one file, evals, keeps or discards, repeats. Plateau-triggered web search breaks through ceilings. Git as state machine. Runs until stopped or budget exhausted. Supports claude, codex, and pi providers.
29