New to Claude Skills? Learn how to install them →

alirezarezvani on GitHub

Decision Logger

Free

Efficiently manage board meeting decisions and action items.

Get this skill

Free · Opens the source repo

What Decision Logger does

The Decision Logger skill provides a structured two-layer memory system specifically designed for logging and managing decisions made during board meetings. This system distinguishes between raw transcripts of discussions and approved decisions, ensuring clarity and preventing confusion in future meetings. Layer 1 captures all contributions and debates, while Layer 2 retains only the decisions that have been officially approved by the founder. This separation helps maintain focus on actionable items and prevents past discussions from clouding current decision-making processes.

The skill is particularly useful for organizations that conduct regular board meetings and need a reliable way to track decisions and action items. By utilizing commands like /cs:decisions and /cs:review, users can easily access the latest approved decisions or review overdue action items, streamlining the follow-up process. The conflict detection feature further enhances the skill’s utility by identifying contradictions or potential issues before decisions are finalized, ensuring that all team members are on the same page.

For those involved in governance or management roles, the Decision Logger skill serves as a critical tool for maintaining accountability and transparency. It allows users to filter decisions by owner or topic, making it easier to track responsibilities and deadlines. The append-only nature of the decision records ensures a complete history of decisions, which can be invaluable for audits or retrospective reviews.

Overall, the Decision Logger skill is designed for teams that prioritize organized decision-making and need a robust system to manage the complexities of board meeting outcomes. By automating the logging process and providing clear access to historical decisions, it enhances productivity and facilitates better governance.

When to use it

Use this skill after board meetings to log decisions and track action items effectively.

When not to use it

This skill may not be suitable for informal decision-making processes or teams that do not require structured logging of their discussions.

What you can build with it

Logging Decisions After Meetings

After a board meeting, use the Decision Logger to document all decisions made, ensuring that only approved items are recorded for future reference.

Reviewing Overdue Action Items

Quickly check overdue action items with the /cs:review command to ensure accountability and follow up on outstanding tasks.

Detecting Decision Conflicts

Before finalizing a new decision, run the conflict detection feature to identify any contradictions with past decisions, ensuring clarity and consensus.

How to install Decision Logger

View source

1. Install with the skills CLI

npx skills add alirezarezvani/claude-skills/decision-logger --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by alirezarezvani

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

Frequently asked questions about Decision Logger

Similar skills