moai-foundation-core

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

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-foundation-core-seung-zedd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-foundation-core
Source: https://github.com/Seung-zedd/secure-file-upload/tree/main/.claude/skills/moai-foundation-core
Command: npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-foundation-core-seung-zedd

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 untracked changes, token waste, and unverified 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-format SPEC, delegate implementation to manager-develop with 85% coverage enforcement, and keep context under budget with progressive disclosure. ## Quick Start Ask the AI to apply the MoAI foundation principles to plan a new feature with a GEARS-format SPEC and TRUST 5 quality gates.

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 (formatter consistency), Secured (OWASP compliance), and Trackable (conventional commits). All five dimensions must pass before work is considered complete.

How does the SPEC-First DDD workflow operate?▼

It runs three phases: /moai plan generates a GEARS-format SPEC, /moai run implements via ANALYZE-PRESERVE-IMPROVE cycles, and /moai sync produces documentation. Executing /clear after planning saves 45-50K tokens for the implementation phase.

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. EARS is a legacy reference kept for six-month backward compatibility with 88 pre-v3 SPECs, expiring 2026-11-22; new SPECs must use GEARS.

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

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

Which agents can MoAI delegate tasks to?▼

MoAI delegates to a flat catalog of 11 retained agents including manager-spec, manager-develop, manager-docs, manager-git, plan-auditor, sync-auditor, builder-harness, super-advisor, manager-design, e2e-tester, and the built-in Explore agent. Archived tiered agent names are rejected at spawn.

What are the limitations of the progressive disclosure structure?▼

SKILL.md files must stay under 500 lines, splitting overflow into modules/ directories. This adds navigation overhead for deep topics, since detailed content requires following cross-references into module files rather than reading a single document.