mine.adrs

Create and maintain Architecture Decision Records with a standardized template.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/NodeJSmith/Claudefiles --skill mine-adrs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mine.adrs
Source: https://github.com/NodeJSmith/Claudefiles/tree/main/skills/mine.adrs
Command: npx skills add https://github.com/NodeJSmith/Claudefiles --skill mine-adrs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured way to document significant architectural and technical decisions, ensuring clarity, traceability, and a shared understanding of project evolution.

Core Features & Use Cases

  • Decision Recording: Captures context, choices, consequences, and alternatives for key project decisions.
  • Standardized Format: Utilizes a consistent template for Architecture Decision Records (ADRs).
  • Workflow Integration: Connects with research and audit skills for a comprehensive decision-making process.
  • Use Case: When deciding on a new database technology, use this skill to record the reasons for the choice, the alternatives considered, and the expected impact on the project.

Quick Start

Create a new Architecture Decision Record for the project.

Frequently Asked Questions about mine.adrs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architectural decisions for my project?

You document architectural decisions by creating Architecture Decision Records (ADRs) that capture context, choices, consequences, and alternatives for significant technical choices. This ensures clarity and traceability of project evolution.

What should be included in an architecture decision record?

An architecture decision record should include the context, decision, consequences, and alternatives for a significant technical choice. This standardized format ensures a shared understanding of why specific architectural choices were made.

When do I need to create an architecture decision record?

You need to create an architecture decision record when making significant technical choices, such as selecting a new database technology. It records the reasons for the choice, alternatives considered, and expected project impact.

What is the best way to track the evolution of technical decisions over time?

The best way to track technical decisions is using an append-only system for architecture decision records. This ensures the architectural evolution is documented sequentially without altering past decision context.