migrate

Migrating to Docent's skills-based architecture converts your existing runbooks into SKILL.md files organized in a .docent/skills directory, updates config.yaml with version and skills configuration, and backs up your legacy content. The migration process automatically detects your project version, transforms runbooks while preserving templates, and ensures backward compatibility.

During upgrade, runbooks are converted into the new SKILL.md format with proper group detection and frontmatter parsing, while bundled templates remain functional. A timestamped backup of your original content is created before any changes, preserving your legacy files for rollback if needed.

No. The migration automatically transforms runbooks into skills format by parsing frontmatter, detecting groups, and generating SKILL.md files. Your content is preserved and reformatted to match the new architecture without manual rewriting.

Yes. The migration creates a timestamped backup of your entire .docent directory before making changes, allowing you to restore your original runbooks and configuration if needed.

Your project must have a .docent directory containing runbooks and templates, plus an existing config.yaml file. The migration detects version 0.9 projects and transforms them into v1.0 skills-based structure with proper configuration updates.

Yes. The migration works with projects using git cli for version control. It modifies your .docent directory and config.yaml while maintaining git compatibility for tracking changes to your migrated skills and configuration.