create-adr
Provides a guide for creating, naming, and indexing ADRs to document project design decisions.
Install
mkdir -p .claude/skills/create-adr && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10642" && unzip -o skill.zip -d .claude/skills/create-adr && rm skill.zipInstalls to .claude/skills/create-adr
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Guide for creating Architectural Decision Records (ADRs) in the torrust-tracker project. Covers the timestamp-based file naming convention, free-form structure, index registration in the docs/adrs/README.md index table, and commit workflow. Use when documenting architectural decisions, recording design choices, or adding decision records. Triggers on "create ADR", "add ADR", "new decision record", "architectural decision", "document decision", or "add decision".Key capabilities
- →Generate timestamp-based ADR filenames
- →Register ADRs in the project index
- →Validate ADRs using linters
- →Cross-link ADRs with affected code
How it works
Generates a timestamped filename, creates the ADR file, registers it in the index, and commits the changes.
Inputs & outputs
When to use create-adr
- →Documenting new design decisions
- →Creating an ADR file
- →Registering decisions in the index
- →Recording architectural choices
About this skill
Moved: create-adr
This skill moved to .claude/skills/create-adr/SKILL.md in issue #2866.
When not to use it
- →Trivial implementation choices
- →Style preferences covered by linting
Prerequisites
Limitations
- →No rigid template provided
- →Status headers only for terminal states
How it compares
Enforces a strict project-wide naming and indexing convention rather than allowing free-form documentation.
Compared to similar skills
create-adr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| create-adr (this skill) | 0 | 6mo | Review | Beginner |
| project-planner | 32 | 1y | Review | Intermediate |
| spec-kit-workflow | 11 | 11mo | No flags | Intermediate |
| specification-architect | 13 | 1y | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by torrust
View all by torrust →You might also like
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
specification-architect
adrianpuiu
A rigorous, traceability-first system that generates five interconnected architectural documents (blueprint.md, requirements.md, design.md, tasks.md, and validation.md) with complete requirements-to-implementation traceability. Use this skill when users need to architect systems, create technical specifications, or develop structured project documentation with guaranteed traceability.
architecture
davila7
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
context-driven-development
wshobson
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context