decision-logger

Log board meeting decisions into a two-layer memory archive with YAML frontmatter.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Veloxia-agency/VELOXIA-WEB --skill decision-logger-veloxia-agency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-logger
Source: https://github.com/Veloxia-agency/VELOXIA-WEB/tree/main/.claude/skills/c-level-advisor/skills/decision-logger
Command: npx skills add https://github.com/Veloxia-agency/VELOXIA-WEB --skill decision-logger-veloxia-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It turns board meeting discussions into a reliable decision record so approved outcomes, owners, deadlines, and rejected ideas are captured without ambiguity or memory drift.

Core Features & Use Cases

  • Two-layer memory separates raw meeting transcripts from founder-approved decisions.
  • Conflict detection flags contradictory active decisions, owner clashes, and attempts to resurface rejected proposals.
  • Action tracking keeps deadlines, review dates, completed items, and overdue follow-ups visible for chiefs of staff and founders.
  • Use it after a board meeting to log the approved synthesis, or later to review past decisions and overdue action items.

Quick Start

Ask the skill to log today's board meeting decisions, check for conflicts, and update any open action items.

Frequently Asked Questions about decision-logger

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

FAQPage Schema
How do I maintain a reliable decision log for board meetings?

To maintain a reliable decision log, this Skill records board meeting outcomes into a two-layer memory archive, separating raw transcripts from founder-approved decisions to prevent memory drift and capture owners, deadlines, and rejected ideas without ambiguity.

What is the best way to track overdue action items from approved board decisions?

Tracking overdue action items is handled by applying action tracking to the approved decision entries, keeping deadlines, review dates, completed items, and overdue follow-ups visible for chiefs of staff and founders.

How do I detect conflicts or contradictions across past board meeting decisions?

Conflict detection works by applying contradiction checks across board discussions, flagging contradictory active decisions, owner clashes, and attempts to resurface rejected proposals using DO_NOT_RESURFACE enforcement.

Do I need YAML frontmatter to log approved decisions?

Yes, YAML frontmatter is required to log approved decisions, ensuring append-only decision entries are properly structured for founder-approved meeting synthesis, conflict detection, and overdue action tracking.

Can I enforce that rejected proposals from earlier board meetings are not brought back up?

Yes, rejected proposals are blocked from resurfacing through DO_NOT_RESURFACE enforcement, which actively flags attempts to reintroduce previously rejected ideas during conflict detection checks across board discussions.

When should I use an append-only decision archive for governance records?

An append-only decision archive should be used after board meetings to log the approved synthesis, or later to review past decisions, ensuring governance records remain immutable and track contradictions without memory drift.