adr

Generates structured Architecture Decision Records for technical choices with trade-off analysis.

Updated Jul 13, 2024
One-click install
npx skills add https://github.com/bearbinary/Jarvy --skill adr-bearbinary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/bearbinary/Jarvy/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/bearbinary/Jarvy --skill adr-bearbinary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you create structured documentation for important architectural and technical decisions, ensuring clarity and a shared understanding within your team.

Core Features & Use Cases

  • Structured Decision Recording: Guides you through capturing context, decision drivers, considered options, and outcomes.
  • Trade-off Analysis: Facilitates explicit discussion and documentation of pros and cons for each option.
  • Fact-Checking Integration: Prompts for verification of technical claims using web search and context analysis.
  • Use Case: When deciding on a new database technology, this skill will help you document the problem, list alternatives like PostgreSQL vs. MongoDB, analyze their trade-offs, and record the final decision with justifications.

Quick Start

Use the adr skill to create a new architecture decision record for choosing a messaging queue.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I document technical decisions and their trade-offs for my team?

Document technical decisions by generating structured Architecture Decision Records that capture context, decision drivers, considered options, and outcomes. This skill guides you through trade-off analysis to ensure clarity and shared understanding within your team.

What is an Architecture Decision Record and when do I need one?

An Architecture Decision Record is structured documentation for important architectural choices. You need one when selecting tools, setting conventions, or choosing architectural patterns, ensuring the problem context and outcome justifications are explicitly recorded.

How do I create a step-by-step trade-off analysis for database selection?

Create a trade-off analysis by listing alternatives like PostgreSQL versus MongoDB, then documenting the pros and cons for each option. This skill guides you through evaluating decision drivers to record the final database choice with justifications.

Can I fact-check technical claims during the architecture decision process?

You can fact-check technical claims during the architecture decision process using integrated web search and context analysis. This verifies the accuracy of statements made about considered options before finalizing the decision record.