speckit-brownfield-migrate

Reverse-engineer existing code into spec-kit migration artifacts with gap reporting.

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-brownfield-migrate-numu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-brownfield-migrate
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-brownfield-migrate
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-brownfield-migrate-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns already-built features into structured spec-kit artifacts so teams can bring legacy work into an SDD workflow without rewriting the implementation.

Core Features & Use Cases

  • Feature Discovery: Detects likely migration targets from existing source, tests, branches, or module paths.
  • Spec Reconstruction: Rebuilds spec.md, plan.md, and tasks.md from the codebase, then marks them as migrated.
  • Gap Analysis: Identifies missing tests, unclear behavior, and undocumented assumptions during the migration process.
  • Use Case: A team adopting spec-kit on an active repository can migrate an authentication module or payments flow into tracked artifacts before making future changes.

Quick Start

Ask the assistant to inspect this repository, identify a legacy feature to migrate, and generate the corresponding migrated spec-kit artifacts.

Frequently Asked Questions about speckit-brownfield-migrate

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

FAQPage Schema
How do I migrate existing legacy code into spec-kit artifacts?

To migrate legacy code into spec-kit artifacts, the Skill reverse-engineers existing source, tests, and database changes to reconstruct spec.md, plan.md, and tasks.md files. It then marks these migrated artifacts without modifying the original source code.

What is brownfield feature migration in software engineering?

Brownfield feature migration is the process of reverse-engineering already-built features into structured documentation. This Skill rebuilds spec-kit artifacts from legacy modules and branches, allowing teams to adopt spec-driven workflows without rewriting existing implementations.

Do I need a git repository to reconstruct specs from existing code?

Yes, you need a git repository with an active spec-kit project containing a .specify/ directory. The Skill uses git access and the existing spec-kit structure to discover migration targets and generate migrated artifacts for your legacy features.

How do I identify undocumented assumptions and missing tests in a legacy module?

To identify undocumented assumptions and missing tests in a legacy module, the Skill performs gap analysis during the migration process. It scans the codebase to detect missing tests and unclear behavior, reporting these gaps alongside the reconstructed artifacts.

Can I generate spec.md and plan.md for a whole project inventory at once?

Yes, you can generate spec.md, plan.md, and tasks.md for a whole-project inventory at once. The Skill detects likely migration targets from existing source, tests, and branches, processing entire project inventories to reconstruct spec-kit artifacts.

Does reverse-engineering legacy features modify my source code?

No, reverse-engineering legacy features into spec-kit artifacts does not modify your source code. The Skill preserves migrated status and generates gap reports while strictly reading from the existing codebase to reconstruct documentation files.