Agile V Adr logo

Agile V Adr

Organization
Agile-V
agile-v-adr

Authoring, approval, immutability, and supersession of Architecture Decision Records (ADRs) in the Agile V lifecycle. Load when recording a significant, long-lived architectural, platform, tooling, or security decision.

Overview

PublisherAgile-V
Repositoryagile_v_skills
Skill nameagile-v-adr
Stars
54
Forks
11
Bundled files
Instructions only
LicenseCC-BY-SA-4.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Agile-V on GitHub. Read the source before you install it.

Installation

Install the Agile V Adr AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Agile-V/agile_v_skills/tree/main/agile-v-adr
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Agile-V/agile_v_skills.git /tmp/agile_v_skills
mkdir -p .claude/skills
cp -r /tmp/agile_v_skills/agile-v-adr .claude/skills/agile-v-adr
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agile V Adr in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agile V Adr on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agile V Adr is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Instructions

An Architecture Decision Record (ADR) captures a significant, long-lived technical decision. It is a distinct artifact from the append-only DECISION_LOG.md: an ADR has a fixed field set, is immutable once written, and is changed only by supersession. Agile V reserves the ADR-XXXX ID; this skill backs it with an artifact and procedure.

Requires agile-v-core loaded first. An ADR does not replace a REQ, risk control, specification, or change record.

When to write an ADR

Use an ADRUse DECISION_LOG.md
Architecturally significant, long-lived choice (platform, framework, tool, architecture pattern, infrastructure, data, security posture)Routine, reversible, day-to-day implementation decisions
A choice future maintainers must not silently reverseSession/context notes and rationale
A decision affecting regulated functionality, data integrity, interfaces, validation, or lifecycle risk—

If in doubt, an ADR is the more durable, auditable choice.

ADR fields (append-only, immutable once written)

FieldValue / allowed values
IDADR-XXXX — unique, never reused
TypePlatform | Framework | Tool | Architecture | Infrastructure | Data | Security
DateDate of decision
Statusproposed | approved | active | deprecated | superseded
SupersedesReference to the ADR this one replaces (if any)
Review DateScheduled re-evaluation date
ContextForces / problem driving the decision
Options ConsideredAlternatives evaluated
DecisionThe choice made
RationaleWhy this option over the others
ConsequencesTrade-offs, follow-on constraints

Procedure

  1. Propose — create the ADR with Status: proposed; Context, Options Considered, Decision, Rationale, Consequences are mandatory.
  2. Approve — the responsible human approver reviews (Human Gate etiquette, agile-v-core Directive 5). On approval, proposed → approved → active. Record approval evidence if the ADR gates a baseline or release.
  3. Link — relate affected requirements, risks, specifications, and change records via typed relationships (agile-v-core Directive 2).

Immutability & supersession

  • An active ADR is never edited in place.
  • To reverse or amend, write a new ADR with Supersedes: ADR-YYYY, and set the old one to Status: superseded (the only permitted status edit on a written ADR).
  • On Review Date, re-evaluate: keep active, or supersede.

Storage & traceability

  • One ADR per record under .agile-v/adr/ (or a dedicated ADR_LOG.md), separate from the append-only DECISION_LOG.md.
  • The DECISION_LOG.md may note an ADR promotion with a pointer to ADR-XXXX, but the ADR is the governed artifact.
  • When an external ALM/requirements tool is bound via an extension, ADRs map to a dedicated item type in that tool — not folded into a decision-log item.

Halt conditions

  • ADR proposed without Context, Options, Decision, Rationale, or Consequences.
  • In-place edit of an approved/active ADR (use supersession instead).
  • Reuse of a retired ADR-XXXX ID.

Frequently asked questions

What does the Agile V Adr AI skill do?

Authoring, approval, immutability, and supersession of Architecture Decision Records (ADRs) in the Agile V lifecycle. Load when recording a significant, long-lived architectural, platform, tooling, or security decision.

Why use Agile V Adr on TypingMind?

Because you install it once and use it with any model. Agile V Adr is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agile V Adr in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Agile-V/agile_v_skills/tree/main/agile-v-adr. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Agile V Adr?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agile V Adr?

As many as you like. As long as a model supports skills, you can use Agile V Adr with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agile V Adr AI skill free?

Yes. It is published on GitHub by Agile-V under the CC-BY-SA-4.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