moai-workflow-spec

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

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/gkswls5006-web/last-todo --skill moai-workflow-spec-gkswls5006-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-workflow-spec
Source: https://github.com/gkswls5006-web/last-todo/tree/main/.claude/skills/moai-workflow-spec
Command: npx skills add https://github.com/gkswls5006-web/last-todo --skill moai-workflow-spec-gkswls5006-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

SPEC workflow orchestration for MoAI-ADK projects that standardize planning, execution, and documentation of feature specifications.

Core Features & Use Cases

  • EARS-based requirement generation for predictable scope
  • Plan-Run-Sync lifecycle integration with DDD-guided execution
  • Parallel development support via worktrees and dependency isolation
  • Governance, versioning, and metadata-driven SPEC artifacts (spec.md, plan.md, acceptance.md)

Quick Start

Create a new SPEC by issuing a plan command and then execute the Run and Sync phases to generate full SPEC artifacts.

Frequently Asked Questions about moai-workflow-spec

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

FAQPage Schema
How do I automate SPEC workflow orchestration for MoAI-ADK projects?

You can automate SPEC workflow orchestration by using EARS-based requirements and Plan-Run-Sync integration to generate, execute, and synchronize feature specifications across your MoAI-ADK projects.

What is the EARS pattern for requirement generation in spec workflows?

The EARS pattern provides predictable scope by standardizing requirement syntax, ensuring that your spec.md artifacts maintain consistent structure and are automatically validated within the lifecycle.

How do I manage parallel development with git-worktree and SPEC artifacts?

You can manage parallel development by isolating dependencies and utilizing parallel worktrees to handle multiple SPECs simultaneously, ensuring governance checks and metadata validation across isolated branches.

Does the Plan-Run-Sync lifecycle support DDD-guided execution for Claude-based teams?

Yes, the Plan-Run-Sync lifecycle integrates DDD-guided execution, allowing Claude-based teams to generate plans, execute run cycles, and sync documentation with automated validation of artifacts.

What is the best way to validate spec.md, plan.md, and acceptance.md artifacts?

The best way to validate these artifacts is through automated governance checks that verify metadata schema and lifecycle compliance, ensuring your EARS-based requirements and Plan-Run-Sync documentation remain consistent.

When do I need to generate SPEC metadata schema and lifecycle versioning?

You need SPEC metadata schema and versioning when standardizing planning, execution, and documentation of feature specifications, ensuring governance and predictable scope across multiple parallel worktrees.