cx-adr

Create and document Architecture Decision Records within development workflows.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/m19803261706/cx-workflow --skill cx-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cx-adr
Source: https://github.com/m19803261706/cx-workflow/tree/main/skills/cx-adr
Command: npx skills add https://github.com/m19803261706/cx-workflow --skill cx-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured way to record and manage architectural decisions, ensuring clarity and maintainability for complex projects.

Core Features & Use Cases

  • Record Architecture Decisions: Capture the context, rationale, and trade-offs behind key technical choices.
  • Maintain Decision History: Create a searchable archive of architectural decisions for future reference.
  • Use Case: When deciding between two database technologies for a new feature, use this Skill to document the evaluation criteria, pros and cons of each, and the final chosen solution.

Quick Start

Use the cx-adr skill to record a new architectural decision about choosing a caching strategy.

Frequently Asked Questions about cx-adr

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

FAQPage Schema
How do I document architectural decisions for a new software feature?

Document architectural decisions by creating Architecture Decision Records (ADRs) that capture the background, proposed solutions, comparisons, and final recommendations. This ensures technical choices are documented and traceable throughout the development workflow.

What is an Architecture Decision Record and when should I create one?

An Architecture Decision Record (ADR) is a structured document used to capture the context, rationale, and trade-offs behind key technical choices. You should create one when making architectural decisions for large-scale features to maintain decision history.

How do I manage technical debt and decision history for complex software projects?

Manage technical debt and decision history by using ADRs to create a searchable archive of architectural decisions. Recording the evaluation criteria, pros, cons, and chosen solutions provides future reference and traceability for complex projects.

Can I record trade-offs and evaluation criteria when choosing between database technologies?

Yes, you can record trade-offs and evaluation criteria when choosing between database technologies by documenting the context, proposed solutions, and comparisons. This captures the rationale behind the final chosen solution for future reference.

What's the best way to integrate architectural documentation into the design and planning phases?

Integrate architectural documentation into design and planning phases by generating ADRs that facilitate technical decision-making. This ensures architectural choices are documented, traceable, and aligned with the development workflow.