wilson-works · claude_skills

The Agent Org

A small software company made of agents — direction, routing, review, and shipping.
18 agents
1 engineering branch
3 hard-ACL channels
drives marathon-org · workday
Click any person to open their profile card — what they’re for, their personality, hands-on vs advisory · browse the whole team →

Chain of command — the org chart

Classical top-down waterfall: every line is a real reporting relationship. Click any box to open their profile card.

CEO(you) JamesCTO · direction TimExec Assistant · routes John ⚖Chief Engineer · gate CindyBackend GavinFrontend DianaDatabase RachelQA JoshAPI Marcusbackend Avafrontend Leodatabase OwenQA FelixAPI Priyabackend Kaifrontend Noradatabase MayaQA ZaraAPI

John is the review gate. He sits in the C-suite but answers to no department — every diff passes through him before merge, so a head can't approve their own team's slop.

The comms bus & the hard ACL

Every tier has its own SQLite-backed channel. The walls are enforced, not polite — and a path-guard hook blocks any agent from editing outside its territory.

#c-suite

James
John
Tim
ceo (label for posts to you)

#dept-heads

Tim
Cindy · Gavin · Diana
Rachel · Josh

#dev-floor

the 5 heads
+ 10 juniors
claims · hand-offs
Hard ACL: a junior cannot post to the CTO. Tim is the only agent on both c-suite and dept-heads; heads bridge down to the floor. Before any edit, an agent claims the file so two agents never fight over it.

How a work order runs — the loop

A loop, not a line: John bounces weak work back with reasons; it re-enters at “implement”. It only exits when John approves and the suite is green.

01
Backlog WO
02
James prioritizes
03
Tim routes
04
Head briefs
05
Junior implements
06
Head pre-review
07
John · merge gate
08
Merge & log
Execution model: in this environment a sub-agent can’t spawn another sub-agent, so the top-level session does all the spawning. The chain above is the accountability model, not a call stack — review gates and named ownership stay; only the spawn-theater is dropped.

The parallel loop — /workday

Four loops at once, each in its own git worktree (zero write collisions), merged in dependency order. /workday-watch is an optional fifth session that keeps them honest in real time.

A
schema / db
B
backend
C
frontend
D
api
Lane E — auto-merge a → b → d → c · verify · clean up · archive
👁 /workday-watch reads each lane’s state & comms and posts [WATCH] steering the lanes obey — catching drift in ~20 min instead of at the morning merge. Optional; the four lanes + Lane E run fine without it.