9d739dfa5d
- All gsdDir/gsdRoot/gsdHome → sfDir/sfRootDir/sfHome - GSDWorkspace* → SFWorkspace* interfaces - bootstrapGsdProject → bootstrapProject - runGSDDoctor → runSFDoctor - GsdClient → SfClient, gsd-client.ts → sf-client.ts - .gsd/ → .sf/ in all tests, docs, docker, native, vscode - Auto-migration: headless detects .gsd/ → renames to .sf/ - Deleted gsd-phase-state.ts backward-compat re-export - Renamed bin/gsd-from-source → bin/sf-from-source - Updated mintlify docs, github workflows, docker configs
47 lines
1.2 KiB
Text
47 lines
1.2 KiB
Text
---
|
|
title: "Migration from v1"
|
|
description: "Migrate .planning directories from the original SF to SF's .sf format."
|
|
---
|
|
|
|
If you have projects with `.planning` directories from the original Singularity Forge (v1), you can migrate them to SF's `.sf` format.
|
|
|
|
## Running the migration
|
|
|
|
```bash
|
|
# From within the project directory
|
|
/sf migrate
|
|
|
|
# Or specify a path
|
|
/sf migrate ~/projects/my-old-project
|
|
```
|
|
|
|
## What gets migrated
|
|
|
|
The migration tool:
|
|
|
|
- Parses `PROJECT.md`, `ROADMAP.md`, `REQUIREMENTS.md`, phase directories, plans, summaries, and research
|
|
- Maps phases → slices, plans → tasks, milestones → milestones
|
|
- Preserves completion state (`[x]` phases stay done, summaries carry over)
|
|
- Consolidates research files
|
|
- Shows a preview before writing anything
|
|
- Optionally runs an agent-driven review of the output
|
|
|
|
## Supported formats
|
|
|
|
The migration handles various v1 format variations:
|
|
|
|
- Milestone-sectioned roadmaps with `<details>` blocks
|
|
- Bold phase entries
|
|
- Bullet-format requirements
|
|
- Decimal phase numbering
|
|
- Duplicate phase numbers across milestones
|
|
|
|
## Post-migration
|
|
|
|
Verify the output:
|
|
|
|
```
|
|
/sf doctor
|
|
```
|
|
|
|
This checks `.sf/` integrity and flags any structural issues.
|