How does it support team collaboration?

It identifies necessary stakeholders (Security, SRE, Product) for different risk levels and generates communication plans to keep all affected teams informed during the evolution process.

What is an ADR and how does this skill help?

An Architecture Decision Record (ADR) captures the 'why' behind a technical choice. This skill automatically generates formatted ADRs based on your proposed changes, including context, consequences, and alternatives considered.

Does this skill help with infrastructure migrations?

Absolutely. It can analyze the impact on networking, security, and monitoring when adding or replacing underlying technology layers or cloud components.

How does the impact analysis work?

The skill maps out your project's component topology to identify direct and transitive dependencies, data migration needs, and API compatibility risks before you write a single line of code.

Can it handle breaking API changes?

Yes, it includes a specific workflow for breaking changes that plans for dual-support periods, versioning strategies, and identifies all affected consumers to ensure a smooth rollout.

Architecture Evolution

Name: Architecture Evolution
Author: jmagly

byjmagly

•

102

•

Infraestructura en la Nube

Manages complex software architecture changes through automated impact analysis, migration planning, and standardized ADR generation.

The Architecture Evolution skill provides a structured framework for managing the lifecycle of architectural transitions within a codebase. It automates the heavy lifting of system design by performing deep impact analysis on direct and transitive dependencies, generating comprehensive Architecture Decision Records (ADRs), and outlining detailed migration paths with built-in rollback strategies. Whether you are adding new components, deprecating legacy services, or introducing breaking API changes, this skill ensures architectural integrity, maintains documentation health, and facilitates clear communication across engineering teams.

Características Principales

01Standardized Architecture Decision Record (ADR) generation

02Cross-team stakeholder identification and coordination mapping

03Categorized change management for components and breaking API updates

04Automated impact analysis for direct and transitive dependencies

05102 GitHub stars

06Detailed migration planning with phase-by-phase rollback strategies

Casos de Uso

01Planning and documenting the transition from a monolithic service to a microservices architecture

02Analyzing the blast radius of breaking API changes across multiple internal and external consumers

03Managing the phased deprecation of legacy infrastructure while maintaining service availability

Características Principales

01Standardized Architecture Decision Record (ADR) generation

02Cross-team stakeholder identification and coordination mapping

03Categorized change management for components and breaking API updates

04Automated impact analysis for direct and transitive dependencies

05102 GitHub stars

06Detailed migration planning with phase-by-phase rollback strategies

Casos de Uso

01Planning and documenting the transition from a monolithic service to a microservices architecture

02Analyzing the blast radius of breaking API changes across multiple internal and external consumers

03Managing the phased deprecation of legacy infrastructure while maintaining service availability