What are the EARS patterns mentioned in the skill?

EARS (Easy Approach to Requirements Syntax) patterns provide structured templates for writing requirements to ensure they are measurable, clear, and unambiguous.

What is a SPEC in this context?

A SPEC is a formal requirements document that drives SPEC-first, Test-Driven Development (TDD), serving as the single source of truth for a feature's behavior.

How does this skill handle version control?

It implements Semantic Versioning (major.minor.patch), where patches are for clarifications, minors for new criteria, and majors for fundamental scope changes.

Does this skill help with project auditing?

Yes, by moving specifications through 'Deprecated' and 'Archived' states, it maintains a complete historical record and audit trail of all project requirements.

MoAI SPEC Foundation

Name: MoAI SPEC Foundation
Author: AJBcoding

byAJBcoding

Productivity & Workflow

Manages the full lifecycle of formal specification documents with integrated versioning and approval workflows.

About

The MoAI SPEC Foundation skill provides a comprehensive framework for SPEC-first development, enabling teams to create, version, and manage formal requirements documents using the EARS (Easy Approach to Requirements Syntax) pattern. It streamlines the transition between specification states—from initial drafting and peer review to active implementation and eventual archival—ensuring high traceability between business requirements, code implementation, and testing within the MoAI-ADK development pipeline.

Key Features

Strict semantic versioning for requirement tracking (Major.Minor.Patch)
Formal review and approval workflow automation for stakeholders
EARS-format requirement templates for clear, unambiguous syntax
Comprehensive SPEC lifecycle management from Draft to Archived
0 GitHub stars
Seamless integration with TDD and MoAI-ADK development pipelines

Use Cases

Maintaining an auditable historical record of requirement changes and evolutions
Establishing a standardized requirement gathering process before starting coding
Managing complex feature specifications requiring multi-stakeholder approval

About

Key Features

Strict semantic versioning for requirement tracking (Major.Minor.Patch)
Formal review and approval workflow automation for stakeholders
EARS-format requirement templates for clear, unambiguous syntax
Comprehensive SPEC lifecycle management from Draft to Archived
0 GitHub stars
Seamless integration with TDD and MoAI-ADK development pipelines

Use Cases

Maintaining an auditable historical record of requirement changes and evolutions
Establishing a standardized requirement gathering process before starting coding
Managing complex feature specifications requiring multi-stakeholder approval