moai

Routes natural language and subcommands to specialized agents for autonomous development workflows.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-seung-zedd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai
Source: https://github.com/Seung-zedd/secure-file-upload/tree/main/.claude/skills/moai
Command: npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-seung-zedd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multi-phase software development work—specification writing, TDD implementation, documentation sync, code review, and testing—requires deciding which agent and workflow to invoke for each request. This Skill acts as a unified orchestrator that classifies user intent and dispatches to the correct specialized workflow automatically. ## Core Features & Use Cases - Intent Routing: Parses subcommands (plan, run, sync, fix, loop, review, clean, e2e, gate, goal, todo, and more) or classifies natural language in any language to select the right workflow, with a mixed-language guard for CJK inputs. - Full Development Pipeline: Supports the complete plan → run → sync lifecycle with SPEC-driven development, DDD/TDD implementation, quality gates, and human approval checkpoints at critical boundaries. - Specialized Workflows: Includes dead-code removal, architecture codemap generation, multi-platform E2E testing (Playwright, Maestro, WebdriverIO), MX tag annotation, backlog management, and condition-declared agentic loops. - Use Case: A developer types "/moai plan add user authentication" and the orchestrator routes to the SPEC creation workflow, then chains into implementation and documentation sync with approval gates. ## Quick Start Ask the assistant to run "/moai plan" followed by a description of the feature you want to build, and it will route your request to the specification workflow.

Frequently Asked Questions about moai

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route a development task to the right workflow?▼

Start your request with a subcommand like plan, run, sync, fix, or review, or write a natural language description. The orchestrator extracts the first word for subcommand matching, then falls back to semantic intent classification across the entire message.

What subcommands does the MoAI orchestrator support?▼

It supports plan, run, sync, project, feedback, fix, loop, mx, review, clean, codemaps, gate, e2e, harness, goal, and todo. Each maps to a dedicated workflow file with its own phases, agents, and flags.

Does intent routing work with Korean or Japanese input?▼

Yes, natural language classification is semantic and language-independent. A mixed-language guard prevents misfires when CJK sentences begin with English loanwords like 'goal' or 'fix', routing only on the full message intent.

Can I run E2E tests for mobile and desktop apps?▼

Yes, the e2e subcommand auto-detects web, mobile, desktop, and desktop-native project types, then selects CLI-first toolchains such as Playwright, Maestro, WebdriverIO with tauri-service, or platform accessibility tools.

Why does the orchestrator ask for approval before implementation?▼

Implementation Kickoff Approval is a mandatory human gate at the plan-to-run boundary. It ensures high-risk decisions like entering autonomous implementation remain under human control even when a completion condition is defined.

What happens when the routing intent is ambiguous?▼

The orchestrator uses AskUserQuestion to present the top two or three matching workflows so the user can choose. If the request is clearly a development task without a routing signal, it defaults to the full plan-run-sync pipeline.