agentleFS
timursafiullintimursafiullin/aod/skills/adr/SKILL.md

adr

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Record an architecture decision as an ADR in .agents/decisions (context, decision, consequences, alternatives), accept it, or supersede an old one. Use whenever a significant decision is made - in chat, in review, or after a PO answer - so it survives the session.

94 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use fdr, runbook and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • thiagofgfSkill

    fdr

    Use when creating, changing, reviewing, retiring, auditing, or backfilling implemented user-visible feature behavior, permissions, feature-specific rationale, tradeoffs, or relationships to architectural decisions.

    Also in 3 projects that use this

  • AnthropicSkill

    runbook

    Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.

    Also in 5 projects that use this

  • drewdrewthisSkill

    sweep

    Search for similar patterns, anti-patterns, or issues elsewhere in the codebase after a fix or feature. Use after implementing a fix to catch the same bug in other places, or proactively to audit for a known pattern.

    Also in 4 projects that use this

  • vndeeSkill

    product-spec

    Use when starting a new feature, product, or project — before any architecture or code, to define what to build and why

    Also in 3 projects that use this

  • OpenAISkill

    threat-model

    Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

    Also in 6 projects that use this

  • montymiSkill

    tech-spec

    Parse and review Technical Specification documents for completeness, consistency, and implementation readiness

    Also in 3 projects that use this

The file

Files
SKILL.md

Architecture Decision Record

A decision counts only once it is in the repository. Write one when a contract, dependency, data format, domain model or process changes, or when the user settles a choice. CLI: aod means node "${CLAUDE_PLUGIN_ROOT}/scripts/aod.mjs".

  1. aod adr new "<the decision, as a sentence>" creates ADR-xxxx-<slug>.md (status Proposed) and an index row.
  2. Fill it in English, concise:
    • Context: the forces and constraints, with links to specs, issues and earlier ADRs.
    • Decision: what we will do, stated so it can be checked.
    • Consequences: what gets easier, what gets harder, follow-up work.
    • Alternatives considered: each with the reason it lost.
  3. Decide who accepts:
    • The architect accepts decisions that follow from the vision, invariants and existing ADRs.
    • The user (PO) accepts decisions with product, cost, licence or public consequences, and choices between equal options. Use /aod:decision to ask, and record their answer in the ADR.
  4. aod adr accept ADR-xxxx (refuses while Context/Decision/Consequences are empty). Accepted ADRs are protected by the contract guard.
  5. To change an accepted decision, write a new ADR and run aod adr supersede ADR-old --by ADR-new; never edit the old one's substance.
  6. Mention the ADR id in the journal's Decisions section and in any packet whose contracts it binds.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.