Decision Logger

Two-layer memory architecture for board meeting decisions.

Business & Ops / Executive Advisorybusiness-opsexecutive-advisory
by AgentVoltv1.0.0Published 1y ago1 install
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

PromptLog the decisions from today’s board meeting.
Beforegeneric AI agent
I can help you capture your board meeting decisions. Here's what I'd typically record for each one:

- The decision made
- The context and rationale
- Who's responsible for any follow-up
- Deadlines for action items
- Any dissent or conditions

If you share your notes or the transcript, I can organize these into a clean record. It's good practice to distinguish between discussion points and actual decisions — not everything discussed becomes a decision.

Would you like to paste your meeting notes?
Afterwith Decision Logger
Two-layer log. Layer 1 keeps the raw transcript; Layer 2 holds only
approved decisions. Nothing enters Layer 2 without founder sign-off —
that gate is the point.

FROM TODAY'S TRANSCRIPT — 4 decisions, 3 discussions, separated

  DECISIONS (pending your approval → Layer 2)
  D1  Raise the Series A in Q1, target $8M
      Rationale: 15 months runway, metrics hit A bar by Dec
      Owner: CEO · Action: engage bankers by Jan 15
  D2  Pause the EU expansion until post-raise
      Rationale: capital discipline; revisit at board+1
      Owner: COO · no action until raise closes
  D3  Approve the $200K security budget (Tier 2)
      Owner: CTO · Action: SOC 2 kickoff this month
  D4  Move to quarterly board cadence from monthly

  DISCUSSED, NOT DECIDED (stays in Layer 1 only)
  • Pricing increase — explored, no resolution, revisit next board
  • A potential exec hire — CEO to bring a proposal, not a decision
  • Competitor's raise — context, no action

WHY THE SPLIT MATTERS
The pricing item felt like a decision in the room. It wasn't — no owner,
no approval. Logging it as decided would have someone acting on a
conversation. The gate catches exactly this.

ACTION ITEMS WITH DATES
  D1 → bankers engaged by Jan 15 (CEO)
  D3 → SOC 2 kickoff by month-end (CTO)

Approve D1–D4 for Layer 2? Anything you approve becomes reviewable later
with /cs:decisions, and the two dated items surface in /cs:review when
they're overdue.

About this skill


name: decision-logger description: Use when Two-layer memory architecture for board meeting decisions.

Decision Logger

Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.

What you get

  • Public GitHub repo (alirezarezvani/claude-skills)
  • the decision-logger skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.

Customize your output

  • Fork the repo and adapt the skill's instructions and references to your workflow.

Example output

Activates automatically when your request matches Decision Logger; chains with the other skills, agents, and commands in the collection.

Best for

Creators, builders, and teams using Claude Code.

SKILL.md preview

SKILL.md
---
name: decision-logger
description: Use this skill after a board meeting to log decisions into a two-layer memory system, or to review past decisions and overdue action items.
version: 1.0.0
category: Business & Ops / Executive Advisory
author: AgentVolt
license: proprietary
tags:
  - business-ops
  - executive-advisory
---

# Decision Logger

Maintains a two-layer memory of board decisions: raw transcripts as Layer 1, founder-approved decisions with owners and deadlines as Layer 2.

## When to use

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More business & ops skills

View all Business & Ops skills →