agentleFS
RemiMyrsetRemiMyrset/roots/.agents/skills/new-adr/SKILL.md

new-adr

Skill0 starsChanged 44 days agoMITView on GitHub

Create a new decision record (MADR 4 minimal) named by today's date, in the correct format. Use when the user says "new ADR", "record this decision", "write a decision record", or a load-bearing choice was just made. Also use unprompted immediately after making a load-bearing choice yourself, such as adding or swapping a dependency, changing a convention or format, or reversing an earlier decision.

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create a decision record under docs/internal/decisions/.

    line 8
  2. Very specific:

    If this is the roots template itself, write no record.

    line 10
  3. Very specific:

    If it replaces or amends an earlier record: add a - Supersedes: ID bullet here, and edit only the old record's Status line to superseded by …

    line 29
  4. Very specific:

    Run pnpm docs:gen (it rewrites any page that keeps a generated list), then pnpm docs:check.

    line 37
  5. Distinctive:

    If merging the default branch reports an add/add conflict on this file, another branch wrote a record with the same name on the same day.

    line 45
  6. Distinctive:

    If the request names the decision topic, use it.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

New decision record

Create a decision record under docs/internal/decisions/.

  1. If this is the roots template itself, write no record. Use the fork and template checks in step 0 of the first-run skill; a contribution fork of roots counts as the template. Every child starts with a copy of docs/internal/decisions/, so it stays clean here (see "What roots chose" in docs/template/conventions.md). Add the choice and its why as a bullet under that heading, and its cost under "Consequences", then stop.
  2. Name it YYYYMMDD-kebab-title.md: today's date with no hyphens (date +%Y%m%d prints it; in PowerShell, Get-Date -Format yyyyMMdd), then a short declarative kebab title, for example 20260929-use-postgres.md. The date needs no counter, so records written on parallel branches never collide. Never create a numbered NNNN- name, even when the folder holds numbered records: those are legacy, stay as they are, and collide across branches.
  3. Copy docs/internal/decisions/_template.md to that name.
  4. Fill it in: the H1 is # Title, with no number or date; set - **Status:** (a decision being adopted now is accepted) and - **Date:** (today, YYYY-MM-DD). Write Context and Problem Statement, Considered Options, Decision Outcome ("Chosen option: X, because Y"), and Consequences (good and bad).
  5. If it replaces or amends an earlier record: add a - **Supersedes:** [ID](./file.md) bullet here, and edit only the old record's Status line to superseded by [ID](./file.md), linking this one. An amendment supersedes too: restate what still holds of the old record, so this one reads alone. The ID is the filename without .md for a dated record (20260929-use-postgres) and the number for a numbered one (0007). Never touch an old accepted record's body.
  6. Run pnpm docs:gen (it rewrites any page that keeps a generated list), then pnpm docs:check; both must pass.

The filename date is the day the record was created and never changes, even when the Date bullet later moves to the day it was accepted. A record written today about an older decision is still named for today; its Date bullet carries the older day.

If merging the default branch reports an add/add conflict on this file, another branch wrote a record with the same name on the same day. When it is the same decision written twice, merge the two into one record; when the decisions differ, rename the one not yet on the default branch to a more specific title and keep its date.

If the request names the decision topic, use it.

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.