mgiovani/ai-arsenal / skills/docs-adr
docs-adr
VerifiedCreate a numbered Architecture Decision Record (ADR) documenting a technical decision with context, alternatives, and consequences. Trigger on "create an ADR", "document this architectural decision", "record why we chose X", or "write an ADR for [decision]". Not for a decision still open for discussion (use docs-rfc, RFCs propose, ADRs record) and not for bootstrapping a project's whole docs/ tree from scratch (use docs-init).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| assets/templates/full.md | markdown | 2.5 KB |
| assets/templates/lightweight.md | markdown | 508 B |
| assets/templates/nygard.md | markdown | 339 B |
| evals/evals.json | config | 3.2 KB |
| evals/trigger-eval.json | config | 2.0 KB |
evals/trigger-eval.json
View on GitHub[
{"query": "can you create an ADR for switching our database to Postgres", "should_trigger": true},
{"query": "write an ADR documenting why we picked Kafka over RabbitMQ", "should_trigger": true},
{"query": "we finally decided to go with microservices, record why we chose that", "should_trigger": true},
{"query": "document this architectural decision about our new auth strategy", "should_trigger": true},
{"query": "/docs-adr \"Adopt Event-Driven Architecture\"", "should_trigger": true},
{"query": "need a numbered ADR for the caching layer decision we made yesterday", "should_trigger": true},
{"query": "write a lightweight ADR for using Redis for session storage", "should_trigger": true},
{"query": "can you write up an architecture decision record for the API gateway choice", "should_trigger": true},
{"query": "we've settled on GraphQL, please make an ADR capturing the decision and alternatives", "should_trigger": true},
{"query": "create adr full variant for the event driven architecture switch", "should_trigger": true},
{"query": "we're still debating between REST and GraphQL, can you write up an RFC to get feedback from the team", "should_trigger": false},
{"query": "generate a mermaid diagram of our current service architecture", "should_trigger": false},
{"query": "check if our docs are outdated compared to the codebase", "should_trigger": false},
{"query": "sync the README with the current state of the code", "should_trigger": false},
{"query": "set up the initial docs folder structure for this new project", "should_trigger": false},
{"query": "write a conventional commit message for these architecture changes", "should_trigger": false},
{"query": "implement the event-driven architecture we discussed", "should_trigger": false},
{"query": "open a PR for the database migration I just finished", "should_trigger": false},
{"query": "what are the pros and cons of choosing Kafka vs RabbitMQ", "should_trigger": false},
{"query": "refactor the session storage module to use Redis", "should_trigger": false}
]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |