Skill

convert

Converts specifications between EARS, Gherkin, Kiro, canonical, and user story formats while preserving semantic meaning. Supports auto-detection, validation, and targeted output paths for spec-driven workflows.

documentation

npx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-development

Tool Access

This skill is limited to using the following tools:

ReadGlobGrepWriteEditSkillTask

Preview

Convert specifications between different formats while preserving semantic meaning.

SKILL.md

Similar Skills

ears-convert

Converts specifications between EARS format and prose, Gherkin, or canonical. Parses prose to structured EARS requirements, EARS to Gherkin scenarios, and more.

7 tools

spec-driven-development

export

Exports elicited requirements to canonical, EARS, Gherkin, Markdown, YAML/JSON formats. Filter by domain, priority, category, or confidence for targeted specs.

5 tools

requirements-elicitation

prd-to-gherkin

Converts Lean PRDs to Gherkin .feature files with Vietnamese steps in mandatory Rule blocks. Use for generating structured BDD scenarios from product specs.

2 files

ai-first-engineering

Stats

Parent Repo Stars63

Parent Repo Forks9

Last CommitFeb 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Convert Specification Format

Convert specifications between different formats while preserving semantic meaning.

Supported Formats

Format	Description	Extension
`canonical`	Canonical specification format	`.md`
`ears`	EARS-only requirements list	`.md`
`gherkin`	Gherkin feature file	`.feature`
`kiro`	AWS Kiro structure	`requirements.md`, `design.md`, `tasks.md`
`userstory`	Agile user stories	`.md`

Workflow

Detect Source Format
- Read source file
- Analyze structure to determine format
- Parse content
Select Converter
- Based on source and target formats:
  - EARS ↔ Canonical: spec-converter ears agent
  - Gherkin ↔ Canonical: spec-converter gherkin agent
  - Kiro ↔ Canonical: spec-converter kiro agent
Execute Conversion
- Invoke appropriate converter agent
- Preserve semantic meaning
- Map identifiers appropriately
Validate Output
- Check target format compliance
- Verify no content lost
- Report conversion summary
Save Result
- Write to specified output path
- Or derive path from source

Arguments

$1 - Source file path
--to - Target format (canonical, ears, gherkin, kiro, userstory)
--output - Output file path (optional)

Examples

# Convert EARS to Gherkin
/spec-driven-development:convert requirements.md --to gherkin

# Convert Gherkin to canonical
/spec-driven-development:convert auth.feature --to canonical

# Convert to Kiro format
/spec-driven-development:convert .specs/auth/spec.md --to kiro

# Specify output path
/spec-driven-development:convert spec.md --to gherkin --output tests/auth.feature

Conversion Matrix

From → To	Canonical	EARS	Gherkin	Kiro
Canonical	-	✓	✓	✓
EARS	✓	-	✓	✓
Gherkin	✓	✓	-	✓
Kiro	✓	✓	✓	-

Conversion Notes

EARS ↔ Gherkin

EARS "WHEN...SHALL" maps to Gherkin "When...Then"
State-Driven EARS maps to Given preconditions
Unwanted EARS maps to negative scenarios

Canonical ↔ Kiro

Kiro uses EARS syntax natively
requirements.md ↔ Functional Requirements
design.md ↔ Design section
tasks.md ↔ Implementation tasks

Related Commands

/spec-driven-development:ears-convert - EARS-specific conversion
/spec-driven-development:gherkin-convert - Gherkin-specific conversion
/spec-driven-development:kiro-sync - Kiro synchronization