Decision Log Skill
bjg4/decision-log-skill
Rastreie decisões com contexto, indexação automática e busca estruturada
Ver no GitHubSkill para rastreamento de decisões em Claude Code com YAML frontmatter estruturado, auto-indexação e busca queryável. Captura decisões de qualquer domínio (engenharia, pesquisa, saúde, criativo, financeiro) com contexto completo e suporta cadeias de supersessão para decisões revogadas.
Instalação
npx convez-ai bjg4/decision-log-skill1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Documentar decisões arquiteturais em projetos de engenharia
- Registrar escolhas em pesquisa científica e análise
- Manter auditoria de decisões financeiras e legais
- Rastrear evolução de decisões criativas e de design
Veredito

Skill sólido e bem documentado para times que precisam manter trilha auditável de decisões. A estrutura YAML + JSONL permite busca poderosa via grep/jq, embora exija disciplina para manter indexação consistente em projetos com alto volume de decisões.
README
A tradução para o português deste README ainda está na fila.
Decision Log
Decision tracking for Claude Code. Captures decisions from any domain with full context, queryable YAML frontmatter, and auto-generated indexing.
Works for engineering, research, health, creative, financial, personal, scientific, legal, or any other context where you want to track decisions over time.
Install
npx skills add bjg4/decision-log-skill
Or manually:
git clone https://github.com/bjg4/decision-log-skill.git ~/.claude/skills/decision-log
Update
npx skills add bjg4/decision-log-skill
If you installed via git clone:
cd ~/.claude/skills/decision-log && git pull
Usage
Invoke in any conversation:
/decision-log
The skill scans the current conversation, extracts decisions, and writes each one as a standalone markdown file in decisions/ with YAML frontmatter.
decisions/
_index.jsonl # Append-only manifest (one JSON record per decision)
DEC-0001.md # One file per decision (source of truth)
DEC-0002.md
Each decision captures: what was decided, options considered, rationale, expected outcome, method, and full conversation context.
Triggers
/decision-logor/DL- "log this decision", "capture this decision", "record decision"
- "what decisions have we made" (reads the index)
- "tell me more about DEC-0003" (reads a specific decision)
Example Output
Logged 2 decisions:
| ID | Domain | Decision | Status |
|----|--------|----------|--------|
| DEC-0001 | Architecture | Use PostgreSQL as the primary database | Active |
| DEC-0002 | Music Production | Analog tape recording for drum tracks | Active |
Updated: ./decisions/
Querying
Decision files use YAML frontmatter, so they're greppable:
# Find all architecture decisions
grep -rl "domain: Architecture" decisions/
# Find superseded decisions
grep -rl "status: Superseded" decisions/
# Find decisions by tag
grep -rl "postgresql" decisions/
The _index.jsonl manifest is one JSON record per decision, so you can query the whole log without opening individual files — handy with jq:
# All active architecture decisions, as a table
jq -r 'select(.status=="Active" and .domain=="Architecture") | [.id,.title] | @tsv' decisions/_index.jsonl
# Count decisions per domain
jq -r '.domain' decisions/_index.jsonl | sort | uniq -c
# Everything tagged "postgresql"
jq -r 'select(.tags | index("postgresql")) | .id' decisions/_index.jsonl
Skill Structure
SKILL.md # Main skill definition
references/
templates.md # Decision file and index schemas
tests/
prompts.json # Trigger and non-trigger test prompts
eval-prompts.json # Eval pipeline prompts with assertions
eval-summary.md # Latest evaluation results
eval-results/ # Raw eval outputs
License
MIT — Created by Blake Graham