Adr Skill
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 Skill creates Architecture Decision Records optimized for agentic coding workflows with implementation plans and validation.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
ADR Skill creates Architecture Decision Records optimized for agentic coding workflows with implementation plans and validation. 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.
Use it when
- ADR Skill teaches ADR (Architecture Decision Record) format as a structured approach to documenting technical design choices.
- ADR Skill standardizes how teams capture and communicate design decisions through its structured four-phase workflow.
Install
joelhooks/joelclaw/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 with the ADR Skill?
ADR Skill guides you through a four-phase workflow to document architecture decisions as executable specifications. Start by scanning existing decisions, then capture intent through structured questions, draft the record with implementation details, and validate against an agent-readiness checklist. This process ensures your architecture decision records are explicit, measurable, and actionable for coding agents and team members.
What is ADR format and what are best practices?
ADR Skill teaches ADR (Architecture Decision Record) format as a structured approach to documenting technical design choices. Best practices include capturing decision context, stating the chosen option clearly, explaining the rationale, and listing consequences. ADR Skill emphasizes making decisions explicit and measurable so they become executable specifications that teams and coding agents can act on consistently.
How does ADR Skill help establish team consensus?
ADR Skill standardizes how teams capture and communicate design decisions through its structured four-phase workflow. By guiding teams through scanning existing decisions, asking clarifying questions, drafting records with implementation details, and validating readiness, ADR Skill creates a shared framework that helps establish consensus on architectural directions and maintains decision history for future reference.
Can ADR Skill create templates for architecture decisions?
Yes, ADR Skill provides templates and structure for creating architecture decision records. It helps you document system design decisions in a standardized format that captures intent, rationale, and consequences. ADR Skill's template-driven approach ensures consistent documentation across your codebase and makes decision records actionable for both human teams and coding agents.
How does ADR Skill track decision status and history?
ADR Skill maintains decision history and rationale through structured record-keeping in your architecture decision log. By documenting each technical choice with context, options considered, and consequences, ADR Skill creates a traceable decision record management system. This approach helps teams understand why decisions were made and supports future architectural planning and agent-driven implementation.
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 architecture decisions with ADR format”
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 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 Drafting helps teams document significant architectural decisions by creating new Architecture Decision Record files with a standard structure. It inspects your repository for existing ADR conventions, then drafts a new record with Title, Status, Context, Decision, and Consequences sections—defaulting to `docs/architecture/adr` when no convention exists.
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.
When a game design document is revised, architectural decisions built on it may become stale. This skill reads the changed GDD, compares it against all architecture decision records, and produces a detailed impact report classifying each ADR as still valid, needing review, or likely superseded. It then guides you through resolution decisions and updates your traceability index.
Documentation and ADRs helps teams record the reasoning behind significant technical decisions through structured Architecture Decision Records. Store decisions in `docs/decisions/` with context, alternatives considered, and consequences so future engineers and AI agents understand not just what was built, but why.
This skill guides you through writing Architecture Decision Records—concise documents that capture the shape of load-bearing choices, why you made them, and what trade-offs you considered. Use it when a decision is hard to reverse, surprising without context, or the result of genuine alternatives. ADRs live in docs/adr/ with sequential numbering and a simple template; most need just a paragraph.
More skills architecture-decision-records (MIT) · create-control-manifest (MIT) · adr-critique (MIT) · Create Adr (NOASSERTION)