Agent skill · product strategy · borghei
decision-logger
Two-layer memory for executive decisions, separating raw deliberation from approved decisions to prevent hallucinated consensus. Use when logging decisions, reviewing past decisions, or checking overdue action items.
Why this skill is useful
Introduces a structured decision logging framework that prevents hallucinated consensus and enhances accountability in executive decision-making.
What it needs
About 11k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Decision Logger Two-layer memory system for executive decisions. Layer 1 stores everything discussed. Layer 2 stores only what the founder approved. Future sessions 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, conflict detection, DONOTRESURFACE, decision history, overdue, supersession, decision search, decision tracking, accountability --- Two-Layer Architecture Why Two Layers? Single-layer decision logs create a dangerous problem: agents read old debates, rejected proposals, and discarded ideas, then treat them as context for new decisions. This causes "hallucinated consensus" where rejected ideas gradually become accepted through repetition. The two-layer system prevents this by strictly separating raw discussion from approved decisions. Layer Architecture Layer Interaction Rules Rule Rationale ------ ----------- Layer 2 is append-only Preserves complete decision history Layer 1 is never auto-loaded Prevents hallucinated consensus Only Chief of Staff writes to Layer 2 Single point of control Agents never write directly All writes go through Chief of Staff after founder approval Superseded decisions stay in Layer 2 History is the record; nothing is deleted --- Decision Entry Format Standard Decision Record Completed Action Item Format --- Conflict Detection System Before logging any new decision, the system checks for three types of conflicts. Conflict Type 1: DONOTRESURFACE Violation A new decision matches a previously rejected proposal. Conflict Type 2: Topic Contradiction Two active decisions on the same topic reach different conclusions. Conflict Type 3: Owner Conflict Same action assigned to different people in different decisions. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/decision-logger