Orchestration layer above /implement, split by when it runs:

dispatch <label>: start of a wave. Read dispatch.md.
land <label>: optional, when dispatch's --check recommends it, before the user merges. Read land.md.
reconcile <label>: after the wave's PRs have merged. Read reconcile.md.

All subcommands require a feature label as the argument after the subcommand (for example /fleet dispatch cv-tailoring). If it is missing, ask for it; never run across all issues. Read the file for the subcommand in the first argument. With no subcommand, use reconcile if the user says the wave has merged, otherwise dispatch. If it is still unclear, ask.

Shared conventions

An issue whose changes are all under skills/ is still dispatched through /implement, which hands it to skill-updater.

Both halves rely on these, so they are defined once here.