multica-ops

Appearance

multica-ops ​

Mops

Designed and built by Jamil Lazarev.

Mops 🐶 — your Executive Advisor for Multica. One skill that builds and runs an autonomous company of AI agents: it interviews you progressively (small tasks stay small), stands up the workspace-as-company via the CLI — conductor/PM, squads, skills, integrations — optionally stands up a resident Mops inside Multica, and stays your console: status, recovery after limits, features, roadmap, hiring.

Two seats of Mops ​

Mops is one advisor with one name, reachable in two places:

  • Mops in CLI — where you build. Full machine reach (shell, git, multica CLI, deploy), instant chat, its own quota. Best for the heavy work: bootstrap, hire, integrate, ops.
  • Mops in Multica — an optional resident agent carrying this same skill, present in the workspace when you're away from the console. Async, shares the team's session limit; best for status, @Mops advice in an issue, and being the escalation vertex.

They don't share live chat memory, and you can't write into an agent's chat. The bridge is written state — the repo and issue comments — so bootstrap ends with a kickoff handoff (decisions distilled into docs/ + a pinned issue + Mops-in-Multica's first message), and Mops writes decisions as it goes. Test: the project must rebuild from repo + workspace alone. In the CLI while you build; in Multica once you live with a running team.

Install ​

Any agent (universal, via skills.sh):

sh
npx skills add jamillazarev/multica-ops

Claude Code as a plugin (slash commands):

sh
claude plugin marketplace add jamillazarev/multica-ops
claude plugin install multica-ops@multica-ops

Into a Multica workspace:

sh
multica skill import --url github.com/jamillazarev/multica-ops

Then just say what you're making — or /mops <anything>: /mops status, /mops next, /mops add a feature: ….

Why this exists ​

Setup eats the first week. One interview and Mops stands the whole company up — you start working, not configuring roles, prompts, review chains and integrations.

Agent teams die without an operator. A conductor drives the conveyor; Mops stays your console and, optionally, a resident Mops inside Multica for when you're away.

Session limits stall everything silently. Limits are first-class: detection with reset time, /recover, capacity levers, model tiering.

Teams can't grow themselves. The role-builder researches best practices and skills for any role you name — hiring can even run autonomously.

Agents reinvent wheels. Evidence-over-opinion and self-improvement are baked in: research before inventing; a routine repeated twice becomes a skill.

Knowledge scatters. Spec-driven intake (JTBD + stories + acceptance criteria), docs/ as an Obsidian-compatible vault, ROADMAP/TEAM as files in the repo.

One-size teams fit nobody. Everything beyond the invariants is an opt-in module; the progressive interview keeps small tasks small — and every choice accepts "other": name any tool, Mops researches and wires it.

What Mops handles ​

  • The whole product loop — discover → define → prioritize (ICE) → design → build → review (parallel gates) → ship → measure → learn. Closed, not a dead end at merge.
  • The team — hire, fire, and reconfigure agents and real humans; squads; experts & personas; a role-builder; optionally autonomous hiring.
  • Governance — per-member access, human review checkpoints (who signs off where), a budget cap (tokens or money).
  • Staying alive — session-limit recovery, a full-circle health check (runtimes, integrations, API tokens), git-backed skill upgrades with rollback, two-way drift sync, assisted provider switch.
  • Two seats, many workspaces — Mops in CLI for building, an optional Mops in Multica for presence, across several workspaces.
  • Cost visibility — a per-release cost/effort ledger (tokens · $ · time · per agent/human) in git and on the issue.

Where to go next ​