umacloud / umadev

What it does

• Deeply integrates the base you already use. All five are equal, first-class, deeply adapted bases. Claude Code, Codex, and OpenCode keep their vendor-specific protocol drivers; Grok Build and Kimi Code use their official ACP v1 interfaces t
• Role-based team orchestration. For work whose depth warrants it, eight specialist roles — product manager, architect, UI/UX designer, frontend engineer, backend engineer, QA, security, and DevOps — receive bounded assignments and return typ
• Plans the work and shows it. A build becomes a dependency plan (.umadev/plan.json) rendered as a live checklist you can steer with /plan. Steps are driven step by step; the coordinator owns the plan, not the base.
• One governed Build contract. A Build routed from chat and one started with umadev run both enter the owned Director path; planning, role scheduling, checks, and artifacts scale with depth and observed evidence.
• Produces delivery evidence when the floor passes. A clean, sufficiently deep delivery can include PRD, architecture, UI/UX, a scorecard, and a proof pack. A small edit gets targeted verification, while a failed or incomplete plan is reporte