speckit.migrate

Reverse-engineering a codebase into spec.md involves parsing the project structure, detecting entry points, and inferring architecture to generate feature-specific documentation. This tool outputs conservative spec.md, plan.md, and tasks.md artifacts reflecting the live codebase.

Generating tasks.md from a project structure requires parsing components and inferring architecture to list concrete work items. This tool produces tasks.md to transition the project into speckit format and maintain traceability for future maintenance.

This reverse-engineering workflow applies to projects of any size. It parses the full project structure and generates feature-specific spec.md, plan.md, and tasks.md artifacts that reflect the live codebase regardless of scale.

Creating plan.md to map components to milestones requires inferring architecture and detecting entry points. This tool generates plan.md mapping components to implementation steps and milestones based on the current live codebase structure.

To start migrating into the speckit artifact model, provide the target project path and feature name, then run the migration. The tool outputs spec.md, plan.md, and tasks.md documenting the current architecture and work breakdown.

No, the generated spec.md contains conservative, non-inventive content suitable for future development. The tool reverse-engineers only the current architecture, constraints, and features that actually exist in the live codebase.