Explores migration paths to target states like microservices or cloud-native by analyzing codebase, documenting current architecture, options, and trade-offs.
npx claudepluginhub melodic-software/claude-code-plugins --plugin enterprise-architectureThis skill is limited to using the following tools:
Explore technical migration options by analyzing current architecture and documenting possible paths with trade-offs.
Compares current codebase architecture to target state, identifies technical gaps in stack, patterns, data, and infra, categorizes by type/complexity/risk, explores migration options. Use for tech roadmaps.
Manages architecture evolution by analyzing change impacts, generating ADRs, planning migrations, and coordinating execution for component additions, deprecations, and breaking changes.
Orchestrates full migration workflows from current state analysis through planning, incremental implementation, and verification for technologies, platforms, and architecture patterns with rollback planning.
Share bugs, ideas, or general feedback.
Explore technical migration options by analyzing current architecture and documenting possible paths with trade-offs.
/enterprise-architecture:explore-migration <target-state-description>
target-state-description (required): Description of the desired end state
/enterprise-architecture:explore-migration microservices architecture
/enterprise-architecture:explore-migration migrate from monolith to modular monolith
/enterprise-architecture:explore-migration replace legacy ORM with modern data access
Analyze Current State
Spawn Migration Explorer Agent
Use the migration-explorer agent to explore options. The agent:
Present Migration Options Display options organized by:
This command explores technical options. Complete migration planning requires additional business context (budget, team capacity, timeline, compliance needs). The output should inform broader planning discussions, not replace them.
## Migration Exploration: [Target State]
### Scope of This Analysis
This document explores technical migration options based on code structure analysis.
Complete migration planning requires additional business context:
- Budget constraints and approval processes
- Team capacity and skill availability
- Business timeline requirements
- Risk tolerance and compliance needs
### Current State
- Architecture pattern: [identified]
- Key dependencies: [list]
- Technical debt areas: [identified]
### Migration Option 1: [Name]
**Approach:** [Description]
**Pros:**
- [benefit]
**Cons:**
- [drawback]
**Estimated complexity:** [Low/Medium/High]
### Migration Option 2: [Name]
[Same structure]
### Migration Option 3: [Name]
[Same structure]
### Trade-off Comparison
| Factor | Option 1 | Option 2 | Option 3 |
| --- | --- | --- | --- |
| Complexity | ... | ... | ... |
| Risk | ... | ... | ... |
| Reversibility | ... | ... | ... |
### Recommended Next Steps
1. [Planning activity]
2. [Validation step]
3. [Stakeholder discussion]