fux-adr

Captures architecture decisions as indexed, code-linked Fux adr entries.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/arpitarya/fux --skill fux-adr-arpitarya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fux-adr
Source: https://github.com/arpitarya/fux/tree/main/archive/v0.1/fux/data/skills/adr
Command: npx skills add https://github.com/arpitarya/fux --skill fux-adr-arpitarya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architecture decisions recorded in free-floating documents rot, are never re-read, and lose their connection to the code they govern. This Skill turns recording a decision into a single step that produces a durable, indexed, code-linked entry. ## Core Features & Use Cases - One-step ADR capture: Scaffolds a structured adr entry with Decision, Context, Options considered, and Consequences sections via fux new adr. - Code and graph linkage: Sets code_refs to the governed code and edges for supersedes/implements relationships, so the decision appears in the index and graph. - Drift detection and recall: Entries are flagged stale by fux check when governed code changes and surfaced by fux recall when relevant. - Use Case: After choosing average-cost basis over FIFO, run the skill to record the decision, link it to the pricing code, deprecate the prior ADR, and have it resurface automatically during future related work. ## Quick Start Ask the assistant to record an architecture decision with /fux adr followed by the decision statement, such as "/fux adr use average-cost basis, not FIFO".

Frequently Asked Questions about fux-adr

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

FAQPage Schema
How do I record an architecture decision record with Fux?▼

Run /fux adr followed by the decision statement, then scaffold the entry with fux new adr and a kebab-case id. Fill the Decision, Context, Options considered, and Consequences sections, set code_refs and edges, then run fux build.

Why use a Fux adr entry instead of a decisions markdown file?▼

A free-floating decisions file rots and is never re-read. A Fux adr entry is indexed, linked to the code it governs, flagged stale by fux check when that code changes, and surfaced by fux recall when relevant.

How do I deprecate a superseded architecture decision?▼

In the new adr entry, add a supersedes edge pointing to the prior ADR and set the old entry's status to deprecated. This keeps the decision history intact while marking which record is current.

Does Fux detect when an ADR becomes outdated?▼

Yes. Because each adr entry declares code_refs to the code it governs, fux check flags the entry as stale when that code changes, prompting a review of the decision.

What sections should an architecture decision record contain?▼

Four sections: Decision stated as a present-tense rule, Context describing the forces behind it, Options considered with why each alternative lost, and Consequences covering what the decision commits to and rules out.