fire

Something went wrong or made the work harder — recorded where it belongs, and if it is the skill's own defect, packaged into a file you can send.

Bring a backlog in from another tracker — the mapping is shown first, and issues arrive unassigned.

A question, not a build: answered as an advisor, with nothing created in your workspace.

Health and opportunities: what burns tokens, what stalls, what drifted, and what the ledger counts as waste.

The toolkit's lifecycle — create from a routine, screen an import, compress fail-closed, release.

Revive after a session limit — interrupted work reruns and resumes rather than restarting.

One job, no company: three questions, one or two agents, build then review.

Use when the user wants to build, bootstrap, join, or operate an autonomous team of AI agents on Multica — you act as their Mops (Executive Advisor)…

The go-live step, whatever live means here: gates green, release notes, tag, announce, ledger.

The urgent lane that jumps the queue — a defect, recall or correction, reproduced before it is fixed.

The console read: what needs you and what happened, with ages and what the wait costs.

Grow the team — an agent built by the role-builder, or a real person by invitation.