moai-foundation-specs

SPEC YAML frontmatter validation (7 required fields) and HISTORY section enforcement.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill automates the validation of SPEC YAML frontmatter and enforces HISTORY section compliance within project documentation. It ensures that all specifications meet the TRUST 5 principles and follow foundation domain best practices, providing a robust quality gate for TDD workflows and technical documentation management.

Use Cases

  • Automated Metadata Validation: Automatically verify that all specification files contain the 7 required YAML frontmatter fields (name, version, created, etc.) to maintain structural integrity.
  • Audit Trail Enforcement: Ensure every document includes a mandatory and properly formatted HISTORY section to maintain a transparent record of changes and updates.
  • Quality Gate Integration: Use as a pre-check in TDD workflows to prevent files with incomplete metadata or insufficient test coverage from proceeding through the development pipeline.
  • Standardization Reviews: Manually or automatically invoke the skill to review existing codebases for compliance with TRUST 5 quality principles and foundation-level standards.
namemoai-foundation-specs
version2.0.0
created2025-10-22
updated2025-10-22
statusactive
descriptionSPEC YAML frontmatter validation (7 required fields) and HISTORY section enforcement.
keywords['spec', 'yaml', 'validation', 'history']

Foundation Specs Skill

Skill Metadata

Field Value
Skill Name moai-foundation-specs
Version 2.0.0 (2025-10-22)
Allowed tools Read (read_file), Bash (terminal)
Auto-load On demand when keywords detected
Tier Foundation

What It Does

SPEC YAML frontmatter validation (7 required fields) and HISTORY section enforcement.

Key capabilities:

  • ✅ Best practices enforcement for foundation domain
  • ✅ TRUST 5 principles integration
  • ✅ Latest tool versions (2025-10-22)
  • ✅ TDD workflow support

When to Use

Automatic triggers:

  • Related code discussions and file patterns
  • SPEC implementation (/alfred:2-run)
  • Code review requests

Manual invocation:

  • Review code for TRUST 5 compliance
  • Design new features
  • Troubleshoot issues

Inputs

  • Language-specific source directories
  • Configuration files
  • Test suites and sample data

Outputs

  • Test/lint execution plan
  • TRUST 5 review checkpoints
  • Migration guidance

Failure Modes

  • When required tools are not installed
  • When dependencies are missing
  • When test coverage falls below 85%

Dependencies

  • Access to project files via Read/Bash tools
  • Integration with moai-foundation-langs for language detection
  • Integration with moai-foundation-trust for quality gates

References (Latest Documentation)

Documentation links updated 2025-10-22


Changelog

  • v2.0.0 (2025-10-22): Major update with latest tool versions, comprehensive best practices, TRUST 5 integration
  • v1.0.0 (2025-03-29): Initial Skill release

Works Well With

  • moai-foundation-trust (quality gates)
  • moai-alfred-code-reviewer (code review)
  • moai-essentials-debug (debugging support)

Best Practices

✅ DO:

  • Follow foundation best practices
  • Use latest stable tool versions
  • Maintain test coverage ≥85%
  • Document all public APIs

❌ DON'T:

  • Skip quality gates
  • Use deprecated tools
  • Ignore security warnings
  • Mix testing frameworks