SkillAgentSearch skills...

recording-architecture-decisions

Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.

Install / Use

npx skills add GanyuanRan/Aegis --skill recording-architecture-decisions

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of recording-architecture-decisions

recording-architecture-decisions scores 85/100 on our quality scale, 1959th of 2,780 Automation skills we index.

Its SKILL.md is 5.8 KB long, well organised into 9 sections with 1 code example: a solid amount of guidance for an agent.

With 1,273 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so recording-architecture-decisions is actively maintained.
  • Our last check on 2026-11-04 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

recording-architecture-decisions compared with similar skills

All 4 of these similar skills score higher than recording-architecture-decisions; compare them before choosing.

SkillScoreStarsUpdatedFormat
recording-architecture-decisions (this skill)by GanyuanRan851.3k53d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install recording-architecture-decisions?
Run npx skills add GanyuanRan/Aegis --skill recording-architecture-decisions. The install tabs above show the steps for each supported agent.
Which AI agents does recording-architecture-decisions work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is recording-architecture-decisions safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is recording-architecture-decisions still maintained?
The repository was last updated about 2 months ago, so recording-architecture-decisions is actively maintained.

name: recording-architecture-decisions description: "Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work."

Recording Architecture Decisions

Purpose

Record durable architecture decisions without losing the current-state baseline closure. An ADR records why a decision was made; a baseline records what the architecture is after that decision.

This skill is a lazy, task-specific workflow. It does not replace verification-before-completion, does not grant completion authority, and does not make authoritative GateDecision or PolicySnapshot outputs.

Required Read Set

Before deciding or writing, read the smallest relevant excerpts from:

  • docs/adr/ADR-CREATION-GATE.md
  • docs/current/AEGIS_ADR_AUTO_BACKFILL.md
  • the target project's current ADR, baseline, or authority docs that own the affected architecture surface

For Aegis repository changes, use this repository's docs/adr/ and docs/current/ authority order. For target projects with their own ADR system, respect that project owner instead of duplicating the same decision into docs/aegis/adr/.

When To Use

Use this skill when the user asks to:

  • create, write, update, amend, supersede, or evaluate an ADR
  • decide whether an architecture decision record is needed
  • record a durable architecture decision or decision log entry
  • close baseline sync after an ADR-relevant architecture change
  • verify that an ADR action did not leave the architecture baseline stale

Do not use it for simple wording edits, ordinary README cleanup, tests-only coverage improvements, low-risk single-file changes, or bug fixes that only restore the existing baseline.

Decision Flow

  1. Identify the decision candidate and evidence source.
  2. Run the ADR creation gate:
    • hard to reverse
    • surprising without context
    • real trade-off
  3. Apply the Retro / Memory Filter:
    • executed durable decisions may become ADR or baseline memory
    • unexecuted ideas stay out of accepted architecture memory
    • process notes may use a lighter record when they do not change current architecture state
  4. Choose exactly one ADR action: create, amend, supersede, or skip.
  5. Choose the owner surface: project docs/adr/, docs/aegis/adr/, existing ADR, or lighter record.
  6. Run Baseline Sync Closure.
  7. If writing files, preserve local ADR conventions and verify structure.

Helper-Backed Write Path

When the chosen owner surface is a target project's docs/aegis/adr/, use the shared workspace helper instead of ad-hoc file creation:

  • create -> <aegis-workspace-helper> new-adr --root <target-project-root> ...
  • amend -> <aegis-workspace-helper> amend-adr --root <target-project-root> --path docs/aegis/adr/ADR-####-<slug>.md ...
  • supersede -> <aegis-workspace-helper> supersede-adr --root <target-project-root> --path docs/aegis/adr/ADR-####-<slug>.md ...

After helper-backed writeback, run:

  • <aegis-workspace-helper> check --root <target-project-root>

The helper owns file shape, ADR numbering, supersession markers, and INDEX.md coverage only. It does not decide architecture truth, whether the ADR gate passed, or whether baseline sync is semantically sufficient.

If the ADR gate or owner-surface decision says skip, do not create or amend ADR files just because the helper exists. An ADR signal in a design/plan is a note for later completion, not an ADR file. Create/amend/supersede an ADR only for an executed durable decision; if an existing ADR already covers the decision surface, amend it instead of creating a sibling.

Baseline Sync Closure

If the ADR action is create, amend, or supersede, baseline sync must be checked.

Baseline sync is required when the decision changes or confirms any of:

  • canonical owner or ownership map
  • public API, schema, artifact shape, or behavior contract
  • dependency direction or allowed cross-module relationship
  • source-of-truth owner
  • host compatibility strategy or install/discovery contract
  • method-pack/runtime-core boundary
  • runtime-ready artifact boundary or evidence model
  • retained fallback, adapter, compatibility path, duplicate owner, or retirement schedule
  • accepted architecture-scoped Implementation Drift
  • release or distribution strategy that future contributors would otherwise misread

If no baseline writeback is made, state why the existing baseline remains valid. Never leave baseline sync implicit after create, amend, or supersede.

Compact Output Contract

Aegis Visibility:
- Why executed-decision filtering, ADR gate, owner surface, or baseline sync matters now:

Decision Candidate:
- Summary:
- Evidence source:

ADR Gate:
- Hard to reverse: yes | no | unknown
- Surprising without context: yes | no | unknown
- Real trade-off: yes | no | unknown

Retro / Memory Filter:
- Classification: executed durable decision | unexecuted idea | process note
- Memory action: record | skip | lighter record
- Reason:

ADR Action:
- create | amend | supersede | skip
- Reason:

Owner Surface:
- Target:
- Existing ADR / baseline checked:

Baseline Sync:
- Required: yes | no | unknown
- Target:
- Action: create snapshot | update baseline | cite unchanged | blocked
- Reason:

Boundary:
- Advisory method-pack signal only; not completion authority.

Common Mistakes

  • Writing an ADR because the topic feels important, even though the gate fails.
  • Recording why in an ADR while leaving the baseline's current-state facts stale.
  • Updating a baseline to match drift without first deciding whether the drift is intentional and ADR-worthy.
  • Duplicating the same decision into both project docs/adr/ and docs/aegis/adr/ without an explicit mirror relationship.
  • Treating an ADR or baseline sync as proof that the work is complete.

Related Skills

View on GitHub
GitHub Stars1.3k
CategoryAutomation
Updated1mo ago
Forks64

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
recording-architecture-decisions — Universal Skill: Install & Safety Check | SkillAgent