skills.rest
DreamMacer
DreamMacerCOMMUNITY
Explore all skills by this author →
GitHub

arch-evolution

Plan architecture migrations, technical debt repayment, and governance workflows with phased roadmaps.

Updated Aug 31, 2026
Search Tags:#adr#technical debt#database schema#strangler fig#architecture migration#conway's law#technology radar
One-click install
npx skills add https://github.com/DreamMacer/jiuwenswarm --skill arch-evolution-dreammacer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-evolution
Source: https://github.com/DreamMacer/jiuwenswarm/tree/main/resources/agent/workspace/plugins/agent_templates/system-architect/skills/arch-evolution
Command: npx skills add https://github.com/DreamMacer/jiuwenswarm --skill arch-evolution-dreammacer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Modernizing a legacy system without breaking production is risky: teams lack a safe migration strategy, technical debt goes untracked, and architecture decisions drift away from team structure. This Skill provides a structured methodology for evolving architecture incrementally while keeping every step verifiable and reversible. ## Core Features & Use Cases - Strangler Fig Migration Planning: Step-by-step legacy replacement using API gateway facades, parallel running, and gradual traffic shifting (1% → 10% → 50% → 100%) with rollback at every stage. - Technical Debt Quantification: D1-D4 severity rating matrix, repayment prioritization rules, and debt kanban practices reserving 15-20% iteration capacity. - Database Schema Design & Migration: Index strategy (B-Tree, GIN, partial indexes), rollback-safe migrations, large-table phased changes, multi-tenancy patterns, and sharding decisions. - Architecture Governance: Team Topologies alignment with Conway's Law, ARB review process, ADR lifecycle management, and quarterly technology radar updates. - Use Case: A team needs to decompose a monolith into services. Use this Skill to assess the current state, define the target architecture, build a four-phase roadmap with rollback plans, and set up an ARB to govern the transition. ## Quick Start Ask the AI to create a phased migration roadmap from our current monolith to microservices using the strangler fig pattern, including technical debt ratings and rollback plans for each phase.

Frequently Asked Questions about arch-evolution

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

FAQPage Schema
How do I migrate a monolith to microservices without downtime?▼

Use the strangler fig pattern: place an API gateway in front of the legacy system, migrate one function at a time, run old and new in parallel, and shift traffic gradually (1% to 100%) with monitoring. Keep a one-click rollback route back to the legacy system at every stage.

How to prioritize technical debt repayment in a backlog?▼

Rate debt on a D1-D4 matrix by impact scope and urgency: D1 (core-path risks) is fixed immediately, D2 enters the next two iterations, D3 goes into quarterly planning, and D4 is fixed opportunistically. Reserve 15-20% of each iteration's capacity for debt repayment.

What is the safest way to change schema on large database tables?▼

For tables over 10 million rows, use a phased expand pattern: add a nullable column, dual-write old and new fields, backfill historical data in batches, switch reads to the new field, then drop the old column. Every migration must have a corresponding rollback.

Which multi-tenancy database pattern should I choose?▼

Choose by tenant count and isolation needs: database-per-tenant for under 50 tenants needing strong isolation, schema-per-tenant for 50-5000 cost-sensitive tenants, and shared schema with tenant_id plus row-level security for large-scale SaaS above 5000 tenants.

When should I not use the strangler fig pattern?▼

Avoid it when the system cannot sit behind a routing facade, when modules are too tightly coupled to migrate individually, or when a full rewrite is genuinely cheaper. This Skill covers evolution and governance; use a dedicated architecture design skill for greenfield selection instead.

Related Skills

Explore More Software Engineering Skills→
openJiuwen-aiopenJiuwen-ai
7.1k

arch-assess

Analyze existing codebases to map dependencies, draw as-is C4 diagrams, and assess architecture health.

Official
Intermediate
BeiBei-ClicBeiBei-Clic

gsd-autonomous

Execute remaining milestone phases through discuss, plan, and run steps.

Community
Advanced
JaviMontanoJaviMontano

system-architecture

Designs software architectures using C4 diagrams, ADRs, and quality attribute trade-off analysis.

Community
Advanced
SUN-UnderwritingSUN-Underwriting

database-architect

Design scalable database architectures with schema modeling and technology selection.

Official
Advanced