decision-log

Capture decisions as structured events and write them to events.jsonl.

Updated Aug 23, 2026

Search Tags:#logging #decision #governance #history #slack #meetings

Ready to run

npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill decision-log-chaletteholdings

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-log
Source: https://github.com/chaletteholdings/command-room-releases-2710/tree/main/command-room/skills/decision-log
Command: npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill decision-log-chaletteholdings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns every decision made by leadership — in meetings, Slack threads, or ad-hoc thinking — into a searchable, time-stamped log with who decided, when, why, and what changed. It ensures a durable historical record that’s easy to query and review for governance, accountability, and post-mortems.

Core Features & Use Cases

Real-time Decision Logging: capture decisions as events so you can trace decisions back to their origin.
Rationale & Traceability: store who decided, why, and what changed to support future audits.
Governance & Retrieval: regenerate the DECISION_LOG.md view and search by topic, date, or decision maker across meetings and channels.

Quick Start

Log a decision by stating 'we decided' or 'log decision' during a session to append it to the decision log.

Frequently Asked Questions about decision-log

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

FAQPage Schema

How do I capture decisions from Slack threads and meetings into a searchable log?▼

To capture decisions into a searchable log, simply state 'we decided' or 'log decision' during a session. The Skill appends the event to a central log, storing who decided, when, and why across Slack threads and meetings.

What is the best way to maintain governance history for leadership decisions?▼

Maintaining governance history requires storing every decision as a structured, time-stamped event. This Skill records the decision maker, rationale, and changes, regenerating a DECISION_LOG.md view for accountability and post-mortems.

How do I retrieve past decisions by topic or decision maker for a post-mortem?▼

Retrieving past decisions by topic, date, or decision maker is done by searching the regenerated DECISION_LOG.md view. The Skill aggregates structured events from meetings and Slack threads to provide a searchable history for post-mortems.

Does this decision logging tool require any specific integrations or dependencies?▼

No specific dependencies are required to use this decision logging tool. It applies across meetings and Slack threads natively, writing structured events to an events.jsonl file to preserve rationale and history.

Can I trace why a leadership decision changed over time in the decision log?▼

Tracing why a leadership decision changed is possible because the Skill stores what changed and the original rationale. It captures every decision as a time-stamped event, ensuring traceability and supporting future audits.

What file formats does the decision logging process use to store history?▼

The decision logging process writes structured events to an events.jsonl file and regenerates a DECISION_LOG.md view. These formats preserve the rationale, maker, and timestamp for governance retrieval.