speckit.migrate

To generate documentation from an existing codebase for migration, this Skill recursively parses repository structure and configuration files to extract architecture, data models, and workflows, then writes organized markdown outputs like spec.md, plan.md, and tasks.md.

The best way to reverse-engineer repository architecture into spec artifacts is by automatically inspecting directory structures and source files to infer frameworks, identify entry points and API endpoints, and produce structured markdown files with confidence annotations.

Yes, you can extract API endpoints and data models from source files automatically by applying this Skill to parse configuration files and source code, inferring the tech stack and identifying key entities for your documentation.

You create onboarding documentation for a legacy code repository by analyzing the existing code to capture architecture and implementation gaps, generating standardized spec.md, plan.md, and tasks.md artifacts to reduce manual analysis time.

Yes, this codebase analysis tool works without external dependencies, as it directly parses the repository structure and configuration files to locate key files and infer the tech stack independently.

The generated spec.md files include confidence annotations that emit a summary score reflecting the reliability of the inferred architecture, extracted entities, and identified workflows from the analyzed repository.