speckit.migrate

Analyze source code to generate spec.md, plan.md, and tasks.md files.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/prof-danielc/SpaceScream --skill speckit-migrate-prof-danielc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.migrate
Source: https://github.com/prof-danielc/SpaceScream/tree/main/.agent/skills/speckit.migrate
Command: npx skills add https://github.com/prof-danielc/SpaceScream --skill speckit-migrate-prof-danielc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the migration of existing codebases into a structured format, reducing the manual effort required to document and organize code.

Core Features & Use Cases

  • Codebase Analysis: Analyze existing codebases to generate specifications and plans.
  • Automated Documentation: Generate spec.md, plan.md, and tasks.md from code.
  • Use Case: Use this Skill to quickly document a legacy codebase and organize it into a maintainable structure.

Quick Start

Migrate your codebase to the speckit structure by running 'speckit.migrate --path /path/to/codebase'.

Frequently Asked Questions about speckit.migrate

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

FAQPage Schema
How do I generate documentation from an existing legacy codebase?

Generating documentation from a legacy codebase is automated by analyzing source code structure and outputting standardized artifacts like spec.md, plan.md, and tasks.md to establish a maintainable organization.

What is the best way to automate code migration into structured specifications?

Automating code migration into structured specifications is achieved by parsing source code files and automatically generating documentation artifacts that reduce manual effort for refactoring initiatives.

Can I use automated codebase analysis to organize a legacy project for refactoring?

Automated codebase analysis can be used to organize legacy projects for refactoring by evaluating the source code and generating structured plans and tasks needed for maintainable migration.

How do I create spec.md, plan.md, and tasks.md files directly from source code?

Creating spec.md, plan.md, and tasks.md files directly from source code requires running an automated migration command that parses the codebase and generates the corresponding documentation artifacts.

Does generating specifications from a codebase require any specific environment setup?

Generating specifications from a codebase requires an environment capable of parsing source code and supporting output generation tools to successfully produce the structured documentation artifacts.

What are the limitations of using speckit.migrate for codebase documentation?

The limitations of using speckit.migrate for codebase documentation involve its reliance on source code parsing and output generation tools, meaning complex or unsupported code structures may require manual refinement.