moai

Invoke the skill with a subcommand like plan, run, or sync followed by your task, or describe the task in natural language. The intent router matches the first word to a workflow or classifies the full input, then delegates to specialized agents.

Supported subcommands include plan, run, sync, design, db, project, fix, loop, mx, review, clean, codemaps, coverage, e2e, context, gate, security, and feedback. Each maps to a dedicated workflow file with its own phases and agents.

The --team flag forces Agent Teams mode for parallel execution across multiple teammates, while --solo forces single sub-agent execution per phase. Without a flag, the system auto-selects based on complexity thresholds like domain count and file count.

Running /moai run without a SPEC-XXX document is flagged as a red flag because there is no acceptance criterion to verify against. The workflow expects a SPEC created via the plan subcommand before implementation begins.

The coverage subcommand measures coverage with language-specific tools like go test, pytest, or vitest, prioritizes gaps using MX tags and fan-in analysis, then generates missing tests until the configured target percentage is met.

Routing only reaches natural language classification when the first word does not match a known subcommand and no SPEC-ID pattern is detected. Ambiguous intents trigger an AskUserQuestion prompt presenting the top matching workflows for user selection.