Architecture decision records
Skill kimtth/agent-skill-100-lines-or-less/skills/architecture-decision-records
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill architecture-decision-recordsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: record a significant technical decision, its context, and consequences as an ADR.
SKILL.md
1.0 KB, as published. Nobody here has run it
Goal: a durable, searchable record of why a decision was made.
Use for:
- capturing significant or hard-to-reverse decisions
- preserving context for future maintainers
- aligning a team on a chosen direction
Workflow:
- Trigger an ADR when a decision is significant or contested.
- State the context and the forces driving the decision.
- Record the decision in one clear statement.
- List the options considered and why they were rejected.
- Capture the consequences, trade-offs, and follow-ups.
- Store it in-repo, numbered and immutable once accepted.
ADR sections:
- title and status (proposed, accepted, superseded)
- context and problem
- decision
- alternatives considered
- consequences
Rules:
- one decision per record; keep it short
- record the why, not just the what
- do not edit accepted ADRs; supersede with a new one
- link related and superseding ADRs