moai-workflow-spec

Orchestrate SPEC workflow management using EARS format and Git Worktrees.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/thkim2015/pdf-tool --skill moai-workflow-spec-thkim2015
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-workflow-spec
Source: https://github.com/thkim2015/pdf-tool/tree/main/.claude/skills/moai-workflow-spec
Command: npx skills add https://github.com/thkim2015/pdf-tool --skill moai-workflow-spec-thkim2015

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation and management of software specifications by enforcing the EARS format and integrating with a Plan-Run-Sync development methodology, ensuring clarity and consistency in requirements.

Core Features & Use Cases

  • EARS Requirement Definition: Structure requirements using five distinct patterns (Ubiquitous, Event-Driven, State-Driven, Unwanted, Optional) for unambiguous specifications.
  • Workflow Orchestration: Manages the entire lifecycle of a SPEC from planning and implementation to synchronization, leveraging agents like manager-spec and manager-ddd.
  • Use Case: When starting a new feature, use this Skill to define its requirements in EARS format, plan its implementation, and track its progress through the development lifecycle, ensuring all stakeholders have a clear understanding of what needs to be built and why.

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?

The EARS format structures software requirements using five distinct patterns: Ubiquitous, Event-Driven, State-Driven, Unwanted, and Optional. This Skill orchestrates SPEC workflows by enforcing these exact patterns to produce unambiguous requirement specifications and acceptance criteria.

What is the best way to manage SPEC documents across a development lifecycle?

Managing SPEC documents across a lifecycle is best handled through a Plan-Run-Sync development methodology. This Skill orchestrates the entire process from planning and implementation to synchronization, ensuring stakeholders maintain clear requirement understanding.

Can I use Git Worktrees for parallel development with SPEC workflows?

Yes, SPEC workflows support parallel development via Git Worktrees. This allows multiple development branches to operate simultaneously while maintaining synchronized requirement tracking and implementation progress within the MoAI-ADK methodology.

Do I need MoAI-ADK to use the EARS requirement workflow?

MoAI-ADK is required to fully leverage the Plan-Run-Sync integration and utilize orchestration agents like manager-spec and manager-ddd. The methodology relies on this framework to manage the SPEC lifecycle from requirement clarification to final synchronization.

Why does requirement clarification matter before creating a SPEC document?

Requirement clarification matters because it ensures the SPEC document accurately captures the needs before implementation begins. Structuring these clarified requirements using EARS patterns prevents ambiguity and aligns expectations across all stakeholders.