adr-guide

Extract decision details and generate formal ADR entries.

5|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/technomensch/knowledge-graph --skill adr-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-guide
Source: https://github.com/technomensch/knowledge-graph/tree/main/skills/adr-guide
Command: npx skills add https://github.com/technomensch/knowledge-graph --skill adr-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting architectural decisions by guiding users to extract key information and generate clear, structured ADRs, reducing manual effort and ensuring consistency.

Core Features & Use Cases

  • Decision Capture: Helps users identify and extract decision topics, contexts, and rationales during technical discussions.
  • Template Generation: Pre-fills formal ADR entries based on user input, facilitating quick documentation.
  • Use Case: During a team meeting, a developer discusses switching databases. This Skill can guide the user to create a comprehensive ADR reflecting the discussion and options considered.

Quick Start

When discussing architectural choices, prompt the AI to help identify decision points and generate ADR drafts efficiently.

Frequently Asked Questions about adr-guide

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

FAQPage Schema
How do I document architectural decisions from technical discussions?

An ADR captures architectural decisions by documenting the context, options considered, and rationale behind a specific technical choice. This Skill structures those elements into formal entries, ensuring teams consistently record why specific technology stacks or patterns were chosen during discussions.

When do I need to create an ADR for software design choices?

You need to create an ADR whenever your team makes significant decisions regarding technology stacks, engineering patterns, or processes. This ensures the technical rationale and options considered are captured formally, providing future reference and reducing manual documentation effort.

What is the best way to generate ADR entries from engineering meetings?

The best way to generate ADR entries is to prompt the AI during or after engineering meetings to help identify decision topics and rationales. This Skill extracts those discussion details and pre-fills formal ADR templates, facilitating quick and consistent documentation.

Can I use this to document database switching decisions and other technology stack changes?

Yes, you can use this to document technology stack changes like switching databases. The Skill extracts the context, options, and rationales discussed and generates a comprehensive ADR entry reflecting the specific architectural choices considered by your team.

Does this ADR generation process require manual template formatting?

No, this ADR generation process does not require manual template formatting. The Skill pre-fills formal ADR entries based on your input, reducing manual effort by automatically structuring the extracted decision topics, contexts, and rationales.