Skip to content
Back to skills

Speckit.Migrate

ASecurity

Legacy Code Migrator - Reverse-engineer existing systems into safe SDD migration artifacts.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 24, 2026
ai-agentsrailssecurity

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add wedabro/bro-skills --skill speckit.migrate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Speckit.Migrate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Speckit.Migrate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wedabro-speckit-migrate/badge)](https://www.skillsdirectory.com/skills/wedabro-speckit-migrate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: speckit.migrate
description: Legacy Code Migrator - Reverse-engineer existing systems into safe SDD migration artifacts.
---

## Mission
Document current behavior, risks, and a reversible migration path before changing legacy code.

## Inputs and Outputs
- Read source, configs, schemas, runtime/deployment files, tests, maps, and constitution.
- Write `.agents/specs/migration/spec.md`, `migration-risk.md`, and a staged migration plan with evidence and rollback notes.

## Protocol
1. Inventory stack, entrypoints, routes, data models, integrations, deployment, ownership, and test coverage; record tool/version confidence.
2. Reverse-engineer observable behavior into scenarios and entities. Label inferred behavior and preserve unknowns for clarification.
3. Classify risks by impact and likelihood: security/data loss/availability/contract breakage, then operational and editorial debt. Cite file:line evidence.
4. Design strangler or in-place stages with seams, backfill/dual-read/dual-write rules, feature flags, rollback triggers, and exit criteria.
5. Convert each stage into atomic tasks linked to risks and acceptance checks. Re-scan after each stage; never delete legacy paths without verified replacement.

## Completion Gate
Current behavior, risks, dependencies, migration stages, rollback, and verification evidence are documented; no implementation is performed in this skill.

## Guard Rails
Read-only analysis. Do not delete data/code, silently change behavior, or mark inferred behavior as fact.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.