moai-workflow-spec

Orchestrate SPEC workflow management with EARS requirements and Plan-Run-Sync integration.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/taewook486/real-estate-mcp --skill moai-workflow-spec-taewook486
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-workflow-spec
Source: https://github.com/taewook486/real-estate-mcp/tree/main/.claude/skills/moai-workflow-spec
Command: npx skills add https://github.com/taewook486/real-estate-mcp --skill moai-workflow-spec-taewook486

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured framework for defining, managing, and orchestrating software specifications using the EARS format, ensuring clarity, consistency, and seamless integration into the Plan-Run-Sync development lifecycle.

Core Features & Use Cases

  • EARS Requirement Definition: Enforces the use of five distinct EARS patterns (Ubiquitous, Event-Driven, State-Driven, Unwanted, Optional) for unambiguous requirement specification.
  • SPEC Lifecycle Management: Guides the creation, refinement, and validation of SPEC documents through defined stages and quality gates.
  • Plan-Run-Sync Integration: Facilitates a cohesive workflow from planning and implementation to synchronization and documentation.
  • Parallel Development Support: Enables parallel feature development using Git Worktrees for isolated environments.
  • Use Case: When initiating a new feature, use this Skill to generate a comprehensive SPEC document that clearly outlines requirements, acceptance criteria, and implementation plans, ensuring all stakeholders have a shared understanding before development begins.

Quick Start

Use the moai-workflow-spec skill to create a new SPEC document for a user authentication system.

Frequently Asked Questions about moai-workflow-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write software requirements using the EARS format?

EARS format requirements use five distinct patterns—Ubiquitous, Event-Driven, State-Driven, Unwanted, and Optional—to create unambiguous software specifications. This approach enforces clarity and consistency when defining SPEC documents for complex feature development.

What's the best way to manage SPEC documents for parallel feature development?

Managing SPEC documents for parallel development is streamlined using Git Worktrees to create isolated environments. This workflow integrates with Plan-Run-Sync cycles, allowing teams to define requirements and implement features concurrently without conflicts.

How do I formulate acceptance criteria for SPEC lifecycle management?

Acceptance criteria formulation in SPEC lifecycle management is driven by EARS requirement definitions and validated through quality gates. This ensures that feature plans meet specified conditions before progressing through the development stages.

Does MoAI-ADK support EARS requirement patterns for feature planning?

MoAI-ADK supports EARS requirement patterns directly within its Plan-Run-Sync development lifecycle. This integration facilitates orchestrating SPEC documents, defining EARS requirements, and executing feature planning seamlessly.

When do I need to use EARS patterns for software specification?

EARS patterns are needed when initiating a new feature that requires a comprehensive SPEC document outlining clear requirements and acceptance criteria. They ensure all stakeholders share a unified understanding before development begins.

Why use EARS over standard user stories for requirements definition?

EARS provides five distinct structural patterns that enforce unambiguous requirement specification, unlike standard user stories. This structured framework ensures clarity and consistency when orchestrating software specifications into the development lifecycle.