Skill

adr-writer

Generate an Architecture Decision Record (ADR) documenting a technical decision with context, options, and consequences

Install

npx claudepluginhub silviaare95/xari-plugins --plugin architect

Tool Access

This skill uses the workspace's default tool permissions.

SKILL.md

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

competitive-landscape

Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.

startup-business-analyst

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 8, 2026

Actions

View Source View Plugin View on GitHub View README

Steps

Read the codebase context — Check existing ADRs if a docs/adr/ or docs/decisions/ directory exists. Follow the existing numbering scheme.

Gather context — Understand what problem is being solved and what forces are at play (technical constraints, business requirements, team capacity).

Document options — List at least 2 alternatives that were considered. For each, note the key tradeoff.

Write the ADR — Use the template below.

Save the file — Write to docs/adr/NNNN-<kebab-case-title>.md using the next available number.

Output Format

Write the ADR as a markdown file:

# ADR-NNNN: <Title> **Status**: <proposed | accepted | deprecated | superseded by ADR-XXXX> **Date**: <YYYY-MM-DD> **Deciders**: <who was involved> ## Context <What is the issue that we're seeing that is motivating this decision or change?> ## Decision Drivers - <driver 1> - <driver 2> - <driver 3> ## Options Considered ### Option 1: <name> <Description> - **Pros**: <list> - **Cons**: <list> ### Option 2: <name> <Description> - **Pros**: <list> - **Cons**: <list> ## Decision <What is the change that we're proposing and/or doing?> ## Consequences ### Positive - <consequence> ### Negative - <consequence> ### Risks - <risk and mitigation>

ADR Writer

Write an Architecture Decision Record for: $0

Status: $1 (default: proposed)

Steps

Read the codebase context — Check existing ADRs if a docs/adr/ or docs/decisions/ directory exists. Follow the existing numbering scheme.
Gather context — Understand what problem is being solved and what forces are at play (technical constraints, business requirements, team capacity).
Document options — List at least 2 alternatives that were considered. For each, note the key tradeoff.
Write the ADR — Use the template below.
Save the file — Write to docs/adr/NNNN-<kebab-case-title>.md using the next available number.

Output Format

Write the ADR as a markdown file:

# ADR-NNNN: <Title>

**Status**: <proposed | accepted | deprecated | superseded by ADR-XXXX>
**Date**: <YYYY-MM-DD>
**Deciders**: <who was involved>

## Context

<What is the issue that we're seeing that is motivating this decision or change?>

## Decision Drivers

- <driver 1>
- <driver 2>
- <driver 3>

## Options Considered

### Option 1: <name>
<Description>
- **Pros**: <list>
- **Cons**: <list>

### Option 2: <name>
<Description>
- **Pros**: <list>
- **Cons**: <list>

## Decision

<What is the change that we're proposing and/or doing?>

## Consequences

### Positive
- <consequence>

### Negative
- <consequence>

### Risks
- <risk and mitigation>

Constraints

Follow existing ADR numbering if a directory exists
Keep it concise — ADRs are reference docs, not essays
The decision section should be 1-3 sentences
Always include at least one negative consequence (every decision has tradeoffs)