smith-migrate-specs

Name: smith-migrate-specs
Availability: InStock
Author: ATTCK

Migrate flat feature specs into a system-based hierarchy under .specify/systems/.

50|8|Updated Apr 12, 2026

Search Tags:#automation #migration #traceability #specs #system-hierarchy #feature-maps #spec-migration

Ready to run

npx skills add https://github.com/ATTCKDigital/smith --skill smith-migrate-specs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smith-migrate-specs
Source: https://github.com/ATTCKDigital/smith/tree/main/skills/smith-migrate-specs
Command: npx skills add https://github.com/ATTCKDigital/smith --skill smith-migrate-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

One-time migration of existing flat spec folders into the system-based hierarchy under .specify/systems/.

Core Features & Use Cases

Scans specs/ for feature folders matching the NNN-* pattern and excludes non-feature directories.
Determines the primary system for each feature by cross-referencing system specs under .specify/systems/system-*/spec.md and identifies other affected systems.
Copies the relevant spec files into the new .specify/systems/<system>/features/<NNN-feature>/ structure and appends proper frontmatter for traceability.

Quick Start

Run smith migrate-specs to migrate flat specs into the system hierarchy.

Frequently Asked Questions about smith-migrate-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate flat feature specs into a system-based hierarchy?▼

Migrate flat feature specs by running smith migrate-specs to scan the specs/ directory and copy NNN-* feature folders into .specify/systems/<system>/features/ with added frontmatter for traceability.

What is the best way to structure existing spec folders into a system hierarchy?▼

Structuring existing spec folders into a system hierarchy involves cross-referencing each feature with system specs under .specify/systems/system-*/spec.md to determine the primary system and identify other affected systems.

Do I need to set up .specify/systems/ before migrating specs?▼

Yes, you need .specify/systems/ to exist with system folders before migrating specs, because the migration determines primary systems by cross-referencing system specs located within that directory structure.

Can I preview a spec migration before applying changes to my repository?▼

Yes, you can preview a spec migration before applying changes by using the optional dry-run preview feature to see how feature folders will be copied and mapped without modifying the actual system hierarchy.

Why does my spec migration skip certain directories in the specs folder?▼

Spec migration skips directories in the specs folder that do not match the NNN-* naming convention or lack a spec.md file, excluding non-feature directories to ensure only valid feature folders are migrated.

How does spec migration handle traceability for copied feature files?▼

Spec migration handles traceability for copied feature files by appending proper frontmatter to the spec.md files during the copy process into the new .specify/systems/<system>/features/<NNN-feature>/ structure.