PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
Agent skill
Architectural Decision Records
by intent-driven-dev in intent-driven-dev/intent-driven-template
A skill your agent uses when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision…
Install Architectural Decision Records
$ npx skills add intent-driven-dev/intent-driven-template --skill architectural-decision-records -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install intent-driven-dev/intent-driven-template architectural-decision-records --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/architectural-decision-records .claude/skills/architectural-decision-records && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "architectural-decision-records" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/architectural-decision-records into .claude/skills/architectural-decision-records/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architectural-decision-records", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/architectural-decision-recordsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add intent-driven-dev/intent-driven-template --skill architectural-decision-records -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install intent-driven-dev/intent-driven-template architectural-decision-records --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/architectural-decision-records .agents/skills/architectural-decision-records && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "architectural-decision-records" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/architectural-decision-records into .agents/skills/architectural-decision-records/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architectural-decision-records", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/intent-driven-template --skill architectural-decision-records -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install intent-driven-dev/intent-driven-template architectural-decision-records --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/architectural-decision-records .cursor/skills/architectural-decision-records && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "architectural-decision-records" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/architectural-decision-records into .cursor/skills/architectural-decision-records/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architectural-decision-records", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/intent-driven-dev/intent-driven-template.git --path .agents/skills/architectural-decision-records--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add intent-driven-dev/intent-driven-template --skill architectural-decision-records -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install intent-driven-dev/intent-driven-template architectural-decision-records --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/architectural-decision-records .gemini/skills/architectural-decision-records && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "architectural-decision-records" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/architectural-decision-records into .gemini/skills/architectural-decision-records/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architectural-decision-records", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install intent-driven-dev/intent-driven-template architectural-decision-recordsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add intent-driven-dev/intent-driven-template --skill architectural-decision-records -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/architectural-decision-records .github/skills/architectural-decision-records && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "architectural-decision-records" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/architectural-decision-records into .github/skills/architectural-decision-records/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architectural-decision-records", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/intent-driven-template --skill architectural-decision-records -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install intent-driven-dev/intent-driven-template architectural-decision-records --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/architectural-decision-records .opencode/skills/architectural-decision-records && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "architectural-decision-records" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/architectural-decision-records into .opencode/skills/architectural-decision-records/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architectural-decision-records", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
architectural-decision-records- GitHub stars
- 159
- Token cost
- ~1k tokens
- SKILL.md length
- 392 words
- Files
- 7
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision…
- Works in 8 steps: Identify the single decision. Split… → Check preferences.md for preferred-style. → If preferred-style: unset, ask the user… → …
- Updating architectural decisions
- SKILL.md covers Overview, When to Use, Workflow and Template Choice, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Architectural Decision Records is an agent skill from intent-driven-dev/intent-driven-template. Use when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision history.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `preferences.md`, `templates/custom.md` and `templates/madr-full.md`).
It sits in Development, covering Architecture decision records. The repository describes itself as: OpenSpec and OpenCode template for intent-driven development with specs, ADRs, C4 diagrams, Gherkin, TDD, Multi-Model Adversarial Spec Authoring, Glossary for Domain Terms, and… The licence is MIT.
When your agent uses it
- Updating architectural decisions
- Architecture decision history
Example prompts
- “/architectural-decision-records”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Identify the single decision. Split multiple decisions into multiple ADRs.
- Check preferences.md for preferred-style.
- If preferred-style: unset, ask the user which style to use, then record it in preferences.md before drafting.
- Use the matching file under templates/.
- Capture known facts only: context, requirements, constraints, options, rationale, decision makers, consequences.
- If facts are missing, mark them as Unknown or ask a focused question; do not invent context, options, or quality attributes.
- Write honest consequences: benefits, downsides, follow-up.
- Preserve history: supersede old accepted ADRs; do not rewrite them away.
What it can do on your machine
Read from SKILL.md and the folder at commit 73f54d5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Architectural Decision Records loads about 1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 392 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from intent-driven-dev/intent-driven-template at commit 73f54d5, republished under its MIT licence (© intent-driven-dev). 392 words, ~1,020 tokens.
Download SKILL.mdSave it as
.claude/skills/architectural-decision-records/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- architectural-decision-records
- description
- Use when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision history.
Architectural Decision Records
Overview
An Architectural Decision Record captures one architecturally significant decision, its rationale, tradeoffs, and consequences. Optimize for future readers reconstructing decision history.
When to Use
Use when creating, updating, reviewing, or explaining an ADR, architecture decision, decision log, tradeoff analysis, rationale, consequences, alternatives, or status.
Do not use ADRs for transient implementation details, meeting notes, or insignificant decisions. If significance is unclear, ask what future maintainers will need to know.
Workflow
- Identify the single decision. Split multiple decisions into multiple ADRs.
- Check
preferences.mdforpreferred-style. - If
preferred-style: unset, ask the user which style to use, then record it inpreferences.mdbefore drafting. - Use the matching file under
templates/. - Capture known facts only: context, requirements, constraints, options, rationale, decision makers, consequences.
- If facts are missing, mark them as
Unknownor ask a focused question; do not invent context, options, or quality attributes. - Write honest consequences: benefits, downsides, follow-up.
- Preserve history: supersede old accepted ADRs; do not rewrite them away.
Template Choice
| Situation | Template |
|---|---|
| Detailed tradeoff record | templates/madr-full.md |
| Concise tradeoff record | templates/madr-minimal.md |
| Classic lightweight ADR | templates/nygard.md |
| One-sentence summary | templates/y-statement.md |
| Project-specific style | templates/custom.md |
| Too little evidence | ADR review notes/questions, not accepted ADR |
Status Values
| Status | Use when |
|---|---|
| Proposed | Under review |
| Accepted | Team committed |
| Deprecated | Historically relevant but no longer recommended |
| Superseded | Replaced by another ADR; link it |
Show full SKILL.md (167 more words)Show less
Preference Prompt
If no preference is recorded, ask:
Which ADR style should I use and remember for this project: MADR full, MADR minimal, Nygard, Y-Statement, or custom?
After the user answers, update preferences.md with the selected preferred-style. Do not ask again unless the user asks to change style.
Review Checklist
- One decision, not a bundle
- Significant: affects structure, quality attributes, constraints, or evolution
- Context explains why it existed
- Rejected options/tradeoffs are explicit
- Rationale is tied to requirements, not preference
- Downsides and follow-up work are recorded
- Status is clear
- Unknowns are marked, not invented
Example
# ADR-012: Use PostgreSQL for Orders
## Status
Accepted
## Context
Orders need relational constraints, consistency, and reporting joins. The team operates PostgreSQL well.
## Considered Options
- PostgreSQL: integrity, SQL reporting, familiar operations; migrations required.
- MongoDB: flexible schema; weaker fit for consistency and joins.
## Decision
We will use PostgreSQL because consistency, joins, and operational familiarity matter more than schema flexibility.
## Consequences
- Positive: Integrity and reporting align with needs.
- Negative: Schema changes need migrations.
- Follow-up: Define migration practice.Common Mistakes
| Mistake | Fix |
|---|---|
| Several decisions in one ADR | Split them. |
| Sales pitch | Include rejected options and negative consequences. |
| Invented context | Mark unknowns or ask. |
| Treating status as decoration | Use status to show lifecycle and link superseding ADRs. |
| Rewriting history | Keep old ADR; create/link superseding ADR. |
| Omitting alternatives under pressure | Include at least the rejected option and why it lost. |
Sources
adr.github.io: home, ADR templates, AD practices. See templates/ for captured template variants.
© intent-driven-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files in .agents/skills/architectural-decision-records of intent-driven-dev/intent-driven-template.
- SKILL.md
- preferences.md
- templates/custom.md
- templates/madr-full.md
- templates/madr-minimal.md
- templates/nygard.md
- templates/y-statement.md
Open the folder on GitHubat commit 73f54d5
Compare with similar skills
Architectural Decision Records next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Architectural Decision Records this skillintent-driven-dev/intent-driven-template | 159 | — | ~1k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 380 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Design Doc MermaidSpillwaveSolutions/design-doc-mermaid | 175 | 1 repos | ~5.6k | Automated safety check: Pass | None |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
Learning Opportunities
DrCatHicks/learning-opportunities
Facilitates deliberate skill development during AI-assisted coding.
More from intent-driven-dev/intent-driven-template
All 10 skills in this repoAcceptance Test Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an…
Adversarial Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when rules or instructions mention "adversarial-authoring", "adversarial authoring", "must use adversarial-authoring skill", "model council", "cross-model review", or…
Gherkin Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data…
Glossary
intent-driven-dev/intent-driven-template
A skill your agent uses when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts
Openspec Bulk Apply Change
intent-driven-dev/intent-driven-template
A skill your agent uses when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
Spec As Source
intent-driven-dev/intent-driven-template
A skill your agent uses when a user or project explicitly adopts OpenSpec spec-as-source, fenced Gherkin specifications as executable acceptance tests, or acceptance-test-first OpenSpec tasks.
Related
Categories
Questions about Architectural Decision Records
What does Architectural Decision Records do?
A skill your agent uses when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision…. Architectural Decision Records is an agent skill from intent-driven-dev/intent-driven-template. Use when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision history.
When should I use Architectural Decision Records?
Architectural Decision Records fits situations like: updating architectural decisions; architecture decision history.
How do I install Architectural Decision Records in Claude Code?
Run `npx skills add intent-driven-dev/intent-driven-template --skill architectural-decision-records -a claude-code`. Or copy the skill folder (.agents/skills/architectural-decision-records in intent-driven-dev/intent-driven-template) into .claude/skills/architectural-decision-records in your project. Claude Code loads it when a task matches its description.
How do I install Architectural Decision Records in Codex?
Run `npx skills add intent-driven-dev/intent-driven-template --skill architectural-decision-records -a codex`. Or copy the skill folder (.agents/skills/architectural-decision-records in intent-driven-dev/intent-driven-template) into .agents/skills/architectural-decision-records in your project. Codex loads it when a task matches its description.
Can I use Architectural Decision Records in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add intent-driven-dev/intent-driven-template --skill architectural-decision-records -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architectural-decision-records, .gemini/skills/architectural-decision-records, .github/skills/architectural-decision-records and .opencode/skills/architectural-decision-records in your project.
What does Architectural Decision Records need to run?
SKILL.md names no scripts, command-line tools or credentials: Architectural Decision Records is instructions for the agent only.
Does Architectural Decision Records access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Architectural Decision Records safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Architectural Decision Records use?
Architectural Decision Records is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Architectural Decision Records use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Architectural Decision Records?
Skills that share tags, products or a category with Architectural Decision Records: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Architectural Decision Records?
intent-driven-dev (a GitHub organization) maintains it in intent-driven-dev/intent-driven-template, which has 159 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 4, 2026.
Source: intent-driven-dev/intent-driven-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.