moai-foundation-core

Defines TRUST 5 quality gates, SPEC-First DDD workflow, and agent delegation patterns for MoAI-ADK.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-driven development often lacks consistent quality gates, clear requirement specifications, and disciplined context management, leading to untracked changes, token overflow, and unvalidated code. This Skill provides the foundational principles of MoAI-ADK so every change follows a specification-first, quality-gated, agent-delegated workflow. ## Core Features & Use Cases - TRUST 5 Quality Framework: Enforces five hard quality gates (Tested, Readable, Unified, Secured, Trackable) with test coverage thresholds, linting, formatting, OWASP security checks, and conventional commit validation. - SPEC-First DDD Workflow: Structures development into three phases (/moai plan, /moai run, /moai sync) using GEARS-format requirements and ANALYZE-PRESERVE-IMPROVE implementation cycles. - Delegation & Token Management: Routes all work through a flat catalog of 11 retained agents via natural-language delegation, with phase-based token budgets (30K/180K/40K) and mandatory /clear points. - Use Case: When starting a new feature, load this Skill to generate a GEARS SPEC, delegate implementation to manager-develop with 85% coverage enforcement, and validate the result against all five TRUST 5 dimensions before merge. ## Quick Start Ask the AI to explain the TRUST 5 quality gates and how to structure a new feature using the SPEC-First DDD workflow.

Frequently Asked Questions about moai-foundation-core

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

FAQPage Schema
What is the TRUST 5 quality framework?▼

TRUST 5 is a hard quality gate system with five pillars: Tested (85% coverage minimum), Readable (linter compliance), Unified (formatter consistency), Secured (OWASP standards), and Trackable (conventional commits). All five dimensions must pass before code can merge.

How does SPEC-First DDD development work?▼

SPEC-First DDD runs in three phases: /moai plan generates a GEARS-format specification, /moai run implements it via ANALYZE-PRESERVE-IMPROVE cycles, and /moai sync produces documentation. A /clear between plan and run phases saves 45-50K tokens.

What is the difference between GEARS and EARS requirement formats?▼

GEARS is the current notation with five patterns including a generalized subject and compound Where/While/When clauses. EARS is a legacy reference kept for 6-month backward compatibility with 88 pre-v3 SPECs, expiring 2026-11-22; new SPECs must use GEARS.

When should I execute /clear during the MoAI workflow?▼

Execute /clear immediately after /moai plan completes, when context exceeds 150K tokens, or after 50+ messages. Never clear in the middle of an agent task or before persisting session state to progress.md.

Can MoAI execute code directly instead of delegating to agents?▼

No. MoAI is an orchestrator that must delegate all work through Agent() to one of 11 retained agents such as manager-spec, manager-develop, or manager-docs. Direct execution bypasses specialization, quality gates, and token optimization.

What are the token budget limits for each development phase?▼

The phase budgets are 30K tokens for SPEC planning, 180K for DDD implementation, and 40K for documentation, totaling 250K per feature. Phase separation with /clear between stages prevents context overflow.