Architecture Decision Records
Create and maintain architecture decision records (ADRs) using established conventions, templates, and a built-in validator. The skill guides you through prospective and retrospective record creation, enforces quality standards like one decision per record and credible alternatives, and helps manage decision lifecycles with status tracking and supersession links. Use it to build a durable, reviewable record of why architecturally significant choices were made.
Architecture Decision Records helps you document and track architectural decisions with structured templates, validation, and supersession tracking.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
Architecture Decision Records helps you document and track architectural decisions with structured templates, validation, and supersession tracking. Create and maintain architecture decision records (ADRs) using established conventions, templates, and a built-in validator. The skill guides you through prospective and retrospective record creation, enforces quality standards like one decision per record and credible alternatives, and helps manage decision lifecycles with status tracking and supersession links. Use it to build a durable, reviewable record of why architecturally significant choices were made.
Use it when
- Architecture Decision Records provides a built-in template that enforces quality standards for your decision documentation.
- Architecture Decision Records manages decision lifecycles with status tracking and supersession links.
Similar skills
Install
dirnbauer/webconsulting-skills/architecture-decision-records · 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
How do I record architectural decisions?
Architecture Decision Records helps you document and track architectural decisions made during software design. The skill guides you through creating structured records using established conventions and templates, capturing the decision, its context, rationale, and alternatives. Each ADR follows a standardized format to ensure consistency across your project and team.
What is an ADR template for software projects?
Architecture Decision Records provides a built-in template that enforces quality standards for your decision documentation. The template ensures one decision per record, includes credible alternatives, and captures the decision's status and rationale. This standardized approach enables team alignment on architectural direction and creates a searchable, reviewable history of why choices were made.
How can I track architecture decisions over time?
Architecture Decision Records manages decision lifecycles with status tracking and supersession links. The skill lets you record both prospective decisions (before implementation) and retrospective ones (after the fact), maintaining a durable record that shows how architectural choices evolved. This enables you to maintain a searchable history and understand the reasoning behind each decision.
What are ADR best practices?
Architecture Decision Records enforces best practices through its built-in validator and guidance. Key practices include documenting one decision per record, considering credible alternatives, capturing clear rationale, and tracking decision status over time. The skill helps establish a standardized format across your team, enabling better collaboration and ensuring architectural decisions are properly documented and justified.
How does Architecture Decision Records help teams?
Architecture Decision Records enables team alignment by creating a structured, standardized record of design choices and their rationale. Teams use it to build a shared understanding of architectural direction, maintain searchable documentation of why decisions were made, and enforce quality standards through validation. This creates a durable reference that supports both current projects and future onboarding.
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 › “Document and track architectural decisions made during software design”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
ADR Writer helps teams document architectural decisions in a structured, numbered format that captures context, alternatives considered, and consequences. It guides you through identifying decision-worthy choices, articulating constraints, evaluating options, and projecting impacts—ensuring future readers understand not just what was decided, but why.
adr-author guides you through structured architecture decision authoring in three phases: Frame captures scope and drivers, Decide evaluates options and rationale, and Govern writes the final ADR file with lineage tracking. Choose between compact Y-Statement or detailed MADR v4.0.0 output, and enter via interactive capture, planner handoff, or template adoption.
Create Adr Spike walks you through a five-phase process—Research, Analysis, Decision, Documentation, and Memory Storage—to evaluate technical alternatives and formalize architectural choices. It manages ADR lifecycle with proper numbering, integrates external research tools, and persists decisions to a memory graph for future reference.
This skill produces structured technical documentation across four types: architectural decision records for design choices, system overviews for onboarding, API references for integrations, and operational runbooks for procedures. It enforces anti-patterns like documentation drift and future fiction while matching detail to audience—from high-level concepts for new developers to procedural steps for operations teams.
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.
This skill guides you through creating Architecture Decision Records for Java projects via structured dialogue. It systematically gathers decision context, stakeholder input, and architectural trade-offs, then produces a MADR-formatted document capturing your choice and rationale.
More skills Create Adr (NOASSERTION) · architecture-decision-records (MIT) · adr-writer (MIT) · adr-drafting (MIT)