← 返回 Skills 市场
alirezarezvani

Decision Logger

作者 Alireza Rezvani · GitHub ↗ · v2.1.1 · MIT-0
cross-platform ✓ 安全检测通过
420
总下载
0
收藏
5
当前安装
2
版本数
在 OpenClaw 中安装
/install decision-logger
功能描述
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions aft...
使用说明 (SKILL.md)

Decision Logger

Two-layer memory system. Layer 1 stores everything. Layer 2 stores only what the founder approved. Future meetings read Layer 2 only — this prevents hallucinated consensus from past debates bleeding into new deliberations.

Keywords

decision log, memory, approved decisions, action items, board minutes, /cs:decisions, /cs:review, conflict detection, DO_NOT_RESURFACE

Quick Start

python scripts/decision_tracker.py --demo             # See sample output
python scripts/decision_tracker.py --summary          # Overview + overdue
python scripts/decision_tracker.py --overdue          # Past-deadline actions
python scripts/decision_tracker.py --conflicts        # Contradiction detection
python scripts/decision_tracker.py --owner "CTO"      # Filter by owner
python scripts/decision_tracker.py --search "pricing" # Search decisions

Commands

Command Effect
/cs:decisions Last 10 approved decisions
/cs:decisions --all Full history
/cs:decisions --owner CMO Filter by owner
/cs:decisions --topic pricing Search by keyword
/cs:review Action items due within 7 days
/cs:review --overdue Items past deadline

Two-Layer Architecture

Layer 1 — Raw Transcripts

Location: memory/board-meetings/YYYY-MM-DD-raw.md

  • Full Phase 2 agent contributions, Phase 3 critique, Phase 4 synthesis
  • All debates, including rejected arguments
  • NEVER auto-loaded. Only on explicit founder request.
  • Archive after 90 days → memory/board-meetings/archive/YYYY/

Layer 2 — Approved Decisions

Location: memory/board-meetings/decisions.md

  • ONLY founder-approved decisions, action items, user corrections
  • Loaded automatically in Phase 1 of every board meeting
  • Append-only. Decisions are never deleted — only superseded.
  • Managed by Chief of Staff after Phase 5. Never written by agents directly.

Decision Entry Format

## [YYYY-MM-DD] — [AGENDA ITEM TITLE]

**Decision:** [One clear statement of what was decided.]
**Owner:** [One person or role — accountable for execution.]
**Deadline:** [YYYY-MM-DD]
**Review:** [YYYY-MM-DD]
**Rationale:** [Why this over alternatives. 1-2 sentences.]

**User Override:** [If founder changed agent recommendation — what and why. Blank if not applicable.]

**Rejected:**
- [Proposal] — [reason] [DO_NOT_RESURFACE]

**Action Items:**
- [ ] [Action] — Owner: [name] — Due: [YYYY-MM-DD] — Review: [YYYY-MM-DD]

**Supersedes:** [DATE of previous decision on same topic, if any]
**Superseded by:** [Filled in retroactively if overridden later]
**Raw transcript:** memory/board-meetings/[DATE]-raw.md

Conflict Detection

Before logging, Chief of Staff checks for:

  1. DO_NOT_RESURFACE violations — new decision matches a rejected proposal
  2. Topic contradictions — two active decisions on same topic with different conclusions
  3. Owner conflicts — same action assigned to different people in different decisions

When a conflict is found:

⚠️ DECISION CONFLICT
New: [text]
Conflicts with: [DATE] — [existing text]

Options: (1) Supersede old  (2) Merge  (3) Defer to founder

DO_NOT_RESURFACE enforcement:

🚫 BLOCKED: "[Proposal]" was rejected on [DATE]. Reason: [reason].
To reopen: founder must explicitly say "reopen [topic] from [DATE]".

Logging Workflow (Post Phase 5)

  1. Founder approves synthesis
  2. Write Layer 1 raw transcript → YYYY-MM-DD-raw.md
  3. Check conflicts against decisions.md
  4. Surface conflicts → wait for founder resolution
  5. Append approved entries to decisions.md
  6. Confirm: decisions logged, actions tracked, DO_NOT_RESURFACE flags added

