moai-workflow-spec

SPEC workflow orchestration automates the creation and management of specification documents by applying EARS patterns (Ubiquitous, Event-Driven, State-Driven, Unwanted, Optional) to drive requirement clarification and Plan-Run-Sync integration. This eliminates fragmented SPEC creation and enables standardized templates with quality gates across parallel development efforts.

EARS (Easy Approach to Requirements Syntax) is a structured pattern framework with five types—Ubiquitous, Event-Driven, State-Driven, Unwanted, and Optional—that standardizes how functional and technical requirements are written. Applying EARS patterns ensures consistent, testable specifications aligned with constitution and Plan-Run-Sync workflows.

Yes. Git Worktrees enable parallel SPEC isolation by allowing multiple branches to be worked on simultaneously without checkout conflicts. The workflow integrates versioned SPECs with worktree-based development, supporting concurrent feature planning and requirement clarification across MoAI-ADK projects.

SPEC workflow orchestration connects generated SPEC documents directly into Plan-Run-Sync integration, enabling a four-step requirement clarification cycle. After SPEC generation, you initiate a Plan run, execute against the specification, then sync progress—creating a closed loop from requirement to test scenario and TDD-ready outputs.

SPEC document generation produces versioned, standardized templates that include test-scenario outputs in TDD-ready formats. These outputs are integrated with Plan-Run-Sync workflows, supporting downstream execution and validation within MoAI-ADK project pipelines.

While EARS pattern experience is beneficial, the workflow includes automated application of all five EARS pattern types as part of the orchestration process. Constitution alignment and standardized templates guide users through requirement clarification without requiring deep prior EARS expertise.