Decision Logger
Decision Logger implements a two-layer memory system for board meeting decisions: Layer 1 stores raw transcripts, and Layer 2 stores only founder-approved decisions. It manages logging, conflict detection, and overdue action item tracking, ensuring future meetings rely only on approved decisions.
✨ What it does
- Two-layer storage: raw transcripts (Layer 1) and approved decisions (Layer 2).
- Conflict detection for DO_NOT_RESURFACE violations, topic contradictions, and owner conflicts.
- Append-only approved decision index with supersession tracking.
- CLI tool for summaries, overdue items, conflict checks, and searches.
- Automatic loading of approved decisions in board meetings.
- Action item tracking with completion marking.
🎯 When to use it
- After a board meeting, when the founder has approved the synthesis and decisions need to be logged.
- When reviewing past approved decisions using /cs:decisions.
- When checking overdue action items with /cs:review.
- When detecting conflicts between new decisions and previously rejected proposals or existing decisions.
🚀 How to use
Trigger: /cs:decisions
Trigger via slash commands /cs:decisions (view approved decisions) or /cs:review (action items due within 7 days, with --overdue for past deadline). The skill is also invoked automatically by the board-meeting skill after Phase 5 founder approval. Inputs include meeting transcripts and founder-approved decisions. Example prompts:
/cs:decisions --owner CTO
/cs:review --overdue
📄 Output: Logs decisions to ~/.claude/decisions/ with raw transcripts and approved records, updates the index, and provides summaries or conflict alerts.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/c-level-advisor/skills/decision-logger .claude/skills/decision-loggerSkill source: c-level-advisor/skills/decision-logger/SKILL.md
⚠️ Good to know
Requires Python environment for the CLI script; Layer 1 raw transcripts are never auto-loaded and are archived after 90 days.
❓ FAQ
What is the difference between Layer 1 and Layer 2?
Layer 1 stores raw transcripts of all debates, including rejected arguments, and is never auto-loaded. Layer 2 stores only founder-approved decisions and action items, and is loaded automatically in future meetings.
How are conflicts handled?
The skill checks for DO_NOT_RESURFACE violations, topic contradictions, and owner conflicts. When found, it surfaces options to supersede, merge, or defer to the founder.
Can decisions be deleted?
No, decisions are append-only and never deleted. They can only be superseded by newer decisions.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.