Compare current state to target state architecture. Scoped to technical options - requires business context for complete analysis.
Compares current vs target architecture by analyzing code structure to identify technical gaps and migration options. Triggers when you request gap analysis, roadmap planning, or migration exploration, but requires business context for complete strategy.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install soft-skills@melodic-softwareThis skill is limited to using the following tools:
Use this skill when you need to:
Keywords: gap analysis, current state, target state, as-is, to-be, roadmap, migration, baseline, transition
IMPORTANT: This analysis covers technical migration options based on code structure.
Complete migration planning requires business context including:
- Budgets and timelines (external to code)
- Organizational structure (external to code)
- Technical debt priorities (partially in code)
- Resource availability (external to code)
Use this as input to broader planning discussions, not as a complete migration strategy.
What can be extracted from code (Zachman rows 4-6):
| Aspect | Source | Analysis |
|---|---|---|
| Technology stack | package.json, pom.xml, etc. | Frameworks, libraries, versions |
| Architecture patterns | Code structure | Monolith, microservices, layers |
| Data storage | Config files | Databases, caches, queues |
| Integration points | API definitions | REST, GraphQL, messaging |
| Infrastructure | IaC files | Cloud resources, networking |
What requires human input (Zachman rows 1-3):
| Aspect | Source Needed |
|---|---|
| Business capabilities | Business documentation |
| Process flows | Stakeholder interviews |
| Strategic alignment | Strategy documents |
Target state should include:
For each architecture dimension:
| Dimension | Current | Target | Gap |
|---|---|---|---|
| Compute | VM-based | Containerized | Container adoption |
| Data | Monolithic DB | Service-per-DB | Database decomposition |
| Integration | Point-to-point | Event-driven | Event mesh implementation |
| ... | ... | ... | ... |
Classify each gap by:
Type:
Complexity:
Risk:
For each gap, document:
## Gap: [Gap Name]
### Current State
[Description of current situation]
### Target State
[Description of desired situation]
### Technical Options
#### Option A: [Name]
- **Approach**: [Description]
- **Pros**: [List]
- **Cons**: [List]
- **Technical complexity**: [Low/Medium/High]
- **Dependencies**: [List]
#### Option B: [Name]
- **Approach**: [Description]
- **Pros**: [List]
- **Cons**: [List]
- **Technical complexity**: [Low/Medium/High]
- **Dependencies**: [List]
### Recommendation
[Technical recommendation with rationale]
### Business Context Required
[What business input is needed to finalize decision]
# Gap Analysis: [System Name]
**Date**: YYYY-MM-DD
**Scope**: [What's included/excluded]
## Scope Limitations
This analysis covers 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
These options should inform broader planning discussions, not replace them.
## Current State Summary
[Overview of as-is architecture]
## Target State Summary
[Overview of to-be architecture]
## Gap Inventory
| ID | Gap | Type | Complexity | Priority |
| --- | --- | --- | --- | --- |
| G1 | ... | ... | ... | TBD |
| G2 | ... | ... | ... | TBD |
## Detailed Gap Analysis
### G1: [Gap Name]
[Detailed analysis per template above]
## Technical Dependencies
[Dependency graph showing which gaps must be addressed first]
## Recommended Sequencing
[Technical sequencing based on dependencies]
## Business Decisions Required
[List of decisions that require business input]
Gap analysis documents should be stored at:
/architecture/
gap-analysis.md
/transitions/
transition-1.md
transition-2.md
Date: 2025-12-05 Model: claude-opus-4-5-20251101
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.