# Modernize Legacy Systems Incrementally

Legacy modernization can disrupt critical operations and hide integration risks. This skill structures assessment, testing, incremental replacement, rollout, and decommissioning with measurable safeguards.

## Install

```bash
npx skillstore add sickn33/framework-migration-legacy-modernize
```

## Metadata

- Status: approved
- Slug: sickn33-framework-migration-legacy-modernize
- Skillstore revision: r2
- Version status: missing
- Tree hash: 3f993123584c505f51963a2a53a2d1ec70337cb3cc4f3a05c401f2125ae00d2f
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/framework-migration-legacy-modernize
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-framework-migration-legacy-modernize
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-framework-migration-legacy-modernize/manifest

## Capabilities

- Assesses technical debt, dependencies, business impact, and migration readiness.
- Defines characterization, contract, performance, and test data coverage before changes.
- Designs strangler routing, adapters, feature flags, fallbacks, and dual-system observability.
- Organizes modernization waves by business value, technical risk, and quick-win potential.
- Establishes progressive rollout gates, rollback triggers, and measurable success criteria.
- Plans legacy decommissioning, documentation, and knowledge transfer after stable operation.

## Use Cases

- Build a modernization roadmap: Prioritize legacy components using technical debt, dependencies, business criticality, risk, and quick-win potential.
- Establish migration safety tests: Plan characterization, contract, performance, and data consistency testing before component replacement.
- Control a progressive rollout: Define traffic stages, monitoring, automatic rollback triggers, fallback mechanisms, and observation periods.

## Prompt Templates

### Assess a legacy system

```
Assess [system]. Identify technical debt, dependencies, business risks, quick wins, and missing information needed for modernization.
```

### Design migration test coverage

```
Design testing for [components]. Include characterization tests, integration contracts, test data, performance baselines, and acceptance criteria.
```

### Plan a strangler migration

```
Plan migration for [component]. Define routing, adapters, data consistency, feature flags, observability, rollback triggers, and phased traffic percentages.
```

### Challenge an advanced migration plan

```
Evaluate [migration plan] against [constraints]. Rank failure modes, challenge assumptions, define automated gates, and specify evidence required for decommissioning.
```

## Limitations

- Provides workflow guidance and prompts; it does not independently inspect or modify a codebase.
- Requires repository access, architecture context, business constraints, and production metrics for useful recommendations.
- Suggested thresholds and technologies need adaptation to local service levels, regulations, and platform capabilities.
- Does not replace security review, migration testing, or human approval for production changes.

## Best Practices

- Capture current behavior with characterization and contract tests before replacing components.
- Define measurable rollback triggers and observe each rollout stage before increasing traffic.
- Retain legacy fallbacks until dependency, traffic, data consistency, and stability evidence support decommissioning.

## Anti Patterns

- Do not start implementation before mapping dependencies, business criticality, and shared data.
- Do not use dual writes without reconciliation monitoring and a documented recovery process.
- Do not decommission legacy components immediately after traffic reaches zero.

## Security Audit

- Audited at: 2026-07-23T22:39:14.299\+00:00
- Summary: The sole static finding is a false positive caused by Markdown backticks around a referenced file path. SKILL.md contains workflow instructions only, with no shell execution, executable code, prompt injection, or malicious intent.

## Stats

- Views: 97
- Downloads: 9
- Favorites: 0
- Popularity score: 0