Decision Logger

The Decision Logger skill creates a two-layer memory system for tracking and managing decisions.

Install

npx promptshop add decision-logger

Details

What This Skill Does

The Decision Logger skill creates a two-layer memory system for tracking and managing decisions. It stores raw transcripts and approved decisions separately, preventing past debates from influencing new deliberations. It's designed for founders and chiefs of staff to maintain a clear and accurate record of decisions.

When to Use

Tracking board meeting decisions.
Reviewing past decisions and action items.
Filtering decisions by owner or topic.
Identifying conflicting decisions.
Maintaining a clear decision history.
Preventing 'hallucinated consensus' from past debates.

Key Features

Two-layer architecture for raw transcripts and approved decisions.
Commands for reviewing, filtering, and searching decisions.
Decision entry format for consistent documentation.
Prevents past debates from influencing current discussions.
Managed by Chief of Staff for accuracy.
Supports conflict detection and overdue action item tracking.

Manual Installation

Manual installation

View Full Skill Content

The complete markdown content that gets installed

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, D

O_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 "C

TO" # Filter by owner python scripts/decision_tracker.py --search "pricing" # Search decisions

Commands

Command	Effect
/cs:decisions	Last 10 approved decisions
/cs:decisions --all	Full history
/cs:decisions --owner C

Two-Layer Architecture

Layer 1 — Raw Transcripts

Location: memory/board-meetings/Y

YYY-MM-DD-raw.md Full Phase 2 agent contributions, Phase 3 critique, Phase 4 synthesis All debates, including rejected arguments N

EVER auto-loaded. Only on explicit founder request. Archive after 90 days → memory/board-meetings/archive/Y

YYY/

Layer 2 — Approved Decisions

Location: memory/board-meetings/decisions.md O

NLY 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.

Decision Entry Format

[Y

YYY-MM-DD] — [A

GENDA I

TEM T

ITLE]

Decision: [One clear statement of what was decided.] Owner: [One person or role — accountable for execution.] Deadline: [Y

YYY-MM-DD] Review: [Y

YYY-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] [D

O_NOT_RESURFACE]

Action Items: [ ] [Action] — Owner: [name] — Due: [Y

YYY-MM-DD] — Review: [Y

YYY-MM-DD]

Supersedes: [D

ATE of previous decision on same topic, if any] Superseded by: [Filled in retroactively if overridden later] Raw transcript: memory/board-meetings/[D

ATE]-raw.md

Conflict Detection

Before logging, Chief of Staff checks for: D

O_NOT_RESURFACE violations — new decision matches a rejected proposal Topic contradictions — two active decisions on same topic with different conclusions Owner conflicts — same action assigned to different people in different decisions

When a conflict is found: ⚠️ D

ECISION C

ONFLICT New: [text] Conflicts with: [D

ATE] — [existing text]

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

O_NOT_RESURFACE enforcement: 🚫 B

LOCKED: "[Proposal]" was rejected on [D

ATE]. Reason: [reason]. To reopen: founder must explicitly say "reopen [topic] from [D

ATE]".

Logging Workflow (Post Phase 5)

Founder approves synthesis Write Layer 1 raw transcript → Y

YYY-MM-DD-raw.md Check conflicts against decisions.md Surface conflicts → wait for founder resolution Append approved entries to decisions.md Confirm: decisions logged, actions tracked, D

O_NOT_RESURFACE flags added

Marking Actions Complete

[Action] — Owner: [name] — Completed: [D

ATE] — Result: [one sentence]

Never delete completed items. The history is the record.

File Structure

memory/board-meetings/ ├── decisions.md # Layer 2: append-only, founder-approved ├── Y

YYY-MM-DD-raw.md # Layer 1: full transcript per meeting └── archive/Y

YYY/ # Raw files after 90 days

References

templates/decision-entry.md — single entry template with field rules scripts/decision_tracker.py — C

LI parser, overdue tracker, conflict detector

Decision Logger

Keywords

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

O_NOT_RESURFACE

Quick Start

TO" # Filter by owner python scripts/decision_tracker.py --search "pricing" # Search decisions

Commands

Command	Effect
/cs:decisions	Last 10 approved decisions
/cs:decisions --all	Full history
/cs:decisions --owner C

Two-Layer Architecture

Layer 1 — Raw Transcripts

Location: memory/board-meetings/Y

YYY-MM-DD-raw.md Full Phase 2 agent contributions, Phase 3 critique, Phase 4 synthesis All debates, including rejected arguments N

EVER auto-loaded. Only on explicit founder request. Archive after 90 days → memory/board-meetings/archive/Y

YYY/

Layer 2 — Approved Decisions

Location: memory/board-meetings/decisions.md O

Decision Entry Format

Conflict Detection

Before logging, Chief of Staff checks for: D

When a conflict is found: ⚠️ D