init-swarmlisted
Install: claude install-skill the-cloud-clockwork/agentihooks
# Init Swarm
The plan is accepted before this skill runs. This session names the swarm,
creates it with its ledger and starts it, then hands the operator to the swarm's **master**: the
agent the swarm keeps online to answer the operator, keep the ledger current
and steer the swarm. This session never claims a task and does not join the
ledger as orchestrator; the master does.
## Plans versus standalone tasks
- A full plan is a plan file a master or planner writes and publishes to the
artifacts; every task built from it carries its slice.
- Follow ups, open questions, operator notes and orders the operator types or
gives are standalone tasks with no plan and no slice.
- A standalone task that a master or planner expands because it grew wide
becomes a plan: write and publish the plan with slice markers, then add its
tasks with their slices.
- Small self explanatory changes, such as a style tweak or a loose layout
change, stay standalone and never get a plan.
## 1. Name the swarm
A swarm name is one or two lowercase words joined by a dash and ending in
swarm, such as `rig-grade-swarm` or `dating-swarm`; it is also the ledger's
name. Ask the operator for it with the question tool, offering two or three
suggestions built from the plan title. Check every suggestion before you offer
it, and the operator's answer before you use it:
```bash
agentihooks swarm names check <name> --plan <plan-file>
```
It prints `valid: <name>`, or `invalid:` with the reason, the rule an