adr-creation
Generate Architecture Decision Records following the project template and numbering convention. Use when documenting architecture decisions, technical choices, or when the user asks to create an ADR.
Best use case
adr-creation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate Architecture Decision Records following the project template and numbering convention. Use when documenting architecture decisions, technical choices, or when the user asks to create an ADR.
Teams using adr-creation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/adr-creation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How adr-creation Compares
| Feature / Agent | adr-creation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate Architecture Decision Records following the project template and numbering convention. Use when documenting architecture decisions, technical choices, or when the user asks to create an ADR.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ADR Creation Skill > **Purpose:** Generate Architecture Decision Records (ADRs) following the project template and numbering convention. ## Trigger **When:** User requests architecture documentation OR major technical decision made **Context Needed:** Decision context, options considered, final decision **MCP Tools:** `mcp_payment-syste_search_full_text`, `read_file` ## ADR Numbering Format: `NNN-SHORT-TITLE.md` ``` 001-AUTH-STRATEGY.md 002-OFFLINE-STRATEGY.md 003-[NEXT-DECISION].md ``` ## Required Sections ```markdown # ADR-NNN: [Title] ## Status [proposed | accepted | rejected | deprecated | superseded] ## Context [What is the issue that we're seeing that motivates this decision?] ## Decision [What is the change that we're proposing and/or doing?] ## Options Considered ### Option 1: [Name] **Pros:** ... **Cons:** ... ### Option 2: [Name] **Pros:** ... **Cons:** ... ## Rationale [Why was this option chosen?] ## Consequences [What becomes easier or more difficult?] ## Related ADRs [Links to related decisions] ``` ## Frontmatter Template ```yaml --- document_type: "adr" module: "architecture" status: "accepted" version: "1.0.0" last_updated: "YYYY-MM-DD" author: "@username" keywords: - "adr" - "[topic]" - "[technology]" related_docs: database_schema: "" api_design: "" adr_metadata: adr_number: NNN decision_date: "YYYY-MM-DD" stakeholders: ["@Architect", "@Backend"] --- ``` ## ADR Categories | Category | Keywords | Example | | :----------- | :----------------- | :------------------------ | | Architecture | pattern, structure | Monolith vs Microservices | | Technology | framework, library | Angular vs React | | Data | database, storage | PostgreSQL vs MongoDB | | Security | auth, encryption | JWT vs Sessions | | Integration | api, protocol | REST vs GraphQL | ## Workflow 1. **Get next number** - Check existing ADRs in `docs/technical/architecture/adr/` 2. **Load template** - Read 02-ADR-TEMPLATE.md 3. **Gather context** - Document the problem 4. **List options** - At least 2 alternatives 5. **Document decision** - Clear statement 6. **Explain rationale** - Why this choice? 7. **Create file** - `docs/technical/architecture/adr/NNN-TITLE.md` ## Reference - [02-ADR-TEMPLATE.md](/docs/templates/02-ADR-TEMPLATE.md) - [001-AUTH-STRATEGY.md](/docs/technical/architecture/adr/001-AUTH-STRATEGY.md) - [002-OFFLINE-STRATEGY.md](/docs/technical/architecture/adr/002-OFFLINE-STRATEGY.md)
Related Skills
data-model-creation
Professional rules for AI-driven data modeling and creation. Use this skill when users need to create and manage MySQL databases, design data models using Mermaid ER diagrams, and implement database schemas.
agent-creation
Standards-compliant agent definitions with templates. Trigger: When creating agent definitions, setting up project agents, or documenting workflows.
content-creation-flow
Step-by-step content creation workflow for documentation and training materials. Includes MCP validation, discovery, content design, Jira planning, and draft generation with priority-based execution. Use when starting the content creation flow, creating documentation or training materials, or when the user asks to follow the content creation workflow.
Automate YouTube Top-Ten Video Creation with OpenAI and Safe Image Search
Integrates OpenAI API for content generation, Bing Image Search API for safe image retrieval, and Pexels API for video footage. Handles authentication via Bearer token, enforces safe search, formats ChatGPT responses into a top-ten list, and includes error handling for API failures.
ai-podcast-creation
Create AI-powered podcasts with text-to-speech, music, and audio editing. Tools: Kokoro TTS, DIA TTS, Chatterbox, AI music generation, media merger. Capabilities: multi-voice conversations, background music, intro/outro, full episodes. Use for: podcast production, audiobooks, voice content, audio newsletters. Triggers: podcast, ai podcast, text to speech podcast, audio content, voice over, ai audiobook, multi voice, conversation ai, notebooklm alternative, audio generation, podcast automation, ai narrator, voice content, audio newsletter, podcast maker
claude-agent-sdk-agent-creation
Use when creating or configuring Claude AI agents using the Agent SDK. Covers agent initialization, configuration, and basic setup patterns.
architecture-agent-creation
Create specialized infrastructure agent definitions for platform/service management (Grafana, Prometheus, Traefik, ERPNext, etc.). Use when the user requests creation of an agent for a specific technology platform or infrastructure component. This skill produces complete agent prompts with integrated research, SOPs, tool references, and handoff protocols following the Linear-First Agentic Workflow framework.
agent-expert-creation
Create specialized agent experts with pre-loaded domain knowledge using the Act-Learn-Reuse pattern. Use when building domain-specific agents that maintain mental models via expertise files and self-improve prompts.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
obsidian-daily
Manage Obsidian Daily Notes via obsidian-cli. Create and open daily notes, append entries (journals, logs, tasks, links), read past notes by date, and search vault content. Handles relative dates like "yesterday", "last Friday", "3 days ago".
obsidian-additions
Create supplementary materials attached to existing notes: experiments, meetings, reports, logs, conspectuses, practice sessions, annotations, AI outputs, links collections. Two-step process: (1) create aggregator space, (2) create concrete addition in base/additions/. INVOKE when user wants to attach any supplementary material to an existing note. Triggers: "addition", "create addition", "experiment", "meeting notes", "report", "conspectus", "log", "practice", "annotations", "links", "link collection", "аддишн", "конспект", "встреча", "отчёт", "эксперимент", "практика", "аннотации", "ссылки", "добавь к заметке".
observe
Query and manage Observe using the Observe CLI. Use when the user wants to run OPAL queries, list datasets, manage objects, or interact with their Observe tenant from the command line.