transformation-mapping

Assigns 7Rs migration strategies to components with dependencies, sequencing, and rollback procedures.

1|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill transformation-mapping-vanduc2514
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: transformation-mapping
Source: https://github.com/vanduc2514/hackathon-lablab-ibm-bob/tree/main/.bob/skills/transformation-mapping
Command: npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill transformation-mapping-vanduc2514

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding how to migrate each component of a legacy system is error-prone when done ad hoc. This Skill produces a structured strategy document that assigns every component a 7Rs migration approach with documented rationale, dependencies, and rollback plans. ## Core Features & Use Cases - 7Rs Strategy Assignment: Classifies each component as Rehost, Replatform, Refactor, Repurchase, Retire, Retain, or Relocate with documented rationale. - Dependency and Sequence Mapping: Builds a dependency graph and ordered migration sequence identifying parallel migration opportunities. - Rollback Planning: Defines per-component rollback procedures and validation checkpoints. - Use Case: Given a target architecture document and an assessment report for a Java monolith, generate a design_component_strategies.md file that maps each service to its migration strategy, risk level, and execution order. ## Quick Start Use the transformation-mapping skill to define 7Rs migration strategies for all components based on design_target_architecture.md and the assessment report.

Frequently Asked Questions about transformation-mapping

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

FAQPage Schema
How do I choose a migration strategy for each application component?▼

Apply the 7Rs framework by assessing each component's complexity, dependencies, and business criticality, then select Rehost, Replatform, Refactor, Repurchase, Retire, Retain, or Relocate based on risk, effort, and target architecture alignment. Document the rationale for each decision.

What is the 7Rs framework in cloud migration?▼

The 7Rs framework categorizes migration strategies as Rehost (lift-and-shift), Replatform (optimize for target), Refactor (re-architect), Repurchase (replace with SaaS), Retire (decommission), Retain (keep as-is), and Relocate (hypervisor-level move).

What inputs are needed to create a component strategy matrix?▼

You need a target architecture document (design_target_architecture.md), an assessment report with component inventory and complexity scores, and a migration plan covering timeline, resources, and risk tolerance.

How do I sequence component migrations with dependencies?▼

Migrate foundation layers first (infrastructure, databases, core services), identify independent components for parallel migration, distribute high-risk components across phases, and define validation checkpoints between migrations.

Does this skill execute the actual code migration?▼

No. It defines what strategy to apply per component, not how to implement it. Code transformation and execution are handled separately by a migration execution phase.