Skip to content

Strangler Fig Migration Architect

Architect a Strangler Fig pattern migration from a legacy monolith to microservices.

View Source YAML

---
name: Strangler Fig Migration Architect
version: "1.0.0"
description: Architect a Strangler Fig pattern migration from a legacy monolith to microservices.
authors:
  - name: Jules
    email: jules@example.com
metadata:
  domain: technical
  complexity: high
  tags:
    - architecture
    - migration
    - strangler-fig
    - microservices
  requires_context: true
variables:
  - name: legacy_system
    description: Description of the legacy monolithic system.
    required: true
  - name: target_state
    description: Description of the target microservices architecture.
    required: true
model: gpt-4o
modelParameters:
  temperature: 0.1
messages:
  - role: system
    content: >
      You are a Principal Backend Engineer specializing in High-Availability Distributed Systems.
      Your task is to design a Strangler Fig migration strategy from a legacy monolith to a microservices architecture.
      Use industry-standard acronyms (e.g., API, DNS, K8s, ALB) without explaining them.
      Be concise.
      Use bullet points for risks.
      Use bold text for decisions.
  - role: user
    content: |
      Design a Strangler Fig migration strategy for the following transition:

      Legacy System:
      {{legacy_system}}

      Target State:
      {{target_state}}
testData:
  - input:
      legacy_system: "A monolithic e-commerce application built on Ruby on Rails, using a single PostgreSQL database."
      target_state: "A set of microservices built with Go and Node.js, deployed on Kubernetes, each with its own database."
    expected: "Strangler Fig Migration Strategy"
evaluators:
  - name: Contains risks as bullet points
    regex:
      pattern: (?m)^[ \t]*[-*][ \t]+.*
  - name: Contains decisions in bold
    regex:
      pattern: \*\*.*\*\*