dept-spawnerlisted

Spawn a new Bubble ops department (agent) end-to-end — create the repo, scaffold the dept tree, wire the VPS prerequisites, and hand off to the self-driving onboarding. Use this whenever the user wants to create/spawn/hatch/onboard a NEW agent or department (like Ben the fund manager or Geraldine the accountant), set up a new dept's repo + systemd unit + Telegram bot + secrets, or asks "add a new agent/dept", "spin up a department for X", "onboard a new ops agent". This orchestrates the EXISTING scaffolding (bootstrap-dept.sh + scaffold.py + the self-driving onboarding skill) — it does not reinvent the process. Do NOT use for editing an existing live dept (that's a normal PR) or for non-agent infra.
Bubble-invest/bubble-ops-loop · ★ 0 · AI & Automation · score 68

Install: claude install-skill Bubble-invest/bubble-ops-loop

# Dept-Spawner — orchestrate a new Bubble department from zero to live Spawning a department is **mostly already automated** (bootstrap-dept.sh + scaffold.py do the repo+tree, the dept's own `CLAUDE.md` self-drives a 7-step onboarding over Telegram, and activate-dept.sh opens the go-live PR). This skill is the **thin orchestrator** that runs those pieces in the right order and fills the ~6 steps that still need a human/operator hand — so you don't rediscover the sequence (and its footguns) every time, the way it was done by hand for Ben and Geraldine. **You are the operator, not the newborn agent.** Your job is Phases 1–2 + 4 (scaffold, wire the VPS, activate). Phase 3 (the actual mandate/missions/layers) is driven by the NEW agent itself, with the human approving — you don't hand-write its mandate. ## The model (one spawn, start to finish) ``` Phase 0 decide: slug · display name · level (ops|management) · domain scope · creds strategy Phase 1 scaffold: bootstrap-dept.sh → repo + onboarding/<slug> branch + 16-file tree + vendored libs Phase 2 wire VPS: the 6-ish manual prereqs (BotFather bot, SOPS secrets, channel dir, folder-trust, watchdog, broker policy) + deploy-to-morty.sh + clone to agents/ Phase 3 self-drive: the NEW agent runs its 7-step éclosure over Telegram; human approves each Phase 4 activate: activate-dept.sh → PR onboarding/<slug> → main → human merges → live Phase 5 domain: post-live, wire the dept's domain-specific skills/tools