Skill

adr

Skill for creating and referencing Architecture Decision Records (ADR). Use when recording design decisions, reviewing past architectural choices, or checking existing ADRs before implementation. Common triggers: "create ADR", "record design decision", "check ADR", "architecture decision", "design rationale". Do NOT use for: general documentation, meeting notes, code comments, or changelog entries.

Install

npx claudepluginhub totto2727-org/monorepo --plugin totto2727

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Important architectural decisions are recorded as ADRs in `doc/adr/`.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 16, 2026

Actions

View Source View Plugin View on GitHub View README

ADR (Architecture Decision Record) Guidelines

Overview

Important architectural decisions are recorded as ADRs in doc/adr/. If the doc/adr/ directory does not exist, create it before writing the first ADR.

File Format

File Name

!echo "$(date +%Y-%m-%d)-title.md"

Frontmatter

All ADR files must have the following YAML frontmatter:

---
confirmed: false
---

Field	Type	Description
`confirmed`	boolean	`true`: Confirmed (generally immutable), `false`: Proposed (pending review)

Body Structure

---
confirmed: false
---

# ADR: Title

## Context

Background on why this decision is needed.

## Decision

The specific design decision. May include table design, API design, route design, etc.

## Impact

The scope of impact from this decision. New tables, changes to existing code, new routes, etc.

Operational Rules

Creation: Create with confirmed: false and confirm after review.
Confirmation: After user approval, change confirmed to true.
Immutability Principle: ADRs with confirmed: true must not be modified in principle.

ADR Creation Procedure

Ensure doc/adr/ directory exists (create if missing)
Create a YYYY-MM-DD-title.md file in doc/adr/
Set confirmed: false in the frontmatter
Describe the context, decision, and impact
Commit and submit for review
After approval, change to confirmed: true

Referencing ADRs

Check relevant ADRs before implementation and follow confirmed design decisions
Do not implement anything that contradicts an ADR with confirmed: true