strangler-conductor

Orchestrate API gateway routing, traffic shifts, and parity checks for mainframe cutovers.

1|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/duboc/mainframe-skills-mig --skill strangler-conductor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strangler-conductor
Source: https://github.com/duboc/mainframe-skills-mig/tree/main/skills/07-strangler-conductor
Command: npx skills add https://github.com/duboc/mainframe-skills-mig --skill strangler-conductor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Strangler Conductor coordinates phased cutover governance to migrate mainframe workloads safely, minimizing risk and downtime.

Core Features & Use Cases

  • Orchestrates phase-07 workflows with API gateway routing and traffic shifting
  • Tracks MIPS reduction and parity sign-off status for each workload
  • Generates rollback runbooks and alerts for on-call teams
  • Supports coexistence management and rollback readiness

Quick Start

Execute a guided cutover for a workload using the strangler-conductor instructions.

Frequently Asked Questions about strangler-conductor

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

FAQPage Schema
How do I automate mainframe migration cutover using the strangler fig pattern?

To orchestrate safe strangler fig cutovers for mainframe migrations, you automate API gateway routing, traffic shifting, and parity checks. This governs each phased workload transition while enforcing sign-off and tracking rollback readiness.

What is the best way to track MIPS reduction during a mainframe workload migration?

Tracking MIPS reduction during workload migration requires updating MIPS dashboards throughout the cutover governance process. This delivers auditable visibility into compute savings and validates operational impact for each migrated phase.

How do I enforce parity sign-off before shifting traffic in a strangler fig migration?

Enforcing parity sign-off before traffic shifts requires automated Phase 06 parity validation. This verifies the new workload matches mainframe outputs exactly, ensuring rollback readiness and preventing unsafe cutover progression.

Can I generate rollback runbooks automatically for mainframe workload cutovers?

Yes, rollback runbooks generate automatically during cutover orchestration. This produces actionable recovery documentation and alerts for on-call teams, maintaining coexistence management and rollback readiness throughout the migration lifecycle.

When do I need API gateway routing for mainframe migration coexistence?

API gateway routing is needed for mainframe migration coexistence when running parallel workloads during phased cutovers. It directs traffic between legacy and modern systems, enabling safe traffic-shift orchestration and parity validation before full transition.