architecture-evolution

Analyze architecture change impact and generate ADRs and migration plans.

175|26|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/jmagly/ai-writing-guide --skill architecture-evolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-evolution
Source: https://github.com/jmagly/ai-writing-guide/tree/main/.factory/skills/architecture-evolution
Command: npx skills add https://github.com/jmagly/ai-writing-guide --skill architecture-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires decision-support, project-awareness, artifact-metadata, and includes references (resource) components.

What problem does it solve?

This Skill eliminates architectural drift by automatically managing architecture changes with impact analysis, ADR generation, and migration planning.

Quick Start

When you say "evolve architecture to add caching layer", this Skill analyzes the impact, generates migration plans, and coordinates cross-team dependencies for controlled architecture evolution.

Example Output

"Architecture Evolution: Add Caching Layer

Impact Analysis:

  • Direct dependencies: 3 services
  • Data stores: 1 new (Redis)
  • API changes: None
  • Performance: +40% expected improvement

Migration Plan: Phase 1: Deploy Redis cluster (Week 1) Phase 2: Add cache-aside to read paths (Week 2)

  • Performance: +40% expected improvement

Risk: Medium

  • Rollback: Disable cache reads, direct DB

Generated:

  • ADR: .aiwg/architecture/adr-023-caching-layer.md
  • Migration Guide: .aiwg/architecture/migrations/add-caching.md"

Frequently Asked Questions about architecture-evolution

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

FAQPage Schema
How do I analyze the impact of architecture changes across my services?

Architecture evolution impact analysis automatically maps direct and transitive dependencies, data stores, and API changes across services. It identifies affected components, quantifies risk, and reveals cross-team coordination needs before deployment.

Can I generate migration plans for technology changes automatically?

Yes. Migration planning generates phased rollout strategies with rollback procedures for technology migrations, component additions, and deprecations. It designs execution phases, identifies dependencies, and coordinates multi-team handoffs.

What's the best way to document architecture decisions during system evolution?

Architecture evolution generates Architecture Decision Records (ADRs) automatically during change planning. ADRs capture rationale, alternatives, and consequences, creating living documentation linked to migration guides and stakeholder communications.

How do I manage breaking changes without disrupting dependent teams?

Breaking change management uses transitive dependency analysis to identify all affected services and APIs, then coordinates rollout phases with rollback plans. Generated migration guides and stakeholder communications enable controlled deprecation cycles.

Can architecture evolution handle data store changes and API deprecations?

Yes. The Skill evaluates data store additions, API changes, and breaking changes as part of impact assessment. It generates migration paths and risk profiles specific to each change type, supporting comprehensive architectural refactoring.

Do I need to manually coordinate across teams when evolving architecture?

No. Architecture evolution enables cross-team coordination automatically by analyzing shared dependencies, generating stakeholder communication plans, and producing migration guides that align implementation schedules across services.