moai

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

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-jjjh7401
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai
Source: https://github.com/jjjh7401/AI-Lighting_Console/tree/main/.claude/skills/moai
Command: npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-jjjh7401

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating a full software development lifecycle — planning SPECs, implementing with TDD, syncing documentation, reviewing code, and running E2E tests — requires knowing which agent and workflow to invoke for each task. This Skill acts as a unified orchestrator that interprets natural language or explicit subcommands and dispatches the correct specialized agent pipeline automatically. ## Core Features & Use Cases - Intent-Based Routing: Classifies natural language input (including Korean, Japanese, and Chinese) or explicit subcommands (plan, run, sync, fix, loop, review, clean, e2e, gate, goal, todo, and more) into the correct workflow using a strict priority router. - Full Development Pipeline: Orchestrates SPEC creation, DDD/TDD implementation, documentation sync, code review, dead-code removal, architecture codemaps, and multi-platform E2E testing with quality gates and human approval checkpoints. - Safety and Observability: Enforces flag-subcommand compatibility validation, mandatory kickoff approvals before implementation, and an opt-in append-only routing ledger that records privacy-preserving digests of dispatch decisions. - Use Case: A developer types "/moai fix the failing lint errors in the auth module" and the orchestrator routes to the fix workflow, delegates to the appropriate agent, tracks tasks, and reports verified results. ## Quick Start Ask the assistant to run "/moai plan" followed by a description of the feature you want to specify and build.

Frequently Asked Questions about moai

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

FAQPage Schema
How do I route a natural language request to a development workflow?▼

Type your request in plain language after the moai command, such as "/moai implement user login". The intent router classifies the entire message semantically and dispatches the matching workflow, falling back to a clarification question when intent is ambiguous.

What subcommands does the moai orchestrator support?▼

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

Does the router work with Korean or other non-English input?▼

Yes, intent classification is semantic and language-independent, so Korean, Japanese, or Chinese requests route identically to English ones. A mixed-language guard prevents English loanwords at sentence start from triggering false subcommand matches.

Why was my --branch flag rejected with /moai run?▼

The --branch flag is only allowed with plan and the default autonomous workflow. Run and sync must reuse the branch created during plan, so the router stops with an error explaining the correct usage before any processing continues.

Can the orchestrator start implementation without my approval?▼

No, Implementation Kickoff Approval is mandatory at the plan-to-run boundary in every mode. Derived completion conditions and autonomous loops never bypass this human gate.

What happens when the routing ledger recording fails?▼

Ledger recording is opt-in and fail-open, so a missing CLI or non-zero exit is silently ignored and never blocks routing. An empty ledger indicates an un-recorded dispatch, not that observability is disabled.