skills.rest
yekinya
yekinyaCOMMUNITY
Explore all skills by this author →
GitHub

moai-workflow-spec

Creates EARS-format SPEC documents with acceptance criteria for Plan-Run-Sync workflows.

2|Updated May 27, 2026
Search Tags:#workflow#planning#requirements#acceptance criteria#spec#ears#moai-adk
One-click install
npx skills add https://github.com/yekinya/moai-novel --skill moai-workflow-spec-yekinya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-workflow-spec
Source: https://github.com/yekinya/moai-novel/tree/main/moai-novel/.claude/skills/moai-workflow-spec
Command: npx skills add https://github.com/yekinya/moai-novel --skill moai-workflow-spec-yekinya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing unambiguous software requirements is hard—vague specs cause misinterpretation, scope creep, and rework. This Skill structures feature requirements using the EARS format and integrates them into the MoAI-ADK Plan-Run-Sync development workflow. ## Core Features & Use Cases - EARS Requirement Patterns: Structures requirements using five patterns (Ubiquitous, Event-Driven, State-Driven, Unwanted, Optional) to eliminate ambiguity. - SPEC Document Generation: Produces standardized 3-file SPEC directories (spec.md, plan.md, acceptance.md) with metadata, constraints, and Given-When-Then test scenarios. - Plan-Run-Sync Integration: Connects SPECs to implementation via /moai:1-plan, /moai:2-run, and /moai:3-sync commands, including Git Worktree support for parallel feature development. - Use Case: When planning a user authentication feature, invoke this Skill to clarify requirements, generate SPEC-001 with EARS requirements and measurable acceptance criteria, then hand it off to the RUN phase for implementation. ## Quick Start Ask the AI to create a new SPEC for your feature, for example: run /moai:1-plan "user authentication system" to generate an EARS-format SPEC document.

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 requirements in EARS format?▼

EARS format uses five patterns: Ubiquitous (system shall always), Event-Driven (WHEN event THEN action), State-Driven (IF condition THEN action), Unwanted (shall not), and Optional (where possible). Each requirement uses exactly one pattern to eliminate ambiguity.

How do I create a SPEC document with this workflow?▼

Run /moai:1-plan followed by a feature description, such as /moai:1-plan "user authentication system". The manager-spec agent clarifies requirements, applies EARS patterns, and creates a SPEC directory with spec.md, plan.md, and acceptance.md files.

What files must a SPEC directory contain?▼

Every SPEC directory under .moai/specs/ must contain three files: spec.md with EARS requirements, plan.md with the implementation plan, and acceptance.md with Given-When-Then acceptance criteria. Missing files block proper workflow execution.

Can I develop multiple features in parallel with SPECs?▼

Yes, use the --worktree flag with /moai:1-plan to create multiple SPECs with isolated Git Worktree environments. Each feature gets its own working directory, enabling parallel development without branch switching or merge conflicts.

What should not be placed in the .moai/specs directory?▼

Reports analyzing existing code (security audits, performance reports) belong in .moai/reports/, and documentation explaining how to use features belongs in .moai/docs/. The specs directory is exclusively for forward-looking feature definitions.

Related Skills

Explore More Software Engineering Skills→
bacchus-labsbacchus-labs
4

brainstorming

Transform raw ideas into validated design specifications through structured questioning.

Official
Intermediate
afonsoftafonsoft

execute-spec

Implements approved SPEC documents using test-driven development with red-green-refactor cycles.

Community
Intermediate
kivo360kivo360
1

moai-foundation-ears

Automate EARS requirement authoring with five official patterns and TRUST 5 integration.

Community
Advanced
burgebjburgebj

octopus-quick

Execute small software changes with atomic commits and state tracking.

Community
Intermediate