C3 Architectural Change Manager FAQs

Question 1

Why does C3 Alter require an ADR for every change?

Accepted Answer

Using Architectural Decision Records (ADRs) ensures that every change has a documented rationale, impact assessment, and user approval, which prevents architectural drift and technical debt.

Question 2

Does C3 Alter write code or just documentation?

Accepted Answer

It manages both. It first updates the architectural documentation and ADRs to reflect the intended change, then generates and executes a plan to implement the corresponding code.

Question 3

How does the verification stage work?

Accepted Answer

After execution, the skill runs a C3 audit to verify that component IDs, diagrams, and linkages between the documentation and the source code are consistent and valid.

Question 4

What is the C3 architecture methodology?

Accepted Answer

C3 stands for Context-Container-Component, a design pattern that organizes software systems into hierarchical layers for better clarity, scalability, and maintainability.

Question 5

Can I use this skill without an existing .c3 directory?

Accepted Answer

No, this skill requires a pre-existing .c3/ directory structure as it relies on those files to analyze the current state and record new design decisions.

C3 Architectural Change Manager

Key Features

Use Cases

C3 Architectural Change Manager

Key Features

Use Cases