Execute Fleet
Phase execution skill for licensed Atlas Fleet runs.
Install
npx skills add anombyte93/prd-taskmaster --skill execute-fleet -g -a claude-code -y- Repository
- anombyte93/prd-taskmaster606
- Category
- Git and review
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Mediumabout 2,095 tokens
- Runs scripts
- No, instructions only
What it does
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.
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.
mcp__plugin_prd_go__detect_capabilities()reportstier: "premium"and atlas-launcher MCP registration/aliveness.mcp__atlas-launcher__inbox_readis callable for this session..taskmaster/tasks/tasks.jsonexists..taskmaster/reports/task-complexity-report.jsonexists.git status --shortis empty. Fleet starts only from a committed base.- 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:
