design-recordlisted

Record a design decision as an ADR, or update the living architecture document, in a repo that keeps a record of how it is built and why. Drafts the ADR body from the conversation, allocates the next number, maintains the ADR index, and edits named sections of architecture.md. Stages file edits only; never produces its own commit. Trigger with: 'record an ADR', 'document this decision', 'we decided X — write it up', 'why did we choose Y — capture it', 'update the architecture doc'.
xxthunder/xxthunder-agentic-skills · ★ 1 · Web & Frontend · score 66

Install: claude install-skill xxthunder/xxthunder-agentic-skills

# Design Record Writes the two artifacts that outlive a unit of work: the **ADR log** at `docs/adr/`, and the living **`architecture.md`**. Formats live in [references/adr-format.md](references/adr-format.md) and [references/architecture-format.md](references/architecture-format.md). This skill **stages file edits only**. It never creates a commit. Commits are the user's call — typically via `commit-helper` — so a record change can ride in the same commit as the code change that justifies it. ## Why this skill authors prose, unlike `backlog-ops` `backlog-ops` refuses to author content: it applies mechanical lifecycle operations and leaves all writing to `refinement`. This skill deliberately breaks that seam and drafts ADR bodies itself. The reason is frequency. Most decisions worth recording produce both an ADR and an architecture edit, so splitting authorship across a conversation skill and a mechanics skill would make recording a decision a two-invocation ritual on the highest-frequency path in the whole design — and a two-step ritual on the common path is how a practice quietly stops being followed. **Do not "fix" this inconsistency.** It is a considered divergence, recorded in ADR-0003 of this skill's home repository. Removing it reintroduces the friction it exists to avoid. ## When This Skill Triggers | Trigger phrase | Operation