moai-workflow-spec

Orchestrate SPEC workflows using EARS format with Plan-Run-Sync integration.

Updated Nov 20, 2025
One-click install
npx skills add https://github.com/soo-kate-yeon/shadowoo --skill moai-workflow-spec-soo-kate-yeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-workflow-spec
Source: https://github.com/soo-kate-yeon/shadowoo/tree/main/.agents/skills/moai-workflow-spec
Command: npx skills add https://github.com/soo-kate-yeon/shadowoo --skill moai-workflow-spec-soo-kate-yeon

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 software specifications using the EARS format, ensuring clarity, completeness, and testability throughout the development lifecycle.

Core Features & Use Cases

  • EARS Requirement Generation: Define requirements using five distinct patterns (Ubiquitous, Event-Driven, State-Driven, Unwanted, Optional).
  • SPEC Document Orchestration: Manage the creation, refinement, and lifecycle of SPEC documents.
  • Plan-Run-Sync Integration: Seamlessly integrates with development workflows for planning, execution, and synchronization.
  • Use Case: When starting a new feature, use this Skill to meticulously define its requirements, acceptance criteria, and technical constraints, ensuring all stakeholders have a clear understanding before implementation 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?

The EARS format structures software requirements into five patterns: Ubiquitous, Event-Driven, State-Driven, Unwanted, and Optional. This approach ensures requirements remain clear, testable, and unambiguous throughout the development lifecycle.

What is the best way to manage SPEC documents for new feature development?

Managing SPEC documents is best handled through systematic orchestration that handles creation, requirement clarification, and acceptance criteria definition. This ensures all stakeholders share a clear understanding before implementation begins.

How do I integrate requirement definition with a Plan-Run-Sync workflow?

Requirement definition integrates with a Plan-Run-Sync workflow by mapping EARS-based specifications directly into planning, execution, and synchronization phases. This aligns development tasks with documented acceptance criteria and technical constraints.

Can I use Git Worktrees for parallel development based on software specifications?

Yes, Git Worktrees support parallel development derived from software specifications. This allows multiple branches to implement distinct requirements simultaneously while maintaining synchronization with the main SPEC document.

Does this SPEC workflow support template inheritance and automated validation?

Yes, the SPEC workflow supports advanced patterns like template inheritance and automated validation. These features enforce robust software specification management and ensure ongoing compliance with defined EARS requirements.