mxDecision

Create and maintain Architecture Decision Records in the mxLore knowledge DB via MCP-Tools.

29|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/MicrotronX/mxLore --skill mxdecision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mxDecision
Source: https://github.com/MicrotronX/mxLore/tree/main/claude-setup/skills/mxDecision
Command: npx skills add https://github.com/MicrotronX/mxLore --skill mxdecision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

mxDecision enables teams to create and manage Architecture Decision Records (ADRs) directly in the mxLore knowledge base via MCP-Tools, ensuring traceability, supersedes, and lifecycle management. It centralizes decisions, captures context, and links to related specs and plans for coherent architectural governance.

Core Features & Use Cases

  • Create ADRs in the knowledge DB with automatic numbering and server-generated slugs.
  • Maintain supersedes chains and status transitions, including proposed, accepted, implemented, superseded, deprecated.
  • Link ADRs to related specifications or plans and generate follow-ups using the included ADR template and assets.
  • Use cases: capturing critical architectural choices during design sessions, auditing decisions during reviews, and migrating decisions across projects.

Quick Start

Provide the ADR title and initial context to generate and store an Architecture Decision Record in the mxLore knowledge base.

Frequently Asked Questions about mxDecision

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

FAQPage Schema
How do I create and manage Architecture Decision Records in a knowledge base?

Architecture Decision Records are created and managed in the mxLore knowledge base via MCP-Tools, supporting automatic slug derivation, status transitions, and relation linking to related specs and plans.

How does an ADR tool handle status transitions and supersedes updates?

ADR status transitions and supersedes updates are handled through lifecycle management, tracking states like proposed, accepted, implemented, superseded, and deprecated to ensure auditable, traceable decisions.

Can I link architecture decisions to related specifications and plans?

Architecture decisions can be linked to related specifications or plans to generate follow-ups, capturing context and ensuring coherent architectural governance across projects.

What is the best way to capture architectural choices during design sessions?

Capturing critical architectural choices during design sessions is done by providing the ADR title and initial context to generate and store a traceable Architecture Decision Record in the knowledge base.

Do I need MCP-Tools to maintain ADR templates and local fallback?

MCP-Tools are required to maintain ADR templates and local fallback in the mxLore knowledge DB, ensuring decisions remain auditable and traceable across projects.

Why does automatic slug derivation matter for architecture decision documentation?

Automatic slug derivation matters for architecture decision documentation because it enables server-generated slugs for consistent numbering, ensuring traceable records without manual naming conflicts.