speckit-brownfield-migrate

You can migrate a specific feature by name, a module path, a branch scope, or use an interactive selection when no input is provided. The skill validates the git repository and source code before generating the migration artifacts.

This process applies to brownfield projects where features were built before the spec-kit workflow existed. It helps teams adopt SDD workflows by rebuilding missing documentation from the actual codebase structure and frameworks.

The skill confirms before writing generated artifacts to ensure safe migration. Without the .specify/ directory, the migration cannot proceed.

The generated files are marked with status: migrated to distinguish them from forward-engineered specs. The skill first proposes a migration plan for review before writing the files.

This selective migration supports migrating a named feature, a module path, a branch scope, or interactive selection when no input is provided. It gives flexibility in adopting spec-kit incrementally.

Additionally, the reverse-engineered specs include explicit notes on assumptions, meaning inferred scenarios and requirements may not perfectly match original intentions. Human review of proposed migration plans is required before writing artifacts.