b29c12d5e5
Final rebrand: rename remaining Rust source file to complete the gsd → forge transition. All parser references already use forge_parser after earlier commits. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
48 lines
1.3 KiB
Markdown
48 lines
1.3 KiB
Markdown
# Migration from v1
|
|
|
|
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 your old `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 into the new structure
|
|
- Shows a preview before writing anything
|
|
- Optionally runs an AI-driven review for quality assurance
|
|
|
|
## 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
|
|
|
|
## Requirements
|
|
|
|
Migration works best with a `ROADMAP.md` file for milestone structure. Without one, milestones are inferred from the `phases/` directory.
|
|
|
|
## Post-Migration
|
|
|
|
After migrating, verify the output:
|
|
|
|
```
|
|
/sf doctor
|
|
```
|
|
|
|
This checks `.sf/` integrity and flags any structural issues.
|