skills.rest
starrank-soft
starrank-softOFFICIAL
Explore all skills by this author →
GitHub

architecture-decision-records

Create structured Markdown architecture decision records with context and alternatives.

Updated Jun 24, 2026
Search Tags:#architecture#documentation#adr#best-practices#decision-making#software-design
One-click install
npx skills add https://github.com/starrank-soft/PixelArraySkill --skill architecture-decision-records-starrank-soft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/starrank-soft/PixelArraySkill/tree/main/skills/architecture-decision-records
Command: npx skills add https://github.com/starrank-soft/PixelArraySkill --skill architecture-decision-records-starrank-soft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of "tribal knowledge" loss by ensuring that critical architectural choices are documented, contextualized, and stored directly alongside the codebase rather than being lost in chat logs or memory.

Core Features & Use Cases

  • Automated ADR Generation: Creates structured Markdown documents based on the Michael Nygard format, including context, alternatives, and consequences.
  • Decision Tracking: Maintains an index of all architectural decisions, allowing developers to quickly understand the "why" behind existing code structures.
  • Use Case: When a team decides to switch from a REST API to GraphQL, this skill helps capture the specific trade-offs, rejected alternatives, and long-term impacts for future reference.

Quick Start

Ask the agent to record an architecture decision record for the current database migration strategy.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
How do I document architectural decisions to prevent tribal knowledge loss?▼

To document architectural decisions and prevent tribal knowledge loss, you can capture technical trade-offs, rejected alternatives, and rationale directly within your project repository using structured Markdown formats.

What is the best way to track the rationale behind software design choices?▼

The best way to track the rationale behind software design choices is by maintaining a centralized index of architecture decision records, ensuring developers can quickly discover the context and impacts of past decisions.

How do I create an architecture decision record for a database migration strategy?▼

You can create an architecture decision record for a database migration strategy by asking the agent to generate a structured document, which includes the context, alternatives, and long-term consequences of the decision.

Does this skill use a standardized template for architecture decision records?▼

Yes, this skill uses a standardized template system based on the Michael Nygard format to ensure consistency and discoverability of architectural decisions across the software development lifecycle.

When do I need to record architectural trade-offs in my codebase?▼

You need to record architectural trade-offs in your codebase whenever your team makes significant structural choices, such as switching from a REST API to GraphQL, to ensure the context is stored alongside the code rather than lost in chat logs.

Related Skills

Explore More Software Engineering Skills→
rjschierjschie

adr

Automate Architecture Decision Record creation, indexing, and repository updates.

Community
Intermediate
MadAppGangMadAppGang
7

adr-documentation

Create Architecture Decision Records with standardized sections for context, decision, consequences, and alternatives.

Official
Intermediate
1479089714790897
7

kwp-engineering-architecture

Create and evaluate Architecture Decision Records documenting technical trade-offs.

Community
Intermediate
jrodrigopucajrodrigopuca

context-compactor

Save conversational decisions, steps, and context into organized markdown files.

Community
Intermediate