Language Migration Planning
Move a component from one language to another with a safe path.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Plan a migration of [COMPONENT] from [OLD_LANGUAGE] to [NEW_LANGUAGE]. Reason: [REASON]. Size and complexity: [SIZE]. Team skills: [SKILLS]. Tests available: [TESTS]. Start by challenging the reason: could the problem be solved without a rewrite? Then, if it proceeds, plan by behaviour: write tests that specify current behaviour, port module by module with the same tests, run both implementations on the same inputs and compare outputs, and cut over gradually. Return a decision note on whether to proceed, a module order with risk, a comparison harness design, performance and memory checks, training needs, and the cost estimate as a range with assumptions. Highlight idioms that do not translate directly. Describe the migration of a small, self-contained piece first as a pilot, and the metrics to judge whether the rewrite delivered the benefit that justified it. Provide a plan for hiring or training, a way to keep the old system maintained during the overlap and a risk list that includes loss of undocumented behaviour. Include a go or no-go checkpoint after the pilot with clear criteria such as defect rate, performance and team confidence.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.