mimmo-the-root

UEFN Dream Bot Team — Productivity skill for Claude Code

Productivity community

How to install UEFN Dream Bot Team

This entry records only its repository, not the path inside it, so there is no exact command to give. Open mimmo-the-root/UEFN-dream-bot-team and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What UEFN Dream Bot Team does

"Claude Code multi-agent starter kit for UEFN — twelve specialized subagents (each with one narrow job), a plan-first workflow with two independent review gates, a shared cross-project lessons skill, and an optional real-time Agent Console. Free, documented, works for one island or fifty."

Alternatives in Productivity

Swarm Worker — You are a swarm worker agent for the {{tentacleName}} tentacle 1.4k ★
Jobs — Create, list, edit, or delete cron jobs 1.3k ★
Land A Job — Workflow recipe — go after a specific role end to end by chaining 4 skills: decode the JD, research the compan 1.3k ★

README

UEFN Dream Bot Team

A Claude Code multi-agent starter kit for building UEFN (Unreal Editor for Fortnite) experiences — twelve specialized subagents, each with one narrow job, instead of one general-purpose assistant trying to do everything and stepping on its own toes.

Built by someone juggling ~50 UEFN islands at once. Free, fully documented, works for one island or fifty.

Screenshots

**The Agent Console header** — session stats, token usage, and the "miniflow" rail tracking a task live through its five gated stages (intent-gate → coder → intent-reviewer → compliance-reviewer → planner-docs):

![Agent Console header with the miniflow rail](docs/images/miniflow-rail.png)

**The full Agent Console** — the header above, plus every agent's live status at a glance:

![Agent Console](docs/images/agent-console.png)

**The full pipeline** — every agent and every hand-off, end to end:

![Pipeline diagram](docs/images/pipeline-diagram.png)

What's in the box

Twelve agents, each doing one job: project setup, an independent ambiguity check before any code is written, the actual Verse coding with a mandatory compile-fix loop, two separate review gates (spec adherence, then mechanical rule conformance — never the same agent grading both), regression/bug hunting after every playtest, documentation that stays current, a go/no-go release check, and an optional second-brain (Obsidian) integration for reusable mechanics.
A plan-first workflow: every code change ties to a tracked task, and a task isn't marked done until two independent reviewers have both signed off — no agent grades its own work.
A shared cross-project skill (uefn-lessons) that never resets: something learned fixing a bug on project #12 stops being invisible on project #37.
An optional real-time Agent Console — a local dashboard showing which agent is working, a live "miniflow" rail for the review-gate sequence, MCP server activity, and token usage.
**`mcp-tool-c