Project Migrate FAQs

Question 1

When should I use this skill?

Accepted Answer

You should use this skill when bringing an existing (brownfield) project into the SynthesisFlow methodology. It is ideal for teams who want to organize scattered documentation, ADRs, and design docs into a standardized directory without losing data or version history.

Question 2

Will I lose my documentation's git history after migration?

Accepted Answer

No. Unlike a simple copy-paste, this skill uses git-aware file movement. By utilizing git commands for the migration, it ensures that all historical metadata, commit logs, and authorship information remain attached to your documentation in its new location.

Question 3

How does Project Migrate ensure the migration is safe?

Accepted Answer

Safety is built-in via a multi-phase process: it offers a dry-run mode for previewing changes, creates a complete timestamped backup before execution, and generates an automated rollback script to restore your original structure if anything goes wrong.

Question 4

What does the Project Migrate skill do?

Accepted Answer

Project Migrate automates the transition of existing project documentation into the structured SynthesisFlow format. It intelligently discovers markdown files, categorizes them into specs or ADRs, moves them using git to preserve history, and automatically updates relative links.

Question 5

Does it handle broken links and metadata?

Accepted Answer

Yes. The skill includes an integrated link recalculation phase to fix relative markdown paths and an automated frontmatter generator. This ensures your migrated documents are immediately compatible with indexing tools and maintain internal integrity.

Project Migrate

Project Migrate

主要功能

使用场景

主要功能

使用场景