absorb-adrs

Distill architectural decision records into structured rule-based documentation.

2|Updated Jun 20, 2026

Search Tags:#automation #architecture #documentation #refactoring #adr #governance

Ready to run

npx skills add https://github.com/Impractical-Instruments/reuben --skill absorb-adrs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: absorb-adrs
Source: https://github.com/Impractical-Instruments/reuben/tree/main/.claude/skills/absorb-adrs
Command: npx skills add https://github.com/Impractical-Instruments/reuben --skill absorb-adrs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill resolves the accumulation of stale Architectural Decision Records (ADRs) by distilling them into a permanent, maintainable rule-based documentation system, preventing knowledge drift and keeping the codebase's decision history clean.

Core Features & Use Cases

Automated Distillation: Transforms complex ADR chains into concise, present-tense normative rules and rationales.
Lifecycle Management: Automatically updates the derived rules index and safely removes obsolete ADR files.
Use Case: When a team reaches a consensus on a previously debated architectural pattern, use this skill to convert the scattered ADR history into a single, authoritative rule in the project's documentation.

Quick Start

Run the absorb-adrs skill to distill the solidified ADRs into the rules documentation and clean up the repository.

Frequently Asked Questions about absorb-adrs

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

FAQPage Schema

How do I consolidate architectural decision records into permanent rules?▼

To consolidate architectural decision records into permanent rules, this skill distills solidified ADRs into present-tense normative statements and rationales while maintaining index integrity.

What is the best way to clean up stale ADR files in a repository?▼

To clean up stale ADR files, the skill automatically removes obsolete architectural decision records from your repository after distilling their consensus knowledge into a structured rules documentation system.

How do I prevent knowledge drift from accumulated ADR documentation?▼

Preventing knowledge drift from accumulated ADR documentation requires distilling decision records into a maintainable rule-based format, which keeps the codebase's decision history clean and authoritative.

Do I need Python 3 to run the ADR distillation scripts?▼

Yes, you need Python 3 to execute the scaffolding and validation scripts that enforce the project's documentation conventions during the ADR distillation process.

Can I automate architectural governance documentation from existing ADRs?▼

Yes, you can automate architectural governance documentation by running this skill to synthesize scattered ADR history into a single authoritative rule and update the derived rules index automatically.

When should I not use automated ADR refactoring for documentation?▼

You should not use automated ADR refactoring when architectural decisions are still being debated, as the skill is designed to process solidified consensus rather than active proposals.