I Used 22 Prompts to Plan an Entire MuleSoft-to-.NET Migration. Here's the Playbook.

Last week I sat down to migrate a MuleSoft integration project to .NET 10 Minimal APIs. Instead of spending days writing migration specs, architecture docs, and agent team definitions manually, I paired with Claude to do it in a single conversation. 22 prompts. That's all it took to go from "where do I start?" to a fully structured, audited, ready-to-execute migration toolkit -- complete with scanner agents, phased prompts, integration patterns, and project scaffolding. Here's exactly how I did it, broken into a repeatable playbook any dev team can follow. Phase 1 -- Explore & Ground the AI in Your Codebase Most developers start an AI conversation with a wall of text explaining everything upfront. Don't. Start broad. Let the AI propose an approach first, then steer it. My opening prompt was simple: "What is the best approach to convert MuleSoft to C# Minimal API?" Claude came back with a solid general strategy -- Strangler Fig pattern, connector mapping tables, a phased approach. Good