skills.rest
kivo360
kivo360COMMUNITY
Explore all skills by this author →
GitHub

moai-foundation-specs

Validate SPEC YAML frontmatter fields and enforce HISTORY sections.

1|Updated Jul 28, 2025
Search Tags:#documentation#validation#yaml#history#spec
One-click install
npx skills add https://github.com/kivo360/quickhooks --skill moai-foundation-specs-kivo360
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-foundation-specs
Source: https://github.com/kivo360/quickhooks/tree/main/.claude/skills/moai-foundation-specs
Command: npx skills add https://github.com/kivo360/quickhooks --skill moai-foundation-specs-kivo360

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces SPEC YAML frontmatter structure and HISTORY section across MoAI-ADK specs.

Core Features & Use Cases

  • Frontmatter Validation: Enforces 7 required fields
  • HISTORY Enforcement: Requires history entries and versioning
  • Integration: Aligns with TRUST 5 governance
  • Practical Guidance: Examples and templates

Quick Start

Validate a SPEC.md against the 7 required fields and verify HISTORY presence.

Frequently Asked Questions about moai-foundation-specs

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

FAQPage Schema
How do I validate YAML frontmatter in my SPEC documentation?▼

SPEC YAML frontmatter validation enforces seven required fields and HISTORY section structure. Run validation against your SPEC.md to ensure compliance with MoAI-ADK standards and trigger automatic quality gates.

What are the seven required fields for SPEC frontmatter?▼

The Skill enforces seven mandatory YAML frontmatter fields in SPEC files. The exact field names are defined in the validation schema; refer to the SPEC template and documentation for the complete list and required formats.

How do I enforce HISTORY section requirements in my specs?▼

HISTORY enforcement validates versioning entries and audit trails within SPEC documents. The Skill requires history entries to be present and properly structured, integrating with TRUST 5 compliance checks during code reviews and feature design workflows.

Can I use SPEC validation with language detection in my project?▼

Yes. SPEC frontmatter validation integrates with moai-foundation-langs for automatic language detection and moai-foundation-trust for quality gates, enabling language-aware validation across foundation-domain projects.

What test coverage is required when using SPEC validation?▼

SPEC validation requires ≥85% test coverage enforced within a test-driven development workflow. This ensures quality gates pass during validation and maintains consistency across TRUST 5 compliance reviews.

When should I run SPEC validation—manually or automatically?▼

SPEC validation triggers automatically in code discussions and SPEC implementations. Manual reviews are recommended for TRUST 5 compliance checks, feature design decisions, and troubleshooting edge cases within foundation-domain projects.

Related Skills

Explore More Education & Research Skills→
andy-austinandy-austin

create-skill

Create Claude Code skills with YAML frontmatter and structured Markdown guides.

Community
Intermediate
SufficientDaikonSufficientDaikon
8

reviewer

Automates compliance review of implementation code against specification files and generates HTML reports.

Community
Advanced
kivo360kivo360
1

moai-lang-sql

Enforce SQL best-practice compliance across PostgreSQL and MySQL codebases.

Community
Advanced
kivo360kivo360
1

moai-foundation-git

Enforce GitFlow and PR policies for MoAI-ADK workflows via Git and GitHub CLI.

Community
Advanced