moai-foundation-ears

EARS (Easy Approach to Requirements Syntax) provides five official patterns—Ubiquitous, Event-driven, State-driven, Optional, and Unwanted—to structure clear, testable requirements. Use these patterns to author foundation-domain specifications with consistent syntax and reduced ambiguity across SPEC implementations and code reviews.

The five EARS patterns are: Ubiquitous (always applies), Event-driven (triggered by events), State-driven (conditional on system state), Optional (may apply), and Unwanted (behaviors to prevent). Each pattern enforces a specific grammatical structure to eliminate ambiguity and ensure requirements are testable within foundation projects.

Yes. EARS requirement authoring aligns with TRUST 5 validation workflows and governance standards. The Skill generates automatic EARS rule enforcement and test/lint plans that satisfy TRUST 5 integration requirements for foundation-domain specifications.

Write an EARS-based requirement using one of the five official patterns, then map it to your SPEC using the practical templates and real-world scenarios provided. The Skill supports SPEC-first planning workflows and outputs migration guidance to align requirements with SPEC implementations.

EARS pattern enforcement automates requirement generation and prevents common authoring errors such as ambiguous grammar, testability gaps, and inconsistent syntax. It reduces manual review cycles in code reviews and TRUST 5 validation workflows by enforcing compliance with the five official patterns.

Yes. EARS authoring integrates with test-driven development workflows and generates test plans and lint plans as outputs. Each EARS pattern produces requirements structured for automated testing, enabling TDD processes within foundation projects and code review cycles.