execute-fleet
Phase execution skill for licensed Atlas Fleet runs. Use when HANDOFF has selected Atlas Fleet and the project should be executed across isolated launcher worktrees with inbox-based result collection, verified CDD cards, sequential integration merges, and one final PR.
npx skills add anombyte93/prd-taskmaster --skill execute-fleet --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# execute-fleet Atlas Fleet is the premium parallel sibling of `execute-task`. It keeps the same proof discipline, but the orchestrator owns the scoreboard while workers only build inside isolated worktrees. ## Hard Gates Before the first wave, all gates must pass. If any gate fails, report the gap and stop; do not fall back to solo execution from inside this skill. 1. `mcp__plugin_prd_go__detect_capabilities()` reports `tier: "premium"` and atlas-launcher MCP registration/aliveness. 2. `mcp__atlas-launcher__inbox_read` is callable for this session. 3. `.taskmaster/tasks/tasks.json` exists. 4. `.taskmaster/reports/task-complexity-report.json` exists. 5. `git status --short` is empty. Fleet starts only from a committed base. 6. The integration branch policy is clear: use `fleet-integration`; main is never auto-touched. **SOLE-WRITER RULE:** only this orchestrator writes `.taskmaster/tasks/tasks.json` and `.atlas-ai/state/pipeline.json`. Workers must never edit those files. The orchestrator may update task state only through TaskMaster or the plugin pipeline MCP, and only after verification. ## Wave Loop Repeat until no runnable tasks remain: 1. Call `mcp__plugin_prd_go__compute_flee
- Hard Gates
- Wave Loop
- Worker Prompt Template
- Failure Paths
- Status Rendering
- Termination
- Non-Exits
python3 skel/ship-check.py
What does the execute-fleet skill do?
Phase execution skill for licensed Atlas Fleet runs. Use when HANDOFF has selected Atlas Fleet and the project should be executed across isolated launcher worktrees with inbox-based result collection, verified CDD cards, sequential integration merges, and one final PR.
How do I install it?
Run `npx skills add anombyte93/prd-taskmaster --skill execute-fleet --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From anombyte93/prd-taskmaster, a repository with 586 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.