migrate_stack
Plan a technology migration by comparing current and target stacks, assessing risks, mapping phased steps with rollback plans, and delivering a GO/NO-GO recommendation.
Instructions
Plan a technology migration: compare old vs new stack, risk assessment, phased migration steps with rollback plans, and GO/NO-GO recommendation.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"current_stack": "<current_stack>",
"target_stack": "<target_stack>",
"project_type": "<project_type>",
"scale": "<scale>"
},
"name": "migrate_stack"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scale | Yes | Project scale | |
| team_size | No | Team size (default: 3) | |
| project_type | Yes | Project type | |
| target_stack | Yes | Target technology IDs (e.g., ["nestjs", "postgresql"]) | |
| current_stack | Yes | Current technology IDs (e.g., ["express", "mongodb"]) |