pair-capability-record-decision

Record technical decisions as ADRs or ADLs and update adoption files.

6|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/foomakers/pair --skill pair-capability-record-decision
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pair-capability-record-decision
Source: https://github.com/foomakers/pair/tree/main/.claude/skills/pair-capability-record-decision
Command: npx skills add https://github.com/foomakers/pair --skill pair-capability-record-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting technical decisions, ensuring that architectural choices and non-architectural preferences are consistently recorded and reflected in project adoption files.

Core Features & Use Cases

  • Decision Recording: Creates either an Architectural Decision Record (ADR) or an Adoption Decision Log (ADL) entry.
  • Adoption File Updates: Automatically updates relevant adoption files (e.g., tech-stack.md, architecture.md) to maintain a single source of truth.
  • Use Case: When deciding on a new database technology, use this Skill to create an ADR, detailing the context, options considered, the final decision, and its impact, while simultaneously updating the tech-stack.md file.

Quick Start

Use the pair-capability-record-decision skill to record an architectural decision about the new caching strategy with the topic 'redis-caching'.

Frequently Asked Questions about pair-capability-record-decision

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

FAQPage Schema
How do I record architectural decisions and keep project documentation in sync?▼

Recording architectural decisions involves creating ADRs while updating adoption files like tech-stack.md to maintain a single source of truth for project standards.

What is the difference between an ADR and an ADL for decision documentation?▼

An ADR (Architectural Decision Record) documents structural architectural choices, whereas an ADL (Adoption Decision Log) records non-architectural preferences, with both updating your project's adoption files accordingly.

When do I need to update adoption files like tech-stack.md or architecture.md?▼

You need to update adoption files like tech-stack.md or architecture.md whenever a new technical decision is made, ensuring the documentation reflects the current context, options considered, and final choices.

What is the best way to document a new database technology choice in project standards?▼

The best way to document a new database technology choice is to create an ADR detailing the context and impact, while simultaneously updating the tech-stack.md adoption file to maintain consistency.

Can I log non-architectural working preferences without creating full ADRs?▼

Yes, you can log non-architectural working preferences by creating an Adoption Decision Log (ADL) entry, which then updates relevant project documentation like way-of-working.md to track standards.

How does updating decision logs maintain a single source of truth for project standards?▼

Updating decision logs maintains a single source of truth by ensuring every technical choice is recorded as an ADR or ADL and directly reflected in corresponding adoption files like architecture.md.