Adr
Adr helps you systematically capture architecture decisions with context, options, and consequences. Create numbered decision records, browse your decision history, and search past choices to avoid redundant deliberation.
Adr lets you create and manage architecture decision records to document your project's technical choices.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-26
Adr lets you create and manage architecture decision records to document your project's technical choices. Adr helps you systematically capture architecture decisions with context, options, and consequences. Create numbered decision records, browse your decision history, and search past choices to avoid redundant deliberation.
Use it when
- Adr guides you through creating numbered decision records using a structured template.
- Adr's template captures the essential elements of an architectural decision: the decision itself, the context and problem it addresses.
Install
alfredolopez80/multi-agent-ralph-loop/adr · repository language: Shell
generated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is an ADR and how does Adr help me use it?
Adr helps you create and manage Architecture Decision Records (ADRs)—numbered documents that capture architectural choices, their rationale, and consequences. Adr systematically captures architecture decisions with context, options, and consequences, letting you build a searchable decision history so your team can review past choices and avoid redundant deliberation.
How do I create ADR documentation with Adr?
Adr guides you through creating numbered decision records using a structured template. You document the architectural choice, the options you considered, the rationale behind your decision, and its consequences. This systematic approach ensures each decision is recorded with full context, making it easy to understand why choices were made and share that reasoning with team members.
What does Adr's decision record template capture?
Adr's template captures the essential elements of an architectural decision: the decision itself, the context and problem it addresses, the options you evaluated, your chosen solution and its rationale, and the consequences of that choice. This structured format ensures decisions are documented consistently and comprehensively across your project.
Can I track and review past architectural decisions with Adr?
Yes. Adr maintains a searchable log of your architecture decisions, allowing you to browse your decision history and review past choices. This tracking capability helps you understand the evolution of your architecture, find relevant precedents, and ensure your team stays aligned on architectural direction over time.
How does Adr help my team share decision context?
Adr creates a centralized repository of architecture decisions with full rationale and consequences documented. Team members can search and review past decisions to understand the architectural choices that shape your project, reducing the need to re-explain decisions and ensuring everyone has access to the same decision context.
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Create and manage architecture decision records for my project”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill captures architectural decisions made during coding sessions as structured ADR documents that live alongside your codebase. It detects decision moments, gathers context and alternatives, and maintains a searchable log so future developers understand the reasoning behind your architecture.
ADR Writer creates formatted architecture decision records that capture the problem, alternatives weighed, and chosen solution. It automatically numbers files, slugifies titles, and populates a standard template to ensure design decisions survive team turnover.
This skill guides you through authoring Architecture Decision Records (ADRs) that capture major technical choices with full context. It validates decisions against existing architectural stances, engine compatibility, and GDD requirements, then generates a structured record with status, dependencies, and consequences tracked. Use it to retrofit missing sections into existing ADRs or create new ones from scratch.
This skill walks you through the complete ADR lifecycle—from evaluating whether a decision is ready to record, through structured creation using the MADR template, to quality checks and ongoing log management. It grounds decisions in proven frameworks like START (readiness criteria) and ECADR (completion criteria), helping teams capture architectural rationale rather than just outcomes.
ADR Skill helps teams document architecture decisions as executable specifications for coding agents. It guides you through a four-phase workflow—scanning existing decisions, capturing intent through structured questions, drafting the record with implementation details, and validating against an agent-readiness checklist. Built for codebases where decisions must be explicit, measurable, and actionable.
This skill generates Architecture Decision Records (ADRs) that capture the context, decision, and consequences of significant technical choices. It guides you through gathering essential information, selecting from three formats (MADR, Nygard, or Y-Statement), and produces a structured document that preserves reasoning for future engineers.
More skills adr-writer (MIT) · Adr Architecture (unlicensed) · adr (MIT) · propagate-design-change (MIT) · create-control-manifest (MIT) · Artifacts Creating And Managing (unlicensed) · create-epics (MIT)