speckit.migrate

Automate codebase migration to speckit structure by generating spec.md, plan.md, and tasks.md.

3|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/RangeyRover/home-battery-control --skill speckit-migrate-rangeyrover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.migrate
Source: https://github.com/RangeyRover/home-battery-control/tree/main/.agent/skills/speckit.migrate
Command: npx skills add https://github.com/RangeyRover/home-battery-control --skill speckit-migrate-rangeyrover

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the migration of codebases into the speckit structure, generating spec.md, plan.md, and tasks.md from existing code, streamlining the process of documentation and project organization.

Core Features & Use Cases

  • Codebase Analysis: Analyze existing codebases and generate structured documentation.
  • Automated Documentation: Automatically create spec.md, plan.md, and tasks.md files.
  • Use Case: For a developer looking to migrate an existing project to the speckit structure, this Skill can quickly generate the necessary documentation, saving time and reducing manual effort.

Quick Start

Migrate your project to speckit structure by running 'speckit.migrate --path ./myproject --feature myproject'.

Frequently Asked Questions about speckit.migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate codebase migration to generate documentation from existing code?

You can automate documentation generation by running a command-line script that analyzes your existing code and outputs structured spec.md, plan.md, and tasks.md files. This streamlines project organization and reduces manual effort.

What is the speckit structure for codebase organization?

The speckit structure is a project organization format that relies on structured documentation artifacts, specifically spec.md, plan.md, and tasks.md files, to systematically document and organize existing codebases.

How do I generate spec.md, plan.md, and tasks.md files from my existing project?

Generate these documentation files by executing the migration script with command-line arguments specifying the project path and feature name. The tool analyzes the codebase and automatically creates the spec.md, plan.md, and tasks.md files.

Can I specify the analysis depth when migrating code to automated documentation?

Yes, you can specify the analysis depth when migrating code to automated documentation by passing command-line arguments to the script. This allows you to control the level of codebase analysis performed during the migration process.

Does the codebase migration tool require any external dependencies to run?

No, the codebase migration tool requires no external dependencies to run. It operates as a standalone script to analyze your existing code and generate the structured documentation artifacts.