c3-alter

Manage architectural changes through a staged ADR-driven workflow for C3 artifacts.

2|1|Updated Jan 5, 2026

Search Tags:#architecture #documentation #adr #c3 #change-management #decision-record #layer-navigation

Ready to run

npx skills add https://github.com/lagz0ne/prev-cli --skill c3-alter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: c3-alter
Source: https://github.com/lagz0ne/prev-cli/tree/main/.opencode/skill/c3-alter
Command: npx skills add https://github.com/lagz0ne/prev-cli --skill c3-alter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of managing architectural changes by enforcing an ADR-driven workflow for C3 documents.

Core Features & Use Cases

Enforces staged ADR processes for design changes, refactors, feature additions, and diagram updates.
Generates and references ADR records (e.g., .c3/adr/adr-YYYYMMDD-{slug}.md) and links related documentation.
Integrates with existing references (e.g., .opencode/references) to ensure routing, questions, and decisions are traceable.

Quick Start

Follow Stage 1 through Stage 7 to document and implement an ADR-driven change for a C3 component.

Frequently Asked Questions about c3-alter

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

FAQPage Schema

How do I manage architectural changes using ADRs in my repository?▼

It enforces an ADR-driven workflow to manage architectural changes for C3 documents. By applying a staged process, it generates dated ADR records and links related documentation to ensure design changes, refactors, and feature additions are fully traceable.

What is the process for creating an Architecture Decision Record for a C3 component?▼

Creating an Architecture Decision Record follows a structured Stage 1 through Stage 7 workflow. This stage-based decision making process ensures design changes and diagram updates are systematically documented and integrated with existing references.

How does ADR-driven change management integrate with existing repository references?▼

ADR-driven change management integrates with existing references like the .opencode/references directory. This integration ensures that routing, questions, and decisions remain traceable across newly generated ADR records and C3 artifacts.

When do I need a staged ADR workflow for refactors or diagram updates?▼

You need a staged ADR workflow whenever executing design changes, refactors, feature additions, or diagram updates across C3 artifacts. It enforces stage-based decision making to maintain architectural integrity and documentation consistency.

Can I use ADR records to coordinate feature additions across multiple C3 documents?▼

Yes, you can use ADR records to coordinate feature additions across multiple C3 documents. The workflow generates records like .c3/adr/adr-YYYYMMDD-{slug}.md and applies stage-based decision making to synchronize changes.

What is the best way to document architectural decisions for traceability?▼

The best way to document architectural decisions for traceability is using an ADR-driven workflow with stage-based decision making. It automatically generates ADR records and integrates with reference directories to keep routing and decisions linked.