Can I save the converted output directly to a file?

Yes, by using the --output flag followed by a file path, you can write the results directly to your project documentation.

What is the 'Canonical' format mentioned in the documentation?

Canonical format is a standardized list format used within the spec-driven development plugin suite to ensure requirements are formatted consistently for automated processing.

What is the EARS format?

EARS (Easy Approach to Requirements Syntax) is a mechanism for gently constraining natural language requirements to make them clear, concise, and testable.

How does the converter handle complex logic?

The converter uses pattern preservation to map EARS logic like 'WHILE...SHALL' to Gherkin 'Given (state)...Then' to ensure the original intent is maintained.

Can I convert Gherkin scenarios back into EARS requirements?

Yes, the skill supports bi-directional conversion, allowing you to transform Gherkin Given/When/Then scenarios back into structured EARS requirements.

EARS Requirement Converter

Name: EARS Requirement Converter
Author: melodic-software

bymelodic-software

•

学习与文档

Converts software specifications between EARS (Easy Approach to Requirements Syntax), Gherkin, prose, and canonical formats.

The EARS Requirement Converter facilitates seamless transitions between different specification styles, specifically focusing on the Easy Approach to Requirements Syntax (EARS). By automating the transformation of natural language prose into structured 'SHALL' statements, or converting those requirements directly into Gherkin scenarios for behavior-driven development (BDD), it ensures consistency and rigor in technical documentation. This skill is ideal for teams practicing spec-driven development who need to maintain high-quality, unambiguous requirements while keeping them accessible to both business stakeholders and technical testing frameworks.

主要功能

01Semantic preservation of EARS patterns including WHEN, WHILE, and IF/THEN

02Bi-directional conversion between Prose, EARS, and Gherkin formats

03Automated parsing and structure identification of existing requirements

0438 GitHub stars

05Validation of target format compliance to ensure technical accuracy

06Direct output to file for immediate integration into documentation

使用场景

01Transforming informal stakeholder notes into formal, unambiguous EARS requirements

02Generating Gherkin test scenarios directly from structured EARS specifications

03Converting technical EARS requirements into readable prose for business-facing documentation

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add melodic-software/claude-code-plugins ears-convert

For use in Claude.ai and ChatGPT

Download Skill