document-architectural-evolution

Name: document-architectural-evolution
Availability: InStock
Author: constellize

Generate an Architectural Evolution document with architecture, triggers, migration path, and lessons.

1|Updated Feb 16, 2026

Search Tags:#documentation #adr #traceability #system-design #decision-record #migration-path #architectural-evolution

Ready to run

npx skills add https://github.com/constellize/marketplace --skill document-architectural-evolution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document-architectural-evolution
Source: https://github.com/constellize/marketplace/tree/main/plugins/constellize-evolution/skills/document-architectural-evolution
Command: npx skills add https://github.com/constellize/marketplace --skill document-architectural-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents the rationale and context behind architectural changes, ensuring future teams understand why decisions were made and how they evolved over time.

Core Features & Use Cases

Captures the original architecture, evolution triggers, migration path, and the final design with stated trade-offs.
Provides auditable traceability by linking ADRs and decision records to each evolution step.
Records constraints, lessons learned, and guardrails to guide future evolution and maintenance.

Quick Start

Generate a complete Architectural Evolution document for a system, including original architecture, evolution triggers, migration plan, and learned lessons.

Frequently Asked Questions about document-architectural-evolution

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

FAQPage Schema

How do I document architectural evolution and system migration paths?▼

Document architectural evolution by generating a complete record that captures the original architecture, evolution triggers, migration path, and lessons learned to preserve context for future teams.

What is the best way to link ADRs for auditable system design traceability?▼

Linking ADRs and decision records to each evolution step provides auditable traceability, ensuring future teams understand why specific architectural decisions and constraints were made.

Why should I record constraints and trade-offs during a system migration?▼

Recording constraints and trade-offs during system migration documents the rationale behind architectural changes, establishing guardrails and lessons learned to guide future maintenance and evolution.

When do I need an architectural decision record for software evolution?▼

You need an architectural decision record when a system undergoes structural changes, requiring documentation of evolution triggers, migration strategies, and stated trade-offs to maintain an auditable history.

Does this approach work for documenting legacy system migration plans?▼

Yes, this approach works for evolution projects across software systems, specifically including documenting migration plans, constraints, and lessons learned for legacy migrations.