agentleFS
LeonardoEnnesLeonardoEnnes/ai-engineering-toolkit/.agents/skills/write-adr/SKILL.md

write-adr

Skill0 starsChanged 10 days agoApache-2.0View on GitHub

Guides the creation of formal Architectural Decision Records (ADRs) to document significant design, structural, or technological choices.

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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Ensure the ADR references related domain models, system constraints, or performance requirements.

    line 19

“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

Write ADR Skill

Intent

Enforce structured architectural decision-making by documenting the context, rationale, alternatives considered, and consequences of critical technical choices before implementation.

Obligations

  1. Standardized Structure:
    • Structure the ADR following the standard format: Status, Context, Decision, Consequences, and Alternatives Considered.
  2. Trade-off Analysis:
    • Explicitly document why a specific technology, design pattern, or architectural boundary was chosen over viable alternatives (pros and cons).
  3. Traceability:
    • Ensure the ADR references related domain models, system constraints, or performance requirements.

How to verify

  • The generated ADR file contains all required sections with clear, objective justifications.
  • Alternatives are explicitly evaluated rather than dismissed arbitrarily.

Antipatterns (Do NOT do)

  • Writing vague decisions without documenting the underlying context or problem being solved.
  • Omitting negative consequences or technical debt introduced by the decision.

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.