agentleFS
Sign inStart free
jdanigojdanigo/hydraia/skills/adr/SKILL.md

adr

Skill8 starsChanged 2 months agoMITView on GitHub

Use when a design decision is made that is expensive to reverse, affects multiple components, or rejects a plausible alternative — record it as an Architecture Decision Record under docs/hydraia/adr/. Also use to supersede an old decision. Not for trivial choices.

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 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

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When NONE hold → no ADR. ADR spam buries the decisions that matter.

    line 16
  2. Distinctive:

    Write at decision time (Phase 2 / greenfield step 5), commit with the spec.

    line 42

“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

ADR — Architecture Decision Records (MADR-lite)

One file per decision: docs/hydraia/adr/NNNN-<slug>.md, zero-padded, monotonic (0001-..., 0002-...). Find the next number with ls docs/hydraia/adr/ | sort | tail -1.

When to write one (all it takes is ONE of these)

  • Expensive to reverse (data store, auth model, hosting, framework).
  • Affects multiple components or teams.
  • A plausible alternative was seriously considered and rejected.

When NONE hold → no ADR. ADR spam buries the decisions that matter.

Template

# NNNN — <decision title>

**Status:** proposed | accepted | superseded by NNNN
**Date:** YYYY-MM-DD

## Context
<the forces: requirements, constraints, and any assumption made because
the human could not answer — stated as an assumption with its revisit
trigger>

## Decision
<what was decided, in one or two sentences, active voice>

## Alternatives considered
- <alternative> — rejected because <reason>

## Consequences
- Good: <what this buys>
- Bad: <what this costs — every decision costs something; empty is a smell>

Lifecycle rules

  • Write at decision time (Phase 2 / greenfield step 5), commit with the spec.
  • Supersede, never rewrite: a change of mind = NEW ADR + flip the old one's Status to superseded by NNNN. History stays honest.
  • The Phase 2 spec references ADRs by number; reviewers check code against accepted ADRs.

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