Skill

decision-log

Record and look up decisions in notes/DECISIONS.md with dcn-xxxx reference codes. Use for logging architectural choices, design decisions, and team agreements, or finding past decisions. Triggers on: "log a decision", "we decided", "record this decision", "decision log", "what did we decide about", "find decision".

Install

npx claudepluginhub a3lem/my-claude-plugins --plugin project-notes

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Record decisions concisely in `notes/DECISIONS.md`.

SKILL.md

Similar Skills

design-system

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

163.7k

ui-demo

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

163.7k

kotlin-patterns

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

163.7k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 8, 2026

Actions

View Source View Plugin View on GitHub View README

decision-log

Decision Log

Record decisions concisely in notes/DECISIONS.md.

Format

Decisions are grouped by ## <date> sections (YYYY-MM-DD, as returned by date '+%Y-%m-%d').

Each entry is a single top-level bullet: - dcn-<4-char-hex>: <description>

The description must be 120 characters or fewer (markup for status changes doesn't count).

Generate the hash: head -c 2 /dev/urandom | xxd -p

No nested list items. One bullet per decision.

Optional Annotations

#tags or #key=value tags, e.g. #infra, #bead=kap-fg3

[[wikilinks]] to related notes

[markdown](links) to journal entries or other docs

Status Changes

Decisions are active by default. This log is not append-only -- entries are edited in place for status changes:

Reverse: ~~strikethrough~~ the entry and append [reversed by dcn-xxxx]

Supersede: ~~strikethrough~~ the entry and append [superseded by dcn-xxxx]

The replacing decision should note what it replaces, e.g. (replaces dcn-xxxx)

Example

## 2026-02-16 - ~~dcn-6c80: Use Redis for caching #infra~~ [superseded by dcn-a3f1] - dcn-a3f1: Use Memorystore instead of self-hosted Redis #infra (replaces dcn-6c80) - dcn-hk45: Isolate tenants on every data query

Creating a New Entry

Open (or create) notes/DECISIONS.md

Find or create the ## <today's date> section

Generate a hash: head -c 2 /dev/urandom | xxd -p

Add the entry: - dcn-<hash>: <description 120 chars max>

If the file doesn't exist yet, create it with a # Decisions Log heading and the format comment block (see File Template section).

File Template

When creating notes/DECISIONS.md for the first time:

# Decisions Log

Decision Log

Record decisions concisely in notes/DECISIONS.md.

Format

Decisions are grouped by ## <date> sections (YYYY-MM-DD, as returned by date '+%Y-%m-%d').
Each entry is a single top-level bullet: - dcn-<4-char-hex>: <description>
The description must be 120 characters or fewer (markup for status changes doesn't count).
Generate the hash: head -c 2 /dev/urandom | xxd -p
No nested list items. One bullet per decision.

Optional Annotations

#tags or #key=value tags, e.g. #infra, #bead=kap-fg3
[[wikilinks]] to related notes
[markdown](links) to journal entries or other docs

Status Changes

Decisions are active by default. This log is not append-only -- entries are edited in place for status changes:

Reverse: ~~strikethrough~~ the entry and append [reversed by dcn-xxxx]
Supersede: ~~strikethrough~~ the entry and append [superseded by dcn-xxxx]
The replacing decision should note what it replaces, e.g. (replaces dcn-xxxx)

Example

## 2026-02-16

- ~~dcn-6c80: Use Redis for caching #infra~~ [superseded by dcn-a3f1]
- dcn-a3f1: Use Memorystore instead of self-hosted Redis #infra (replaces dcn-6c80)
- dcn-hk45: Isolate tenants on every data query

Creating a New Entry

Open (or create) notes/DECISIONS.md
Find or create the ## <today's date> section
Generate a hash: head -c 2 /dev/urandom | xxd -p
Add the entry: - dcn-<hash>: <description 120 chars max>

If the file doesn't exist yet, create it with a # Decisions Log heading and the format comment block (see File Template section).

File Template

When creating notes/DECISIONS.md for the first time:

<!--
## About this file

Concise log of all decisions. See the decision-log skill for format details.

- Entries grouped by ## <date> (YYYY-MM-DD)
- Format: `- dcn-<4-char-hex>: <description 120 chars max>`
- Hash: `head -c 2 /dev/urandom | xxd -p`
- Optional: #tags, [[wikilinks]], [markdown](links)
- Status: ~~strikethrough~~ + [reversed by dcn-xxxx] or [superseded by dcn-xxxx]
-->

# Decisions Log