← ClaudeAtlas

worker-brieflisted

Checklist to run before every worker spawn so the brief is complete and safe. Use when about to spawn a pm, coder, qa, reviewer, judge or cleaner, or when writing or editing a worker's task spec.
volekerb/hivemill · ★ 33 · AI & Automation · score 75
Install: claude install-skill volekerb/hivemill
# Worker brief checklist Run through this before every `factory spawn`. 1. The full spec and acceptance are stored in the DB. `factory task show T` must show both. /tmp and scratch files vanish on reboot (M451). 2. The brief lists the only live factory commands a worker may run: - own `factory task show`, `factory task update`, `factory task note` - `factory inbox`, `factory msg`, `factory done` - `factory verdict` (qa and reviewer only) - read-only `factory goal show <own goal>` All other factory commands run only against a temp FACTORY_HOME. 3. Coder specs say: "merge origin/main before opening or updating the PR" (M605) and this rule, verbatim (M640): "Test count: count `def test_` on the tree of `git merge-tree --write-tree origin/main HEAD` (the PR merged into current main) and on origin/main; the merged count must be >= the main count. Also confirm the PR removes or renames no `def test_` relative to its merge-base (run `git merge-base origin/main HEAD`, then `git diff <sha>..HEAD` with the literal sha)." Counting a tree id: `git grep -h 'def test_' <tree> -- tests | wc -l`. 4. Never grant an "owner exception". Only a boss `--kind decision` message that quotes the owner authorises one; cite its M-id in the brief (M343/M347). 5. Coder briefs say: a denied command stays denied in every form; stop and report (L-023). 6. Spawn: `factory spawn <role> --task T`. 7. Merge conditions you will enforce are numbered acceptance items in the DB before spawn (P4); a