Which file formats are supported for conversion?

The skill supports Gherkin (.feature), EARS-only lists, AWS Kiro structures (requirements, design, tasks), Agile User Stories, and a Canonical Markdown format.

Is there a way to validate the conversion results?

The skill automatically performs a validation step after conversion to check for format compliance and verify that no content or data was lost during the process.

How does it handle the AWS Kiro structure?

It maps Functional Requirements to requirements.md, Design sections to design.md, and Implementation tasks to tasks.md while maintaining EARS syntax natively.

Can I define where the converted file is saved?

Yes, you can use the optional --output flag to specify a custom file path, or let the skill derive a path based on the source filename.

Does this skill preserve the meaning of my requirements?

Yes, the converter uses specialized mapping logic—such as translating EARS 'WHEN...SHALL' patterns into Gherkin 'When...Then' steps—to maintain semantic integrity across formats.

Spec Format Converter

Name: Spec Format Converter
Author: melodic-software

bymelodic-software

•

Security & Testing

Converts software specifications between various formats like EARS, Gherkin, and Kiro while maintaining semantic integrity.

The Spec Format Converter is a specialized utility for teams practicing spec-driven development, enabling seamless translation between different requirement and testing formats. It allows users to effortlessly transition between formats such as EARS (Easy Approach to Requirements Syntax), Gherkin feature files, and AWS Kiro structures without losing the underlying logic or meaning. By automating the parsing and mapping process, this skill ensures that project documentation, design specifications, and test scenarios remain synchronized throughout the development lifecycle, reducing manual rewriting and human error in requirements engineering.

Key Features

01Built-in validation to check target format compliance and content integrity

02Semantic mapping to ensure requirement logic and identifiers are preserved

03Bidirectional conversion between Gherkin, EARS, Kiro, and User Stories

0438 GitHub stars

05Full support for AWS Kiro structure (requirements, design, and tasks)

06Automatic source format detection and structural analysis

Use Cases

01Transforming high-level EARS requirements into Gherkin feature files for BDD testing

02Standardizing disparate requirement formats into a canonical markdown format for documentation

03Migrating project documentation into the AWS Kiro structure for cloud-native development

What are Skills?·How to Install

Install with 🐟 Skill.Fish

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

For use in Claude.ai and ChatGPT

Download Skill