architecture-evolution

Analyze change impact, generate ADRs, and plan migration paths.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/robit-man/transcribe-cli --skill architecture-evolution-robit-man
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-evolution
Source: https://github.com/robit-man/transcribe-cli/tree/main/.claude/skills/architecture-evolution
Command: npx skills add https://github.com/robit-man/transcribe-cli --skill architecture-evolution-robit-man

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines the process of managing architectural changes within a system, ensuring controlled evolution, impact analysis, and proper documentation.

Core Features & Use Cases

  • Impact Analysis: Assesses the ripple effects of proposed changes on various system components and dependencies.
  • ADR Generation: Automatically creates Architecture Decision Records to document significant architectural choices.
  • Migration Planning: Develops phased plans for migrating components or technologies.
  • Use Case: When introducing a new microservice, this skill can analyze its dependencies, generate an ADR, and outline a migration strategy for integrating it into the existing architecture.

Quick Start

Evolve the architecture to add a new caching layer.

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 proposed architecture changes on existing system dependencies?

To analyze architecture impact, this skill assesses ripple effects on system components and cross-team dependencies, tracking breaking changes to ensure controlled evolution. It evaluates proposed changes against the existing system to maintain overall architecture health.

What is an Architecture Decision Record and when do I need one for migration planning?

An Architecture Decision Record (ADR) documents significant architectural choices. You need ADR generation during migration planning to record decisions, coordinate cross-team dependencies, and outline phased strategies for integrating new components or technologies.

Can I use this to plan a phased migration path for introducing a new microservice?

Yes, you can use this for microservice migration by analyzing dependencies, generating an ADR for the integration, and developing a phased migration plan. It coordinates cross-team dependencies to safely integrate the new service.

What is the best way to manage breaking changes and coordinate cross-team dependencies during architecture evolution?

The best way to manage breaking changes is through structured change management processes that track dependencies and generate ADRs. This skill coordinates cross-team dependencies and maintains architecture health during evolution.

When should I not use automated ADR generation for architecture change management?

You should avoid automated ADR generation for trivial changes that do not impact system components or cross-team dependencies. It is designed for significant architectural evolution requiring impact analysis and migration planning.

How do I document significant architectural choices and track architecture health during system evolution?

You document architectural choices by generating Architecture Decision Records and tracking breaking changes. This skill maintains architecture health through structured processes, analyzing impacts and coordinating dependencies during system evolution.