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…
Creates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members.
$ npx skills add tech-leads-club/agent-skills --skill create-adr -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tech-leads-club/agent-skills create-adr --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/tech-leads-club/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-adr' .claude/skills/create-adr && 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 "create-adr" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-adr into .claude/skills/create-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-adr", 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/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-adrType 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 tech-leads-club/agent-skills --skill create-adr -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tech-leads-club/agent-skills create-adr --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-adr' .agents/skills/create-adr && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-adr" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-adr into .agents/skills/create-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-adr", 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 tech-leads-club/agent-skills --skill create-adr -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tech-leads-club/agent-skills create-adr --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-adr' .cursor/skills/create-adr && 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 "create-adr" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-adr into .cursor/skills/create-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-adr", 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/tech-leads-club/agent-skills.git --path 'packages/skills-catalog/skills/(creation)/create-adr'--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 tech-leads-club/agent-skills --skill create-adr -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tech-leads-club/agent-skills create-adr --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-adr' .gemini/skills/create-adr && 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 "create-adr" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-adr into .gemini/skills/create-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-adr", 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 tech-leads-club/agent-skills create-adrInstalls 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 tech-leads-club/agent-skills --skill create-adr -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-adr' .github/skills/create-adr && 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 "create-adr" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-adr into .github/skills/create-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-adr", 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 tech-leads-club/agent-skills --skill create-adr -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tech-leads-club/agent-skills create-adr --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-adr' .opencode/skills/create-adr && 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 "create-adr" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-adr into .opencode/skills/create-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-adr", 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.
create-adrCreates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members.
Create Adr is an agent skill from tech-leads-club/agent-skills. Creates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members. Use when the user says "write an ADR", "document this decision", "record why we chose X", "add an architecture decision record", "create an ADR for", or wants to capture the reasoning behind a technical choice so the team understands it later. Do NOT use when the decision hasn't been made yet (use create-rfc instead), for implementation planning (use…
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Development, covering Architecture decision records. The repository describes itself as: The secure, validated skill registry for professional AI coding agents. Extend Antigravity, Claude Code, Cursor, Copilot and more with absolute confidence. The licence is CC-BY-4.0.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6df68d5. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
makeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Create Adr loads about 3.5k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 1,043 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.
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.
The full file from tech-leads-club/agent-skills at commit 6df68d5, republished under its CC-BY-4.0 licence (© tech-leads-club). 1,043 words, ~3,460 tokens.
.claude/skills/create-adr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.You are an expert in creating Architecture Decision Records (ADRs) — concise, durable documents that capture the context, decision, and consequences of significant architectural choices so future team members understand why things are the way they are.
Use this skill when:
Do NOT use for:
create-rfc to drive the decision process firsttechnical-design-doc-creator| Aspect | ADR | RFC |
|---|---|---|
| Timing | Decision already made (or being finalized) | Before the decision (seeking input) |
| Purpose | Record for future team members | Proposal seeking approval |
| Audience | Engineers joining months or years later | Current stakeholders |
| Length | Short — 200–500 words | Long — thorough comparison |
| Mutability | Immutable — superseded, never edited | Iterative — evolves during review |
| Tone | Historical record | Deliberative proposal |
If the user says "I need to decide whether to do X" → use create-rfc.
If the user says "We decided to do X, let me document it" → use this skill.
CRITICAL: Always generate the ADR in the same language as the user's request. Detect the language automatically.
Three formats are widely used. Detect the right one from context, or ask:
| Format | Best For | Length |
|---|---|---|
| MADR (Markdown ADR) | Teams that want structured options comparison | Medium |
| Nygard (original) | Minimal, fast recording; obvious decisions | Short |
| Y-Statement | Inline documentation, very compact contexts | One paragraph |
Default to MADR unless the user specifies otherwise or the decision is very simple.
If the user provides minimal context, use AskQuestion to collect essential information:
{
"title": "ADR Information",
"questions": [
{
"id": "adr_decision",
"prompt": "What was the decision made? (e.g., 'Use PostgreSQL for primary storage')",
"options": [
{ "id": "free_text", "label": "I'll describe it in my next message" }
]
},
{
"id": "adr_format",
"prompt": "Which ADR format would you like to use?",
"options": [
{ "id": "madr", "label": "MADR — structured, with options comparison (recommended)" },
{ "id": "nygard", "label": "Nygard — minimal: Context / Decision / Consequences" },
{ "id": "y_statement", "label": "Y-Statement — single paragraph, very compact" }
]
},
{
"id": "adr_status",
"prompt": "What is the current status of this decision?",
"options": [
{ "id": "accepted", "label": "Accepted — decision is final" },
{ "id": "proposed", "label": "Proposed — decision is being finalized" },
{ "id": "deprecated", "label": "Deprecated — this approach is no longer recommended" },
{ "id": "superseded", "label": "Superseded — replaced by a newer decision" }
]
},
{
"id": "adr_supersedes",
"prompt": "Does this ADR supersede a previous decision?",
"options": [
{ "id": "yes", "label": "Yes — I'll provide the ADR number/title" },
{ "id": "no", "label": "No — this is a new decision" }
]
}
]
}MANDATORY fields — ask if missing:
RECOMMENDED fields:
If any mandatory fields are missing, ask IN THE USER'S LANGUAGE before generating the document.
Scan the existing ADR directory for the next sequential number:
docs/adr/, docs/decisions/, .adr/, or adr/)Generate the ADR following the format selected in Step 1.
After generating, ask where to save it:
ADR Created: "ADR-{NNN}: {Title}"
Suggested file path: docs/adr/{NNN}-{kebab-case-title}.md
Would you like me to:
1. Save it to docs/adr/ (recommended convention)
2. Save it to a different location
3. Just show the content (I'll place it manually)# ADR-{NNN}: {Title}
- **Date**: YYYY-MM-DD
- **Status**: Accepted | Proposed | Deprecated | Superseded by [ADR-NNN]({link})
- **Deciders**: {who was involved in the decision}
- **Tags**: {optional: architecture, security, performance, database, etc.}
## Context and Problem Statement
{Describe the context and the problem or question that led to this decision.
2–4 sentences. What situation forced this choice?}
## Decision Drivers
- {Driver 1 — e.g., "Must support 10k concurrent users"}
- {Driver 2 — e.g., "Team has no Go experience"}
- {Driver 3 — e.g., "Must be deployable on-premise"}
## Considered Options
- {Option A}
- {Option B}
- {Option C — "Do nothing / status quo" when relevant}
## Decision Outcome
Chosen option: **"{Option A}"**, because {concise rationale tied to decision drivers}.
### Positive Consequences
- {Benefit 1}
- {Benefit 2}
### Negative Consequences
- {Trade-off 1 — be honest}
- {Trade-off 2}
## Pros and Cons of the Options
### {Option A} ✅ Chosen
- ✅ {Pro 1}
- ✅ {Pro 2}
- ❌ {Con 1}
### {Option B}
- ✅ {Pro 1}
- ❌ {Con 1}
- ❌ {Con 2}
### {Option C}
- ✅ {Pro 1}
- ❌ {Con 1}
## Links
- {Related ADR, RFC, ticket, or documentation}
- Supersedes: [ADR-{NNN}: {Title}]({link}) (if applicable)
- Superseded by: [ADR-{NNN}: {Title}]({link}) (if applicable)# ADR-{NNN}: {Title}
## Status
Accepted | Proposed | Deprecated | Superseded by ADR-{NNN}
## Context
{What is the situation that led to this decision?
What forces are at play — technical, business, organizational?
What constraints exist? 2–5 sentences.}
## Decision
{What did we decide to do?
State it directly, in active voice: "We will use X" or "We decided to adopt Y."
Include a brief rationale — why this option over the alternatives.}
## Consequences
{What becomes easier or better as a result?}
{What becomes harder or worse? Be honest about trade-offs.}
{What new concerns or constraints does this introduce?}# ADR-{NNN}: {Title}
**Date**: YYYY-MM-DD | **Status**: Accepted
In the context of **{situation/use case}**,
facing **{concern or constraint}**,
we decided **{the option chosen}**,
to achieve **{quality attribute or goal}**,
accepting **{the downside or trade-off}**.
**Deciders**: {names or roles}
**Links**: {related ADRs, tickets}Before finalizing, verify:
NNN-kebab-case-title.mddocs/adr/
├── 001-use-postgresql-for-primary-storage.md
├── 002-adopt-event-driven-architecture.md
├── 003-replace-jenkins-with-github-actions.md ← supersedes ADR-001 if relevant
└── README.md ← optional index001, 002, ... 099, 100.md extensiondocs/adr/, docs/decisions/, adr/, .adr/BAD: # ADR-001: Should we use PostgreSQL?
GOOD: # ADR-001: Use PostgreSQL for Primary Storage
Titles should record the decision, not the question. Future readers need to know what was decided, not what was considered.
BAD:
We needed a database and chose PostgreSQL.GOOD:
Our application requires a relational database with strong ACID guarantees.
The team has deep PostgreSQL experience. MySQL was evaluated but lacks
native support for JSONB columns, which our schema design requires.
Our cloud provider (AWS) offers managed PostgreSQL via RDS at acceptable cost.Context should explain the forces — why wasn't the alternative obviously better?
BAD:
## Consequences
PostgreSQL is fast and reliable.GOOD:
## Consequences
- Enables JSONB columns and advanced indexing for our query patterns
- Team expertise means fast onboarding and fewer operational surprises
- Adds operational burden compared to a managed NoSQL service
- Schema migrations require careful planning in a relational modelHonest trade-offs are what make ADRs valuable years later.
BAD: Editing an old ADR to change the decision after the fact.
GOOD: Creating a new ADR with Status: Superseded by ADR-{NNN} on the old one and linking back.
ADRs are historical records. The old decision was correct given what was known at the time. Superseding preserves that context.
BAD:
## Decision
We will use Redis for session storage.GOOD:
## Decision
We will use Redis for session storage. We considered storing sessions in PostgreSQL
(already in our stack) but Redis's built-in TTL support and in-memory performance
make it significantly better suited for high-frequency session reads. The operational
cost of an additional service is justified by the simplified session expiry logic.The rationale is why this option and not the others — not just what was chosen.
© tech-leads-club, CC-BY-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in packages/skills-catalog/skills/(creation)/create-adr of tech-leads-club/agent-skills.
Open the folder on GitHubat commit 6df68d5
Create Adr 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 |
|---|---|---|---|---|---|---|
| Create Adr this skilltech-leads-club/agent-skills | 7k | — | ~3.5k | Automated safety check: Pass | CC-BY-4.0 | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 381 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Architecture DecisionDonchitos/Claude-Code-Game-Studios | 26k | — | ~1.7k | 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 |
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…
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Donchitos/Claude-Code-Game-Studios
Create an ADR documenting a technical decision: context, alternatives considered, consequences.
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
tech-leads-club/agent-skills
Generates Excalidraw diagram files from plain descriptions, choosing among flowcharts, mind maps, architecture, swimlane, class, sequence and ER diagrams.
tech-leads-club/agent-skills
Creates, validates and renders Mermaid diagrams to SVG, PNG or ASCII, including C4 and AWS architecture-beta, flowcharts, sequence diagrams and ERDs.
tech-leads-club/agent-skills
Answers AWS architecture, security and service-selection questions by searching AWS documentation through MCP tools first, then adapting advice to your stack and team.
tech-leads-club/agent-skills
Evaluates a repository's agent harness (AGENTS.md, rules, skills) for broken paths, redundant instructions and usefulness, and stops at reports.
tech-leads-club/agent-skills
Designs scalable NestJS modular monoliths with domain-driven design, Clean Architecture layers and optional CQRS, defining bounded contexts and strict module boundaries.
Categories
Creates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members. Create Adr is an agent skill from tech-leads-club/agent-skills. Creates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members.
Create Adr fits situations like: the user says write an ADR; document this decision; record why we chose X; add an architecture decision record.
Run `npx skills add tech-leads-club/agent-skills --skill create-adr -a claude-code`. Or copy the skill folder (packages/skills-catalog/skills/(creation)/create-adr in tech-leads-club/agent-skills) into .claude/skills/create-adr in your project. Claude Code loads it when a task matches its description.
Run `npx skills add tech-leads-club/agent-skills --skill create-adr -a codex`. Or copy the skill folder (packages/skills-catalog/skills/(creation)/create-adr in tech-leads-club/agent-skills) into .agents/skills/create-adr in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tech-leads-club/agent-skills --skill create-adr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-adr, .gemini/skills/create-adr, .github/skills/create-adr and .opencode/skills/create-adr in your project.
Going by SKILL.md and its folder, Create Adr needs the command-line tools its instructions call (make).
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.
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.
Create Adr is published under the CC-BY-4.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Create Adr: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars) and Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
tech-leads-club (a GitHub organization) maintains it in tech-leads-club/agent-skills, which has 7,045 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 9, 2026.
Source: tech-leads-club/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.