skills.rest
PaulKinlan
PaulKinlanCOMMUNITY
Explore all skills by this author →
Website𝕏@paul_kinlanGitHub

decision-record

Creates Architecture Decision Records documenting context, rationale, consequences, and numbered conflicts with prior decisions.

2|Updated Feb 4, 2026
Search Tags:#architecture#decision making#documentation#adr#record keeping#process
One-click install
npx skills add https://github.com/PaulKinlan/docker-agent-test --skill decision-record-paulkinlan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-record
Source: https://github.com/PaulKinlan/docker-agent-test/tree/main/config/skills/architect/decision-record
Command: npx skills add https://github.com/PaulKinlan/docker-agent-test --skill decision-record-paulkinlan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you systematically document important decisions, ensuring clarity, accountability, and a historical record of why choices were made.

Core Features & Use Cases

  • Structured Decision Documentation: Guides users through creating Architecture Decision Records (ADRs) with predefined sections for context, decision, consequences, and alternatives.
  • Automated Numbering and Storage: Assigns sequential ADR numbers and stores them in a designated directory.
  • Use Case: When your team decides to adopt a new technology stack, use this Skill to create an ADR detailing the rationale, alternatives considered, and potential impacts, ensuring everyone understands the decision's foundation.

Quick Start

Use the decision-record skill to write a new ADR about adopting a new CI/CD tool.

Frequently Asked Questions about decision-record

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

FAQPage Schema
How do I document architecture decisions to keep a record of context and rationale?▼

To document architecture decisions, you generate Architecture Decision Records (ADRs) through a structured process capturing context, rationale, and consequences. This ensures your decision making is auditable and understandable for technical and organizational contexts.

What is an Architecture Decision Record used for in software engineering?▼

An Architecture Decision Record is used for documenting key technical decisions, ensuring clarity, accountability, and a historical record of why choices were made. It provides predefined sections for context, alternatives, and potential impacts.

How do I structure an ADR when adopting a new technology stack?▼

You structure an ADR by using predefined sections for context, decision, consequences, and alternatives. This structured decision documentation details the rationale and potential impacts of adopting a new technology stack.

Can I check a new architecture decision for conflicts with prior decisions?▼

Yes, you can check new architecture decisions for conflicts with prior decisions. The ADR process supports sequential numbering and conflict checking with previous records to maintain consistency.

How are ADRs numbered and stored during the documentation process?▼

ADRs are managed through automated numbering and storage, assigning sequential ADR numbers and storing them in a designated directory. This record keeping ensures artifacts are registered and easily accessible.

Related Skills

Explore More Software Engineering Skills→
vndkubivndkubi

generate-adr

Generate Architecture Decision Records with a standard template.

Community
Advanced
infantesromeroadrianinfantesromeroadrian

adr-new

Generate markdown Architecture Decision Records from a YAML template with sequential numbering.

Community
Intermediate
tmalcolm-0607tmalcolm-0607

mad-adr

Create Architecture Decision Records compliant with MADR 4.0 format and manage their lifecycle statuses.

Community
Advanced
CygnusfearCygnusfear
5

the-archivist

Document engineering decisions as ADRs with rationale and decision logs.

Community
Advanced