agentleFS
Sign inStart free
davidondrejdavidondrej/cloudroom-core/skills/adr-verbatim/SKILL.md

adr-verbatim

Skill1.2k starsChanged 4 days agoApache-2.0View on GitHub

Record concise ADRs that preserve the user''s decisions without conversational noise. Use for "adr-verbatim", "new ADR", "document that as an ADR", "record this decision", or supplied ADR wording.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the project's established ADR location, including a previously specified repository.

    line 13
  2. Distinctive:

    Write a short, clear ADR. Remove filler, emotional reactions, repetition, rhetorical questions, and instructions to the agent.

    line 14
  3. Distinctive:

    Check every statement against the user's decision.

    line 15
  4. Distinctive:

    Prefer a short paragraph or list.

    line 32
  5. Distinctive:

    Do not add speculative rationale, alternatives, consequences, or implementation details.

    line 33
  6. Distinctive:

    Use exact wording only when the user explicitly asks for an exact quote or verbatim passage.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

ADR Verbatim

Preserve the user's meaning, not the conversation transcript. Record only the decision and context needed to understand it.

Steps

  1. Extract the decision the user stated or approved in the conversation. Ask only if the decision is unclear; do not require him to dictate polished wording.
  2. Use the project's established ADR location, including a previously specified repository. Do not assume the current checkout owns the ADRs. Name the file by that directory's rule (check its README or AGENTS.md); if it has none, take the next number.
  3. Write a short, clear ADR. Remove filler, emotional reactions, repetition, rhetorical questions, and instructions to the agent. Fix grammar and clarify references without changing the meaning, scope, conditions, or priorities.
  4. Check every statement against the user's decision. Remove invented requirements and unapproved agent suggestions.
  5. Show the saved path and full ADR in a code block.

Format

Match the directory's filenames, such as docs/adr/0042-short-slug.md or docs/adr/20261030-175900-short-slug.md. Use the file's ID in the heading.

# <ID> — short title

Status: accepted (<decision owner>, YYYY-MM-DD)

<The decision in plain English.>

Rules

  • Prefer a short paragraph or list. Add sections only when they improve clarity.
  • Do not add speculative rationale, alternatives, consequences, or implementation details.
  • Use exact wording only when the user explicitly asks for an exact quote or verbatim passage.
  • A changed decision needs a new ADR. Correct an existing ADR when the user explicitly requests it, without changing unrelated history.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 32 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the davidondrej/cloudroom-core repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about davidondrej/cloudroom-core

The biggest 5 of 32 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 32

Talked about on GitHub (32 times).

On GitHub · 32

27 more on GitHub
  • Other versions2 projects use a version of this.

    Word for word · 1

    1. davidondrej/cloudroom★ 1.2k100% same

    Edited · 1

    1. davidondrej/skills★ 4.2k84% same

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

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.

Check your setup, free