Marking Actions Complete

- [x] [Action] — Owner: [name] — Completed: [DATE] — Result: [one sentence]

Never delete completed items. The history is the record.


File Structure

memory/board-meetings/
├── decisions.md       # Layer 2: append-only, founder-approved
├── YYYY-MM-DD-raw.md  # Layer 1: full transcript per meeting
└── archive/YYYY/      # Raw files after 90 days

References

  • templates/decision-entry.md — single entry template with field rules
  • scripts/decision_tracker.py — CLI parser, overdue tracker, conflict detector
安全使用建议
This appears to be a local, file-based decision logger and report generator that does not request secrets or install software. Before installing or enabling it for autonomous use: (1) Inspect the remainder of scripts/decision_tracker.py (search for open(..., 'w'/'a'), os.system/subprocess, socket or requests usage) to confirm it does not write files unexpectedly or make network calls. (2) If you intend to keep raw transcripts private, confirm the memory/board-meetings path is stored where you expect and that no other skill will load or transmit those files. (3) Run python scripts/decision_tracker.py --demo in a safe directory to see behavior and outputs. (4) If you rely on the SKILL.md 'append' workflow, ensure the team has an explicit process (or code) that performs appends under founder control — the provided script appears to be a parser/report tool and may not implement automated appending. If you want a deeper review, provide the remainder of the script for a full scan of any write or network operations.
功能分析
Type: OpenClaw Skill Name: decision-logger Version: 2.1.1 The decision-logger skill is a legitimate tool designed to manage board meeting transcripts and approved decisions using a structured two-layer memory system. The core logic in scripts/decision_tracker.py is a safe, standard-library-only parser that identifies overdue action items and detects decision conflicts without any network access, obfuscation, or unauthorized file operations. The instructions in SKILL.md and the templates are consistent with the stated purpose of maintaining an append-only record of founder-approved decisions.
能力评估
Purpose & Capability
Name/description and included files line up: a decision-logging memory architecture plus a Python CLI (scripts/decision_tracker.py) and a template. However, SKILL.md describes a logging workflow that includes writing raw transcripts and appending founder-approved entries to decisions.md, while the visible portion of scripts/decision_tracker.py is a parser/reporter (reads decisions.md and produces reports). This is a capability mismatch (documentation describes write steps; code appears read-only). Not necessarily malicious, but verify whether the script/other agent code performs any writes or automated appends before relying on the claimed workflow.
Instruction Scope
Runtime instructions operate on local project paths under memory/board-meetings/ (decisions.md, YYYY-MM-DD-raw.md, archive/). SKILL.md explicitly forbids auto-loading raw transcripts and defines DO_NOT_RESURFACE rules. There are no instructions to read unrelated system files, environment variables, or to transmit data to external endpoints.
Install Mechanism
No install spec is provided and the Python script claims to use only the standard library. That minimizes installation risk — nothing downloaded or extracted by the skill itself.
Credentials
The skill requires no environment variables, no credentials, and no config paths. All declared I/O is local files under memory/board-meetings/, which is proportionate to a decision-logging tool.
Persistence & Privilege
The skill is not marked always:true and uses the platform default for invocation. It does not request elevated/system-wide persistence. SKILL.md notes Layer 2 is loaded automatically by the board-meeting skill in Phase 1, which is a behavioral detail but not a privilege escalation in this package alone.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install decision-logger
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /decision-logger 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v2.1.1
v2.1.1: optimization, reference splits
v1.0.0
Initial release: C-suite orchestration skill.
元数据
Slug decision-logger
版本 2.1.1
许可证 MIT-0
累计安装 6
当前安装数 5
历史版本数 2
常见问题

Decision Logger 是什么?

Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions aft... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 420 次。

如何安装 Decision Logger?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install decision-logger」即可一键安装,无需额外配置。

Decision Logger 是免费的吗?

是的,Decision Logger 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Decision Logger 支持哪些平台?

Decision Logger 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Decision Logger?

由 Alireza Rezvani(@alirezarezvani)开发并维护,当前版本 v2.1.1。

💬 留言讨论