Log the Decision
Logs a founder-approved boardroom memo as a durable decision in two-layer memory via the decision-logger skill. It preserves raw transcripts for reference and stores only approved decisions, creating a structured record with success/kill criteria and preserved dissent.
✨ What it does
- Verifies founder approval (status: APPROVED) before logging.
- Extracts structured decision record: title, date, option, criteria, dissent, review date.
- Appends to approved decisions directory and updates raw transcript pointer.
- Optionally writes to company vault if llm-wiki bridge is configured.
- Schedules auto-revisit after 90 days.
- Preserves dissent verbatim in the output record.
🎯 When to use it
- After a /cs:boardroom session concludes with a founder-approved memo.
- When a decision must become durable company memory and feed future planning.
- When you need to record dissent verbatim to keep the company honest at post-mortem.
- When you need to schedule a 90-day review checkpoint for a decision.
🚀 How to use
Trigger: /cs:decide
Trigger with the slash command /cs:decide <memo-path> where <memo-path> is the path to the board memo file produced by /cs:boardroom. The skill reads the memo, checks for APPROVED status, and logs the decision. Example prompts:
/cs:decide memos/2025-03-15-boardroom.md
Log the decision from the latest boardroom memo.
📄 Output: A structured decision record file in ~/.claude/decisions/approved/ and an updated raw transcript pointer.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/c-level-agents/skills/decide .claude/skills/decideSkill source: c-level-agents/skills/decide/SKILL.md
⚠️ Good to know
Requires a board memo with founder approval (status: APPROVED); otherwise the skill will not log the decision.
❓ FAQ
What happens to raw transcripts?
Raw transcripts are stored under ~/.claude/decisions/raw/ for reference only and never feed back automatically.
Why is dissent preserved verbatim?
Preserving dissent verbatim keeps the company honest at post-mortem time, because when kill criteria trigger, the dissent often turns out to have been correct.
What does the skill do after logging?
It schedules an auto-revisit after 90 days and updates the raw transcript pointer; optionally writes to the company vault if configured.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.