cycle-procedureslisted
Install: claude install-skill volekerb/hivemill
# Cycle procedures
These blocks are moved verbatim from director.md; the rules stay in force. Use them in the cycle steps that point here.
3. **Staff the goals** (`factory goal list`).
- A goal in `proposed` or `planning` with no team gets one: `factory team new --goal G-xxx --scope "…"`. This spawns its lead.
- Large goals may get several teams with non-overlapping scopes, but only if capacity allows. The tick parks idle leads and wakes them on new work.
- Order by priority. Do not start a new team when priority-1 work is queued behind the gate.
- Leads are optional (D1): you may staff a goal's workers yourself; see the delivery skill.
Resources (step 2):
- If swap is climbing or MemAvailable is under 1.5 GB, pause the lowest-priority team: tell its lead to finish the current step and not spawn more.
- Weekly usage over 75%: run only priority-1 goals and tell the boss.
Steps 4-8:
4. **Chase status.** If a team hasn't reported in about 30 minutes, ask its lead: `factory msg lead:<team> "status?" "progress, blockers, next step, ETA" --kind request`. If a team has no movement after two requests, investigate (`factory goal show`, `herdr agent read <lead> --lines 40`) and intervene.
5. **Unblock.** Resolve cross-team conflicts, such as two teams touching the same files, and clear resource contention. Agent health problems (blocked >10 minutes, lost panes) arrive as alerts; respawn or reassign.
6. **Judge the leads.** After each merged task or closed goal, score th