What is the EARS format used in this skill?

EARS stands for Easy Approach to Requirements Syntax. It uses five specific patterns—Ubiquitous, Event-Driven, State-Driven, Unwanted, and Optional—to ensure that all requirements are clear, testable, and unambiguous.

How do SPEC lifecycle levels work?

The skill defines three levels: spec-first (discarded after use), spec-anchored (maintained alongside code), and spec-as-source (the single source of truth for code generation).

How does this skill support parallel development?

It leverages Git Worktree integration via the --worktree flag, allowing the AI to create isolated working directories for different SPECs. This enables working on multiple features simultaneously without the risks of branch switching.

What is the Plan-Run-Sync integration?

It is a three-phase workflow: PLAN (analyzing requirements and creating SPECs), RUN (executing TDD cycles to implement the code), and SYNC (synchronizing documentation and version control history).

MoAI SPEC Workflow Orchestration

Name: MoAI SPEC Workflow Orchestration
Author: modu-ai

bymodu-ai

•

Productivity & Workflow

Orchestrates comprehensive software requirement specifications using the EARS format and Plan-Run-Sync integration for systematic development.

About

The moai-workflow-spec skill implements the MoAI-ADK development methodology to transform natural language feature requests into structured, unambiguous SPEC documents. By utilizing the Easy Approach to Requirements Syntax (EARS), it eliminates requirement ambiguity across five distinct patterns. The skill facilitates the entire development lifecycle—from root cause analysis and assumption validation to automated SPEC generation and Git Worktree isolation for parallel development. It ensures every feature aligns with the project's technical constitution and quality gates before implementation begins.

Key Features

Automated SPEC document generation with standardized metadata and lifecycle levels
EARS-compliant requirement patterning (Ubiquitous, Event-Driven, State-Driven, Unwanted, Optional)
Systematic four-step clarification process with root cause and assumption analysis
Integrated Git Worktree support for isolated parallel feature development
16 GitHub stars
Quality gate validation using the TRUST 5 framework and measurable success criteria

Use Cases

Defining structured requirements for complex features to prevent scope creep
Managing parallel development of independent features without branch-switching overhead
Enforcing architectural and security standards across team-wide specifications

About

Key Features

Automated SPEC document generation with standardized metadata and lifecycle levels
EARS-compliant requirement patterning (Ubiquitous, Event-Driven, State-Driven, Unwanted, Optional)
Systematic four-step clarification process with root cause and assumption analysis
Integrated Git Worktree support for isolated parallel feature development
16 GitHub stars
Quality gate validation using the TRUST 5 framework and measurable success criteria

Use Cases

Defining structured requirements for complex features to prevent scope creep
Managing parallel development of independent features without branch-switching overhead
Enforcing architectural and security standards across team-wide specifications