moai-foundation-core

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-assisted development often lacks consistent quality gates, clear requirement specifications, and disciplined context management, leading to untested code, token overflow, and uncoordinated agent work. 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 checkpoints. - Use Case: When starting a new feature, generate a GEARS-format SPEC with acceptance criteria, clear context, then delegate implementation to manager-develop with TRUST 5 validation before merging. ## 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 framework in MoAI-ADK?▼

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

How does the SPEC-First DDD workflow work?▼

The workflow has three phases: /moai plan generates a GEARS-format SPEC document, /moai run implements it via ANALYZE-PRESERVE-IMPROVE cycles, and /moai sync produces documentation. You must run /clear after planning to free 45-50K tokens for implementation.

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

GEARS is the current notation with five patterns including Where capability gates and event-detected failure handling, using a generalized subject. EARS is a legacy reference kept for 6-month backward compatibility with 88 pre-v3 SPECs, expiring 2026-11-22.

How does agent delegation work in MoAI-ADK?▼

MoAI never executes work directly; it delegates through natural-language prompts to a flat catalog of 11 retained agents like manager-spec, manager-develop, and manager-docs. Legacy tiered agent names are archived and rejected at spawn.

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

Run /clear immediately after /moai plan completes, when context exceeds 150K tokens, or after 50+ messages. Before clearing, persist session state to progress.md so work can resume cleanly.

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 prevents context overflow within the 200K window.