speckit.migrate

Generate speckit artifacts by analyzing architecture, entities, and workflows from an existing codebase.

Updated Oct 4, 2025

Search Tags:#documentation #migration #speckit #reverse-engineering #repo-analysis #spec-generation

Ready to run

npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-migrate-peancharoen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit.migrate
Source: https://github.com/peancharoen/lcbp3/tree/main/.agents/skills/speckit.migrate
Command: npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-migrate-peancharoen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates reverse-engineering of an existing codebase into speckit-style documentation artifacts (spec.md, plan.md, tasks.md), reducing manual analysis time and helping teams capture architecture, data models, and implementation gaps.

Core Features & Use Cases

Automated Discovery: Recursively inspects repository structure to locate key files, entry points, and configuration.
Architecture & Model Extraction: Infers framework, tech stack, entities, and API endpoints from configs and source files.
Artifact Generation: Produces spec.md, plan.md, and tasks.md under a feature directory and emits a summary with confidence scores.
Use Case: Migrate legacy repositories into a standardized speckit documentation format for planning, onboarding, or handoffs.

Quick Start

Analyze the repository and generate spec.md, plan.md, and tasks.md for a feature named "migrate-feature" at analysis depth 2.

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 codebase for migration?▼

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.

What is the best way to reverse-engineer repository architecture into spec artifacts?▼

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.

Can I extract API endpoints and data models from source files automatically?▼

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.

How do I create onboarding documentation for a legacy code repository?▼

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.

Does this codebase analysis tool work without external dependencies?▼

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.

What confidence annotations are included in the generated spec.md files?▼

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.