Moai
>
Try it out
How it works
Pre-execution Context
!git status --porcelain 2>/dev/null || true
!git branch --show-current 2>/dev/null || true
Essential Files
.moai/config/config.yaml
Authority References
Rules and constraints governing all workflows are always loaded from these sources. Do NOT duplicate their content here:
- Core identity, orchestration principles, agent catalog: CLAUDE.md
- Quality gates, security boundaries: .claude/rules/moai/core/moai-constitution.md
- SPEC workflow phases, token budgets: .claude/rules/moai/workflow/spec-workflow.md
- Development methodologies (DDD/TDD): .claude/rules/moai/workflow/workflow-modes.md
- Agent definitions: See CLAUDE.md Section 4. For agent creation, use builder-agent subagent.
- @MX tag rules and protocol: .claude/rules/moai/workflow/mx-tag-protocol.md
Intent Router
Raw User Input
$ARGUMENTS
Routing Instructions
[HARD] Route the Raw User Input above using the strict priority order below. Extract the FIRST WORD of the input for subcommand matching. All text after the subcommand keyword is CONTEXT to be passed to the matched workflow — it is NOT a routing signal and MUST NOT influence which workflow is selected.
Execution Mode Flags (mutually exclusive)
--team: Force Agent Teams mode for parallel execution--solo: Force sub-agent mode (single agent per phase)- No flag: System auto-selects based on complexity thresholds (domains >= 3, files >= 10, or complexity score >= 7)
When no flag is provided, the system evaluates task complexity and automatically selects between team mode (for complex, multi-domain tasks) and sub-agent mode (for focused, single-domain tasks).
Priority 1: Explicit Subcommand Matching
[HARD] Extract the FIRST WORD from the Raw User Input section above. If it matches any subcommand below (or its alias), route to that workflow IMMEDIATELY. Do NOT analyze the remaining text for routing — it is context for the matched workflow:
- plan (aliases: spec): SPEC do...