decision-logger

Log CEO decisions and raw transcripts with a two-layer memory system.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit --skill decision-logger-getfresh-ventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-logger
Source: https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit/tree/main/skills/decision-logger
Command: npx skills add https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit --skill decision-logger-getfresh-ventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two-layer memory architecture helps logging and recalling CEO decisions by separating raw transcripts from approved conclusions. This separation enables robust audit trails, safer decision playback, and clean recall for future sessions.

Core Features & Use Cases

  • Layer 1 — Raw Transcripts: Location: memory/consultations/YYYY-MM-DD-raw.md, captures full agent contributions, critique, synthesis, and rejected arguments; not auto-loaded.
  • Layer 2 — Approved Decisions: Location: memory/consultations/decisions.md; stores only CEO-approved decisions and action items; loaded automatically at the start of every advisory session and never deleted.
  • Conflict Detection & Safety Guards: Checks for DO_NOT_RESURFACE violations, topic contradictions, and owner conflicts; surfaces conflicts for CEO resolution.
  • Logging Workflow: From transcription to decision logging, including conflict checks and archival.
  • Session Start Protocol & Proactive Triggers: On session start, loads Layer 2 decisions and flags overdue items; proactive prompts when decisions stall.
  • File Structure: memory/consultations/ with decisions.md and per-session raw transcripts and archive folders.

Quick Start

Log a CEO decision after a consult and review overdue actions at the next session.

Frequently Asked Questions about decision-logger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log and recall CEO decisions across multiple advisory sessions?

To log and recall CEO decisions, use a two-layer memory system that stores raw transcripts separately from CEO-approved decisions, enabling clean recall and audit trails at the start of every session.

What is the best way to track overdue action items from past consultations?

Tracking overdue action items requires a session start protocol that automatically loads approved decisions and flags stalled actions, prompting CEO resolution when consultations stall.

How do I maintain an audit trail for governance decisions without cluttering active memory?

Maintain a governance audit trail by separating raw transcripts into an archive folder while keeping only approved conclusions in a dedicated decisions file loaded at session start.

Can I detect conflicting decisions or topic contradictions when logging new conclusions?

Conflict detection checks for topic contradictions, owner conflicts, and do-not-resurface violations when logging new decisions, automatically surfacing any issues for CEO resolution.

Does the decision logging workflow support multi-role consultations with rejected arguments?

Multi-role consultations are fully supported by logging full agent contributions, critique, synthesis, and rejected arguments into raw transcript files before extracting CEO-approved decisions.

Why do I need a separate raw transcript store instead of just logging approved decisions?

A separate raw transcript store is needed to preserve full agent contributions and rejected arguments for audit purposes while keeping the approved decisions file clean for automatic session loading.