stepwise-clean-architecture-migration

Migrate legacy modules step by step into Domain, Application, and Infrastructure layers.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill stepwise-clean-architecture-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stepwise-clean-architecture-migration
Source: https://github.com/SergeuMatyasov/dotnet-shared-skills/tree/main/stepwise-clean-architecture-migration
Command: npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill stepwise-clean-architecture-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Этот скилл обеспечивает безопасный пошаговый перенос legacy-кода в чистую архитектуру без масштабного переписывания и сохранение наблюдаемого поведения.

Core Features & Use Cases

  • Пошаговое планирование миграций модулей (Domain, Application, Infrastructure) с явным управлением зависимостями.
  • Введение портов и адаптеров вокруг существующего API без изменения поведения.
  • План миграции для одного модуля или сценария с явным учетом изменений и проверки эквивалентности.

Quick Start

Зафиксируй текущее поведение и подготовь план пошаговой миграции.

Frequently Asked Questions about stepwise-clean-architecture-migration

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

FAQPage Schema
How do I migrate legacy code to clean architecture without changing behavior?

Plan stepwise clean architecture migration by isolating modules into Domain, Application, and Infrastructure layers with explicit step checks and rollback points to safely separate dependencies without a full rewrite.

How do I separate a domain model from legacy infrastructure safely?

Ports and adapters introduce boundaries around existing legacy APIs during migration, allowing you to isolate domain logic and manage dependencies without altering the system's observed behavior.

Does stepwise clean architecture migration work for module-level migrations?

Stepwise migration reduces risk by providing explicit step checks and rollback points, ensuring you verify behavioral equivalence and log changes before safely removing legacy code.

When should I not use a big rewrite for legacy code?

Prepare for stepwise clean architecture migration by capturing and documenting the current behavior of your legacy software modules to establish a baseline for verifying behavioral equivalence.

What is the best way to plan a gradual clean architecture migration?

After completing stepwise clean architecture migration, execute downstream analysis on the newly separated Domain, Application, and Infrastructure layers to verify behavioral equivalence and ensure legacy code removal.