decision-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.

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.

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.

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.

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.

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.