Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Decision Logger

  • 574 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

decision-logger is a Claude Code skill that parses board-meeting decision logs and surfaces overdue owners, conflicts, and due-within reports for developers running lightweight governance over decisions.md files.

About

decision-logger is a governance reporting skill from alirezarezvani/claude-skills backed by a stdlib-only Python decision_tracker.py script. The parser reads memory/board-meetings/decisions.md and produces actionable reports via CLI flags: --summary, --overdue, --conflicts, --owner, --search, and --due-within. Use decision-logger when engineering or product leads maintain a decisions log and need automated overdue tracking, owner lookups, conflict detection, and due-within-7-day reports without external dependencies. A --demo flag runs against sample data for quick validation.

  • Python decision_tracker.py CLI with stdlib only—no extra dependencies
  • CLI modes: --summary, --overdue, --conflicts, --owner, --search, --due-within, --demo
  • Parses memory/board-meetings/decisions.md into owners, dues, reviews, and completion state
  • Overdue and due-within filters for operational standups
  • Conflict detection across decision records for advisor-style reviews

Decision Logger by the numbers

  • 574 all-time installs (skills.sh)
  • Ranked #690 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill decision-logger

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs574
repo stars23.5k
Security audit2 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you track overdue board decisions?

Parse board-meeting decision logs and surface overdue owners, conflicts, and due-within reports for a founder running lightweight governance.

Who is it for?

Engineering and product leads maintaining a decisions.md log who need CLI reports on overdue owners and conflicts.

Skip if: Teams without a structured decisions.md file or those needing full project management suite features.

When should I use this skill?

A decisions.md log needs parsing for overdue owners, conflicts, owner lookups, or due-within reports.

What you get

Summary, overdue, conflict, owner, search, and due-within reports from parsed decisions.md

  • Decision summary report
  • Overdue and conflict reports

By the numbers

  • Stdlib-only Python script with zero external dependencies
  • 6 report modes via CLI flags plus --demo

Files

SKILL.mdMarkdownGitHub ↗

Decision Logger

Two-layer memory system. Layer 1 stores everything. Layer 2 stores only what the founder approved. Future meetings read Layer 2 only — this prevents hallucinated consensus from past debates bleeding into new deliberations.

Keywords

decision log, memory, approved decisions, action items, board minutes, /cs:decisions, /cs:review, conflict detection, DO_NOT_RESURFACE

Quick Start

python scripts/decision_tracker.py --demo             # See sample output
python scripts/decision_tracker.py --summary          # Overview + overdue
python scripts/decision_tracker.py --overdue          # Past-deadline actions
python scripts/decision_tracker.py --conflicts        # Contradiction detection
python scripts/decision_tracker.py --owner "CTO"      # Filter by owner
python scripts/decision_tracker.py --search "pricing" # Search decisions

---

Commands

CommandEffect
/cs:decisionsLast 10 approved decisions
/cs:decisions --allFull history
/cs:decisions --owner CMOFilter by owner
/cs:decisions --topic pricingSearch by keyword
/cs:reviewAction items due within 7 days
/cs:review --overdueItems past deadline

---

Two-Layer Architecture

Storage follows the canonical two-layer decision memory (see ../agent-protocol/SKILL.md → "Decision Memory (Canonical Layout)") — the same layout /cs:decide writes.

Layer 1 — Raw Transcripts

Location: ~/.claude/decisions/raw/YYYY-MM-DD-<slug>.md

  • Full Phase 2 agent contributions, Phase 3 critique, Phase 4 synthesis
  • All debates, including rejected arguments
  • NEVER auto-loaded. Only on explicit founder request.
  • Archive after 90 days → ~/.claude/decisions/raw/archive/YYYY/

Layer 2 — Approved Decisions

Location: ~/.claude/decisions/approved/ — one record per decision (YYYY-MM-DD-<slug>.md) plus the append-only index decisions.md

  • ONLY founder-approved decisions, action items, user corrections
  • Loaded automatically in Phase 1 of every board meeting
  • Append-only. Decisions are never deleted — only superseded.
  • Managed by Chief of Staff after Phase 5. Never written by agents directly.

Migration: a legacy memory/board-meetings/ folder may exist from earlier versions; read it for history but write all new entries to ~/.claude/decisions/.

---

Decision Entry Format

## [YYYY-MM-DD] — [AGENDA ITEM TITLE]

**Decision:** [One clear statement of what was decided.]
**Owner:** [One person or role — accountable for execution.]
**Deadline:** [YYYY-MM-DD]
**Review:** [YYYY-MM-DD]
**Rationale:** [Why this over alternatives. 1-2 sentences.]

**User Override:** [If founder changed agent recommendation — what and why. Blank if not applicable.]

**Rejected:**
- [Proposal] — [reason] [DO_NOT_RESURFACE]

**Action Items:**
- [ ] [Action] — Owner: [name] — Due: [YYYY-MM-DD] — Review: [YYYY-MM-DD]

**Supersedes:** [DATE of previous decision on same topic, if any]
**Superseded by:** [Filled in retroactively if overridden later]
**Raw transcript:** ~/.claude/decisions/raw/[DATE]-<slug>.md

---

Conflict Detection

Before logging, Chief of Staff checks for: 1. DO_NOT_RESURFACE violations — new decision matches a rejected proposal 2. Topic contradictions — two active decisions on same topic with different conclusions 3. Owner conflicts — same action assigned to different people in different decisions

When a conflict is found:

⚠️ DECISION CONFLICT
New: [text]
Conflicts with: [DATE] — [existing text]

Options: (1) Supersede old  (2) Merge  (3) Defer to founder

DO_NOT_RESURFACE enforcement:

🚫 BLOCKED: "[Proposal]" was rejected on [DATE]. Reason: [reason].
To reopen: founder must explicitly say "reopen [topic] from [DATE]".

---

Logging Workflow (Post Phase 5)

1. Founder approves synthesis 2. Write Layer 1 raw transcript → ~/.claude/decisions/raw/YYYY-MM-DD-<slug>.md 3. Check conflicts against ~/.claude/decisions/approved/decisions.md 4. Surface conflicts → wait for founder resolution 5. Write the approved record to ~/.claude/decisions/approved/YYYY-MM-DD-<slug>.md and append to the index decisions.md 6. Confirm: decisions logged, actions tracked, DO_NOT_RESURFACE flags added

---

Marking Actions Complete

- [x] [Action] — Owner: [name] — Completed: [DATE] — Result: [one sentence]

Never delete completed items. The history is the record.

---

File Structure

~/.claude/decisions/
├── raw/YYYY-MM-DD-<slug>.md        # Layer 1: full transcript per meeting
├── raw/archive/YYYY/               # Raw files after 90 days
├── approved/YYYY-MM-DD-<slug>.md   # Layer 2: one record per approved decision
└── approved/decisions.md           # Layer 2 index: append-only, founder-approved

---

References

  • templates/decision-entry.md — single entry template with field rules
  • scripts/decision_tracker.py — CLI parser, overdue tracker, conflict detector

Related skills

How it compares

Pick decision-logger for markdown decision logs with owner deadlines; full PM tools are heavier when you only need parsed accountability reports.

FAQ

What file does decision-logger parse?

decision-logger parses memory/board-meetings/decisions.md using the bundled stdlib-only decision_tracker.py script. Reports include summary, overdue items, conflicts, per-owner views, search results, and due-within ranges.

What CLI commands does decision-logger support?

decision-logger supports `python decision_tracker.py --summary`, `--overdue`, `--conflicts`, `--owner`, `--search`, `--due-within`, and `--demo` for sample data—no external Python dependencies required.

Is Decision Logger safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.