moai-alfred-spec-authoring

Generate and validate YAML metadata and EARS syntax for MoAI-ADK SPECs.

1|Updated Jul 28, 2025
One-click install
npx skills add https://github.com/kivo360/quickhooks --skill moai-alfred-spec-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-alfred-spec-authoring
Source: https://github.com/kivo360/quickhooks/tree/main/.claude/skills/moai-alfred-spec-authoring
Command: npx skills add https://github.com/kivo360/quickhooks --skill moai-alfred-spec-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive guide for authoring SPEC documents in MoAI-ADK projects. It covers YAML metadata structure, EARS syntax patterns, version management, and validation tooling to streamline planning and reduce errors.

Core Features & Use Cases

  • YAML front matter with 7 required + 9 optional fields and a complete SPEC metadata reference
  • 5 official EARS patterns: Ubiquitous, Event-driven, State-driven, Optional, Unwanted Behaviors
  • Version lifecycle guidance from draft to production
  • TAG chaining and validation scripts to ensure consistency

Quick Start

Start by reading SKILL.md for a guided 5-step SPEC creation, then use the included automated validation tools to verify metadata before submission.

Frequently Asked Questions about moai-alfred-spec-authoring

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

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

SPEC authoring automation generates YAML metadata and EARS syntax blocks with validated structure. Use this Skill to create SPECs with enforced metadata fields, semantic versioning, and lifecycle compliance, then run validation tools before submission.

What are EARS patterns and how do I use them in SPEC documents?

EARS syntax defines five requirement patterns: Ubiquitous (always true), Event-driven (triggered by events), State-driven (dependent on system state), Optional (conditional), and Unwanted Behaviors (forbidden actions). Apply these patterns to structure functional requirements in your SPEC.

What metadata fields are required in a SPEC document?

SPEC documents require seven mandatory metadata fields plus nine optional fields in YAML front matter. This Skill enforces and documents the complete metadata reference to ensure consistency and pre-submission validation compliance.

How do I validate and chain TAGs in SPEC documents?

TAG chaining and validation scripts ensure traceability and consistency across SPEC versions and dependencies. Use the included validation tooling to verify TAG chains and enforce semantic versioning before submitting SPECs to the repository.

Can I use this for updating existing SPEC documents?

Yes, this Skill supports SPEC creation, updates, and maintenance workflows within local repositories. Apply validation runs and automated checks to existing SPECs to enforce metadata compliance and lifecycle-required structure.