From loopkit
Captures architectural decisions as ADR files so future sessions understand why a choice was made. Use after non-obvious technical choices like libraries, patterns, or schemas.
How this skill is triggered — by the user, by Claude, or both
Slash command
/loopkit:decision-recordWhen to use
picked a library/pattern/schema, a tradeoff was made, a hard-to-reverse choice
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write a short file `docs/decisions/NNN-<slug>.md`:
Write a short file docs/decisions/NNN-<slug>.md:
npx claudepluginhub archive228/loopkit --plugin loopkitDocuments architectural decisions using ADR format. Guides when and how to record significant technical decisions with context, rationale, and consequences.
Writes Architecture Decision Records (ADRs) documenting decisions, rationale, alternatives, and trade-offs from codebases or conversations. Triggers on 'write an ADR' or 'document decision'.
Architecture Decision Records — capture a hard-to-reverse choice while the reasons are fresh. Triggers on "why did we choose", "record this decision", "ADR", picking a database, framework, protocol, auth model, or API shape, or any fork where reversing the choice later would cost more than a day. One short file per decision, so the next person inherits the reasoning, not just the result.