faf-migrate

Migrate legacy project.faf files to IANA-registered 3.0.0+ format with backups and validation.

4|1|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/Wolfe-Jam/faf-skills --skill faf-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: faf-migrate
Source: https://github.com/Wolfe-Jam/faf-skills/tree/main/skills/faf-migrate
Command: npx skills add https://github.com/Wolfe-Jam/faf-skills --skill faf-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate older project.faf formats to the current IANA-registered version (3.0.0+), preserving existing content and adding required modern fields to stay compatible with FAF tooling.

Core Features & Use Cases

  • Automatically upgrades legacy FAF formats (v1.x/v2.x) to the current standard (v3.x), preserving all content.
  • Creates automatic backups of the original project.faf and validates the migrated file to ensure integrity and IANA compliance.
  • Provides a safe, repeatable workflow for re-migration, verification, and rollback if needed.

Quick Start

Run the migrate command to upgrade your project.faf to the latest format.

Frequently Asked Questions about faf-migrate

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

FAQPage Schema
How do I migrate old project.faf files to the current IANA-registered format?

To migrate old project.faf files, trigger the migration command to automatically upgrade legacy v1.x and v2.x formats to the current 3.0.0+ standard while preserving all existing content and adding required modern fields.

Can I rollback a FAF format migration if the updated file fails validation?

Yes, you can rollback a FAF format migration because the process creates automatic backups of the original project.faf file before upgrading, ensuring a safe and repeatable workflow for verification and recovery.

Does the FAF migration process support both legacy v1.x and v2.x formats?

Yes, the FAF migration process supports both legacy v1.x and v2.x formats, automatically upgrading them to the IANA-registered version while validating post-migration integrity to ensure full compliance.

What is the best way to ensure IANA compliance when upgrading legacy FAF files?

The best way to ensure IANA compliance when upgrading legacy FAF files is to run the migration tool, which automatically adds required modern fields and validates the resulting 3.0.0+ file structure for integrity.

Why does my project.faf file need modern fields added during migration?

Your project.faf file needs modern fields added during migration to maintain compatibility with current FAF tooling and meet the strict requirements of the IANA-registered 3.0.0+ format standard.

Are there limitations when re-migrating a project.faf file that is already on version 3.0.0+?

The migration tool targets legacy v1.x and v2.x formats for upgrade. If your project.faf file is already on the current 3.0.0+ version, re-migration is not required and the tool will focus on validating existing integrity.