hexagonal-migration-planning

Analyze partially migrated codebases to generate Jira-ready migration tasks.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/thomassloboda/ai-stuff --skill hexagonal-migration-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hexagonal-migration-planning
Source: https://github.com/thomassloboda/ai-stuff/tree/main/skills/hexagonal-migration-planning
Command: npx skills add https://github.com/thomassloboda/ai-stuff --skill hexagonal-migration-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineering teams transform codebases that are only partially hexagonal into a clean, ports-and-adapters architecture by identifying migration gaps, architectural violations, and a concrete, incremental backlog of tasks.

Core Features & Use Cases

  • Identify non-hexagonal modules and boundaries in the current codebase.
  • Define a target hexagonal shape and map migration steps into small, Jira-ready tasks.
  • Produce a prioritized backlog that minimizes changes per task and preserves runtime behavior.

Quick Start

Analyze the target repository to surface the first set of concrete migration tasks you can start implementing immediately.

Frequently Asked Questions about hexagonal-migration-planning

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

FAQPage Schema
How do I plan a migration to a ports-and-adapters architecture for a partially refactored codebase?

Yes, it is designed for partially migrated codebases where legacy, framework-first, or persistence-coupled layers coexist with hexagonal targets, mapping the remaining gaps into small migration tasks.

How do I break down a hexagonal migration into Jira-ready tasks?

It identifies non-hexagonal boundaries in your current codebase, maps the migration steps into a prioritized backlog, and ensures each task minimizes changes to preserve runtime behavior.

Can I generate a migration backlog for a codebase with persistence-coupled layers?

It enforces incremental task decomposition to ensure each step minimizes changes per task while preserving runtime behavior.

What is the best way to extract module boundaries during a hexagonal migration?

The best way to extract module boundaries is to analyze the codebase against a target hexagonal shape, which identifies architectural violations and maps the extraction steps into a prioritized backlog.

Does this approach work for migrating legacy layers that already partially use hexagonal patterns?

Yes, this approach works for legacy layers by surfacing migration gaps and architectural violations, then producing a fine-grained, low-risk migration plan toward a clean ports-and-adapters architecture.