umacloud

Umadev — Development skill for Claude Code

Development community

UmaDev: A coding agent that works like a real dev team, commanding the Claude Code / Codex / OpenCode you already use.

How to install Umadev

This entry records only its repository, not the path inside it, so there is no exact command to give. Open umacloud/umadev and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Umadev does

UmaDev: A coding agent that works like a real dev team, commanding the Claude Code / Codex / OpenCode you already use.

Alternatives in Development

  • Hapi — App for Claude Code / Codex / Gemini / OpenCode, vibe coding anytime, anywhere 3.6k ★
  • Agent Of Empires — Manage multiple Claude Code, OpenCode agents from either TUI or Web for easy access on mobile 3.1k ★
  • Claude Scholar — Semi-automated research assistant for academic research and software development 3k ★

README

umadev

umadev

UmaDev: A coding agent that works like a real dev team, commanding one of five AI coding CLIs you already use.

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) [![Rust](https://img.shields.io/badge/Rust-1.88%2B-orange)](https://www.rust-lang.org/) [![Spec](https://img.shields.io/badge/Spec-UMADEV__HOST__SPEC__V1-blue)](spec/UMADEV_HOST_SPEC_V1.md) [![Version](https://img.shields.io/badge/Version-1.0.x-success)](CHANGELOG.md)

English | [简体中文](README.zh-CN.md) | [繁體中文](README.zh-TW.md)


umadev is **a coding agent that works like a real dev team**. It drives one of five first-class AI coding CLIs you already have — Claude Code, Codex, OpenCode, Grok Build, or Kimi Code — and owns no model endpoint of its own: the model your selected base is connected to is the brain.

What you get is **role-based team orchestration** over that borrowed brain. For work whose depth warrants it, bounded sessions take product, architecture, UI/UX, frontend, backend, QA, security, and DevOps assignments; a small edit stays a small edit. These roles are not independent people and their verdicts are advisory. UmaDev owns the plan and deterministic acceptance floor, produces depth-appropriate artifacts/evidence, and reports failed or incomplete work honestly rather than promising that every request becomes shippable software.

A ninth seat, the **coordinator**, routes the request, owns a visible plan for deliberate work, schedules the selected roles, evaluates gates, and leaves the audit trail. It doesn't generate code; the base CLI does. Roles exchange bounded blackboard artifacts and structured verdicts rather than free-form cross-talk.

It's a single Rust binary. npm is just the delivery shell.


Table of Contents