adr
Manages Architecture Decision Records (ADR) for tracking important architectural decisions
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install jellydn-my-ai-tools-adr
Repository
Skill path: skills/adr
Manages Architecture Decision Records (ADR) for tracking important architectural decisions
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: MIT.
Original source
Catalog source: SkillHub Club.
Repository owner: jellydn.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install adr into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/jellydn/my-ai-tools before adding adr to shared team environments
- Use adr for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: adr description: Manages Architecture Decision Records (ADR) for tracking important architectural decisions license: MIT compatibility: claude, opencode, amp, codex, gemini hint: Use when managing architecture decisions, creating ADRs, or tracking architectural choices user-invocable: true metadata: audience: all workflow: documentation --- # Architecture Decision Records (ADR) Provides a unified interface for managing Architecture Decision Records. ## Usage `/adr <ACTION> [ARGUMENTS]` ## Actions - **init [DIRECTORY]** - Initialize ADR directory structure - **new <TITLE>** - Create new ADR with given title - **supersede <NUMBER> <TITLE>** - Create ADR that supersedes existing one - **list** - List all ADRs in the project - **search <TERM>** - Search ADRs by content - **view <NUMBER>** - View specific ADR - **help** - Show this help ## What are ADRs? Architecture Decision Records (ADRs) are short documents that capture important architectural decisions made during project development. They help teams: - Record the context and reasoning behind decisions - Track the evolution of architectural choices - Onboard new team members - Avoid revisiting already-settled decisions ## ADR Structure Each ADR typically contains: - **Title**: Brief description of the decision - **Status**: Proposed, Accepted, Deprecated, Superseded - **Context**: The situation requiring a decision - **Decision**: The chosen solution - **Consequences**: Positive and negative outcomes ## ADR Template A template is available at `$SKILL_PATH/templates/adr-template.md`: ```markdown # [NUMBER]. [TITLE] Date: [DATE] ## Status [Proposed | Accepted | Deprecated | Superseded by [ADR-NUMBER]] ## Context [Describe the context and problem statement] ## Decision [Describe the decision and solution] ## Consequences ### Positive - [Positive outcome 1] - [Positive outcome 2] ### Negative - [Negative outcome 1] - [Risk or trade-off] ``` ## ADR Directory Detection Common ADR locations to check: - `doc/adr/` (default) - `docs/adr/` - `docs/architecture/decisions/` - `architecture/decisions/` ## Process Examples ### Create new ADR: ```bash /adr new "Use PostgreSQL for primary database" ``` ### List all ADRs: ```bash /adr list ``` ### Search ADRs: ```bash /adr search "database" ``` ### View specific ADR: ```bash /adr view 5 ```