factory-operatorlisted
Install: claude install-skill The-Zoop-Troop/software-factory-rs
# Factory operator — run the factory day to day
The factory turns a prose plan into an epic of small verified tasks, lands each on the
feature branch, and asks a human only when it is stuck. Your job as operator is five verbs:
**plan → watch → resolve → review → stop**. Everything else here (scaling, upgrades,
backups, troubleshooting) keeps that loop healthy.
**Sources of truth**: `docs/DEPLOYMENT.md` · `docs/guides/first-project.md` ·
`docs/RELIABILITY.md` (failure table + restore drill) · `docs/generated/cli.md` ·
`docs/generated/console-api.md`. When this skill and those disagree, they win.
## Where everything is
- Host: this repository (compose file, images) + `~/.factory` (registry, per-rig
`compose.env` + `rig.env`, `console/` config, `secrets/`).
- Handles: `R="docker compose -p factory-<rig> --env-file ~/.factory/<rig>/compose.env -f compose.yaml"`
— every per-rig command is `$R <verb>`. The console is its own project:
`-p factory-console --env-file ~/.factory/console/compose.env -f ~/.factory/console/compose.yaml`.
- Remote (token in hand): `export FACTORY_RIG=https://<console>/rigs/<rig> FACTORY_TOKEN=…`
then `factory doctor|watch|inbox|plan|stop|metrics` work from anywhere.
## The operating loop
1. **Plan** — write the epic per `references/plan-writing.md` (this is the highest-leverage
document in the skill; a good plan is most of a good run). Submit from the console's Plan
form, `factory plan --text/--file` (add `--queued` to queue on the ledg