// Manage Architecture Decision Records (ADRs) using adr-tools. Use this to initialize, create, list, and link ADRs to document architectural evolution.
| name | manage-adr |
| description | Manage Architecture Decision Records (ADRs) using adr-tools. Use this to initialize, create, list, and link ADRs to document architectural evolution. |
Architecture Decision Records (ADRs) are a lightweight way to document the "why" behind significant technical choices.
list).If ADRs are not yet initialized in the project, run:
adr init docs/adr
This ensures records are created in docs/adr.
To create a new ADR, use the provided script to ensure non-interactive creation:
.cursor/skills/manage-adr/scripts/create-adr.sh "Title of the ADR"
After creation, the script will output the filename. You MUST then edit the file to fill in the Context, Decision, and Consequences.
If a new decision replaces an old one, use the -s flag:
.cursor/skills/manage-adr/scripts/create-adr.sh -s <old-adr-number> "New Decision Title"
To link two existing ADRs (e.g., ADR 12 amends ADR 10):
adr link 12 Amends 10 "Amended by"
adr listread_file docs/adr/NNNN-title.mdadr generate tocadr generate graph | dot -Tpng -o adr-graph.pngIMPORTANT: After creating or superseding an ADR, you MUST perform a synchronization pass:
CLAUDE.md if the decision affects core architectural rules, testing standards, or monorepo structure.AGENTS.md if the decision introduces new agents, skills, or modifies existing responsibilities.CLAUDE.md for details.references/adr-concepts.md for more details on the ADR philosophy.assets/template.md as a guide.Scaffold and standardize new dbt-helpers plugins (Warehouse, Tool, or Schema). Use when starting a new plugin implementation or updating plugin discovery configuration.
Comprehensive workflow for creating, implementing, and validating Agent Skills. Use when asked to "create a new skill", "author a skill", "add a capability", or when standardizing project-specific workflows. Support for platform detection (Cursor, Claude Code, Gemini CLI, Codex) and template selection.
Set up the development environment for the project. Use when starting work on the project, when dependencies are out of sync, or to fix environment setup failures.
Implement and run End-to-End tests using golden output comparison. Use when verifying CLI behavior, plan generation, or full project execution.
Set up and run integration tests using Testcontainers. Use when testing warehouse adapters against real database engines or verifying filesystem-dependent operations.
Implement and use Nullable Infrastructure adapters for mock-free testing. Use when writing unit tests for core logic, implementing infrastructure adapters, or setting up test fixtures.