fleet-expansion
description (verbatim frontmatter)
Batch-scaffold, deploy, and register MANY new Cloudflare Worker sites at once across the subagent*.com / agent*.com family, coordinated through a Postgres deploy ledger instead of conversation context. Use when launching workers for multiple owned-but-unserved domains in one pass — "deploy workers for the domains I own", "launch the rest of the fleet", "fill the unserved zones". Composes (never duplicates) the single-site skills: cwc-engineering:worker-build builds ONE worker, cwc-deploy:deploy-playbook/deploy-runner ship ONE worker — this skill owns only what batching adds: the typed fleet manifest, up-front accent allocation, the wave protocol with its serialization rules, the fact_fleet_deploy ledger, and batch verification. Do NOT use for a single new site (deploy-playbook alone is simpler) and do NOT let any wave edit workers/_shared/kit/ (a kit edit mid-batch is a 66-lock fleet relock event).
summary
Batch-scaffold, deploy, and register MANY new Cloudflare Worker sites at once across the subagent*.com / agent*.com family, coordinated through a Postgres deploy ledger instead of conversation context.
source
plugins/cwc-deploy/skills/fleet-expansion/SKILL.md
provenance
created 2026-07-10 18:13:13 · JSON