agentleFS
Sign inStart free
sarveshtalelesarveshtalele/devcrew/.claude/skills/adr/SKILL.md

adr

Skill1 starsChanged 3 months agoMITView on GitHub

Write an Architecture Decision Record in MADR format. Use for any new dependency, data store, protocol, boundary, auth model, or hard-to-reverse choice.

90 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use fdr, runbook and 9 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

  • montymiSkill

    tech-spec

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

    Also in 3 projects that use this

  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 75 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write an ADR for: $ARGUMENTS

    line 6
  2. Very specific:

    Use context7 MCP for current facts about any library or service involved.

    line 14
  3. Distinctive:

    Keep it under 2 pages. An unread ADR is worthless.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 75 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 an ADR for: $ARGUMENTS

  1. Next number: ls docs/adr | tail -1. File: docs/adr/ADR-<NNN>-<kebab-slug>.md from templates/ADR.md.
  2. State the quality attributes driving the decision (Project-Context.md §5). An architecture decision is a trade-off between NFRs; name them.
  3. List at least two real alternatives, each with cost, risk, reversibility, and operational burden. "Do nothing" is a valid alternative and often the right one.
  4. Recommend one, plainly, and say what would make you change your mind.
  5. Consequences must include the bad ones. An ADR listing only benefits is marketing, not a record.
  6. Note the compliance/data-classification impact if the decision moves PII/PHI/CHD across a boundary.
  7. Use context7 MCP for current facts about any library or service involved. Do not decide from memory.
  8. Status starts Proposed; security-engineer reviews before Accepted.
  9. Link it from Changelog.md and the relevant tracker card.

Keep it under 2 pages. An unread ADR is worthless.

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.

Check your setup, free