Agent Creation Queue — Next Session Priority
Step 0: Create Ossie & Ruby (BY HAND — last time ever)
They are the agent creators. Every agent after them goes through /create-agent.
- Ossie (Ossie Davis) — Structure: agent def, command, skills, tools, registry
- Ruby (Ruby Dee) — Identity: name, avatar, 3D page, story, personality
- Command:
/create-agent - Both are workers dispatched via Cursor
Step 1: Session Agents (male + female pair — sibling commands)
/session-start— reads memory, checkpoint, Slack, sets the stage/session-end— writes checkpoint, summarizes, flags unfinished work- Need a male agent for one, female for the other (Maat balance)
- Sibling commands = sibling agents
Step 2: Build Agent (needs name from Ossie & Ruby)
- Handles ALL local EAS builds on QC1
- Command:
/build-mobile - Knows:
--local,--non-interactive, Fastlane timeouts, keychain unlock, Apple creds - After build:
eas submit(FREE) to TestFlight - Lewis was already taken (Docker) — Ossie & Ruby pick the name
Step 3: QC1 Agent (needs name from Ossie & Ruby)
- Knows everything about the Mac M4 Pro machine
- Keychain password, SSH config, Tailscale IP, disk space
- Ollama models, installed CLIs, project paths
- Node.js version, Xcode version, EAS CLI version
- Can diagnose machine issues, restart services, clean caches
Rule
- All agents created through
/create-agent(Ossie & Ruby) - Every agent gets Maat balance (male/female counterpart noted)
- Names come from Black historical figures (checked against registry)
- Every agent gets: command, agent def, skills, avatar, 3D page, story