Percerno Skillsbeta
← everything it can do · finance

Decision Logger DOCX

Manages a two-layer memory system for board meeting decisions, storing raw transcripts and founder-approved decisions with conflict detection. It tracks action items, enforces 'DO_NOT_RESURFACE' rules for rejected proposals, and provides commands to review past decisions or check overdue tasks.

4 uses this weeksource alirezarezvanilicence MIT
Quality gate: FAIL · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift -20.0 points (specificity, structure, method, fit).
won 0/2, lift -20.0, tokens ×97.99
Security scan: review · 2026-10-24 · 3 files · ran in sandbox
something a person should read before trusting it: hidden-imperative ×1.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Loggér beslutningen om at skifte til B2B-modellen fra dagens bestyrelsesmøde.”
“Vis mig alle forfaldne handlingspunkter fra de seneste møder.”
“Er der nogen konflikter mellem den nye marketingstrategi og tidligere afviste forslag?”
“Log the decision from today's board meeting regarding the pivot to B2B SaaS.”
“/decision-logger review --overdue”
“Check if there are any conflicts with our new pricing strategy proposal against last month's rejected ideas.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

board-meetingsdecision-loggingaction-itemsmemory-managementconflict-detectioncomplianceaudit-trailgovernance

Not for

Do not use this skill for drafting meeting agendas, facilitating real-time debate, or generating initial strategic recommendations, as those are handled by the board-meeting or c-level-agents skills. It is not for general project management or task tracking outside the context of board-level governance decisions.

Details

When it is the right choice

Use this skill to log decisions after a board meeting has concluded and the founder has approved the synthesis. It is also the correct tool for querying the history of approved decisions, checking for overdue action items, or detecting conflicts between new proposals and previously rejected ideas.

The full recipe the assistant reads

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, /decision-logger decisions, /decision-logger 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

Command Effect
/decision-logger decisions Last 10 approved decisions
/decision-logger decisions --all Full history
/decision-logger decisions --owner CMO Filter by owner
/decision-logger decisions --topic pricing Search by keyword
/decision-logger review Action items due within 7 days
/decision-logger review --overdue Items 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 /c-level-agents: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
Files in this skill (4)
  • LICENSE
  • SKILL.md
  • scripts/decision_tracker.py
  • templates/decision-entry.md
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-advisor/skills/decision-logger, licence MIT. The upstream licence file ships inside the skill.