Adr Skill
Adr Skill guides you through a structured four-phase workflow to author Architecture Decision Records that serve as executable specifications for coding agents. It captures decision intent through targeted questioning, scans your codebase for related patterns and existing ADRs, then drafts records with implementation plans concrete enough for agents to act on without follow-up.
Adr Skill creates Architecture Decision Records designed for agents to implement without ambiguity or follow-up questions.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-28
Adr Skill creates Architecture Decision Records designed for agents to implement without ambiguity or follow-up questions. Adr Skill guides you through a structured four-phase workflow to author Architecture Decision Records that serve as executable specifications for coding agents. It captures decision intent through targeted questioning, scans your codebase for related patterns and existing ADRs, then drafts records with implementation plans concrete enough for agents to act on without follow-up.
Use it when
- Adr Skill helps you create Architecture Decision Records (ADRs)—executable specifications that capture the rationale, context.
- Yes.
Install
vercel/ai/adr-skill · repository language: TypeScript
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 write an ADR using Adr Skill?
Adr Skill guides you through a structured four-phase workflow to author Architecture Decision Records. The skill captures decision intent through targeted questioning, scans your codebase for related patterns and existing ADRs, then drafts records with implementation plans concrete enough for agents to act on without follow-up.
What is an architecture decision record and why document it?
Adr Skill helps you create Architecture Decision Records (ADRs)—executable specifications that capture the rationale, context, and implementation details of system design choices. ADRs serve as a persistent log of technical decisions, enabling teams to understand the reasoning behind architectural choices and communicate that rationale to stakeholders across the project lifecycle.
Can Adr Skill generate ADR templates for my team?
Yes. Adr Skill generates ADR templates and establishes standardized formats for recording architectural decisions. It helps your team adopt a consistent structure for decision records, ensuring that all ADRs follow the same format and capture the necessary context for future reference and implementation.
How does Adr Skill track architectural decisions?
Adr Skill organizes and tracks technical decisions over your project lifecycle by scanning your codebase for related patterns and existing ADRs. This allows you to maintain an architecture decision log that evolves with your system, making it easy to reference past decisions and understand how architectural choices have shaped your design.
What makes Adr Skill's documentation framework different?
Adr Skill combines targeted questioning with codebase analysis to draft records with implementation plans concrete enough for coding agents to act on without follow-up. This approach bridges the gap between architectural intent and executable specifications, ensuring your ADRs are both well-reasoned and actionable.
How does Adr Skill help share architecture rationale?
Adr Skill structures your Architecture Decision Records in a standardized, documented format that makes it easy to communicate architecture rationale with stakeholders. By capturing decision context, alternatives considered, and implementation details in a consistent framework, Adr Skill ensures all team members understand the reasoning behind system design choices.
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 document architecture decision records for system 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 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.
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.
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 to document decisions that matter—architectural choices, API shifts, and feature launches—by capturing the reasoning, constraints, and alternatives considered. It includes templates for Architecture Decision Records (ADRs) that preserve historical context, inline documentation patterns that explain intent rather than restating code, and structures for API and README documentation that help current and future engineers understand not just what was built, but why.
adr-writing creates and formats architectural decision records using the MADR structure, applying E.C.A.D.R. quality criteria to ensure completeness. It sequences numbering, explores related decisions and code context, fills template sections, and marks gaps for investigation where data is unavailable.
Guides you through seven-phase ADR drafting via focused dialogue, asking one question per turn and pressure-testing your reasoning before self-critique. Enforces specificity on components, deciders, and architectural characteristics, then routes to discovery if foundations are shallow.
More skills Create Adr (NOASSERTION) · write-adr (Apache-2.0)