What is the Canonical Specification Format?

It is a provider-agnostic, YAML-based intermediate representation for software requirements designed to bridge different specification tools and standards like Gherkin or EARS.

Does this skill support EARS patterns?

Yes, it validates requirements against EARS types including ubiquitous, state-driven, event-driven, unwanted, complex, and optional patterns.

How are specifications validated?

The skill checks for required fields like IDs (SPEC-XXX), minimum character counts for problem descriptions, valid ISO 8601 dates, and specific enum values for status and priority.

Can I map this format to other tools?

Yes, the canonical format serves as a central hub for transformations between providers like Gherkin, SpKit, and ADRs.

Canonical Spec Format

Name: Canonical Spec Format
Author: melodic-software

bymelodic-software

•

学习与文档

Standardizes software requirements using a provider-agnostic YAML schema for structured, validated specifications.

关于

This skill provides a comprehensive reference and validation framework for the Canonical Specification Format, an intermediate representation defined in ADR-115. It enables developers to create, validate, and map requirements between different formats (such as Gherkin or EARS) while maintaining a consistent structure across identifiers, MoSCoW priorities, and metadata. It is an essential tool for teams practicing spec-driven development who require a single, machine-readable source of truth for features, bugs, and technical debt.

主要功能

Provides schema-based validation for specification IDs and metadata
Supports MoSCoW priority classification for requirement management
Facilitates provider-agnostic mapping between various documentation formats
Includes built-in traceability for ADRs, Epics, and User Stories
5 GitHub stars
Enforces EARS (Easy Approach to Requirements Syntax) pattern validation

使用场景

Standardizing diverse project documentation into a single machine-readable format
Validating complex requirements against strict architectural patterns and schema constraints
Generating consistent specification structures for feature requests and technical debt tracking

关于

主要功能

Provides schema-based validation for specification IDs and metadata
Supports MoSCoW priority classification for requirement management
Facilitates provider-agnostic mapping between various documentation formats
Includes built-in traceability for ADRs, Epics, and User Stories
5 GitHub stars
Enforces EARS (Easy Approach to Requirements Syntax) pattern validation

使用场景

Standardizing diverse project documentation into a single machine-readable format
Validating complex requirements against strict architectural patterns and schema constraints
Generating consistent specification structures for feature requests and technical debt tracking