Adr
Record an architecture / cross-cutting decision as the next numbered ADR under docs/adr/. Use when a non-obvious or hard-to-reverse decision is made (a module boundary, a trade-off, a tech choice), or when the user says "record an ADR", "ADR 남겨", "이 결정 기록", "document this decision".From its SKILL.md
npx -y skills add jhlee0409/omni-harness-kit --skill adrAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 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.
SKILL.md
1.0 KB, as published. Nobody here has run it
adr
Capture WHY a non-obvious decision was made, so a future reader (or session) doesn't re-litigate it.
- Scaffold: run
bash "${CLAUDE_PLUGIN_ROOT}/skills/adr/new-adr.sh" "<title>"from the repo root. It computes the next number, writesdocs/adr/NNNN-<slug>.mdfrom the template, and prints the path. - Fill: Context (the forces) → Decision (active voice) → Consequences (what's easier / harder) → Alternatives (and why not). Keep it short — an ADR records the reasoning, not a manual.
- Record an ADR for decisions that are non-obvious, cross-cutting, or hard to reverse — not for routine changes.