skills.rest
jmigrala
jmigralaCOMMUNITY
Explore all skills by this author →
GitHub

decision-logger

Organize board meeting decisions into raw transcripts and approved decisions.

Updated Oct 30, 2025
Search Tags:#memory#decision-log#action-items#conflict-detection#approved-decisions#board-minutes#do_not_resurface
One-click install
npx skills add https://github.com/jmigrala/priceyourfence --skill decision-logger-jmigrala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-logger
Source: https://github.com/jmigrala/priceyourfence/tree/main/.agents/skills/decision-logger
Command: npx skills add https://github.com/jmigrala/priceyourfence --skill decision-logger-jmigrala

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a two-layer memory system for board meeting decisions, separating raw transcripts (Layer 1) from founder-approved decisions (Layer 2) to prevent past debates from influencing future deliberations.

Core Features & Use Cases

  • Two-layer architecture with Layer 1 raw transcripts at memory/board-meetings/YYYY-MM-DD-raw.md and Layer 2 decisions.md containing only founder-approved decisions.
  • Structured decision entries with DO_NOT_RESURFACE, action items, and a history that supports backtracking and governance reviews.
  • Use the /cs:decisions and /cs:review commands to review past decisions and overdue items during or after board meetings.

Quick Start

Activate the Decision Logger during board meetings to capture raw transcripts and surface approved decisions into memory/board-meetings/decisions.md.

Frequently Asked Questions about decision-logger

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

FAQPage Schema
How do I separate raw board meeting transcripts from approved decisions to prevent past debates from influencing future deliberations?▼

Board meeting decisions use a two-layer memory architecture that separates raw transcripts in Layer 1 from founder-approved decisions in Layer 2, preventing past debates from surfacing during future deliberations.

How do I log board decisions and review overdue action items after a meeting?▼

You can log board decisions and review overdue action items by using the /cs:decisions command to check past decisions and the /cs:review command to surface overdue action items during or after board meetings.

What is the structured format for logging board meeting decisions and action items?▼

The structured decision-entry format requires logging founder-approved decisions into a dedicated decisions.md file, capturing action items and supporting a DO_NOT_RESURFACE flag to control future meeting context.

How does conflict detection work when logging approved board decisions?▼

The system provides a governance workflow for conflict detection and safe logging, automatically surfacing Layer 2 founder-approved decisions after Phase 5 approval to ensure only vetted entries are recorded.

Can I backtrack on a previously approved board decision during a governance review?▼

Yes, the decision-log history supports backtracking and governance reviews, allowing you to manage and revisit founder-approved decisions and action items stored in the Layer 2 memory file.

Related Skills

Explore More Content & Communication Skills→
tapanshahtapanshah

decision-logger

Manage board meeting decisions with two-layer memory and conflict detection.

Community
Advanced
devCharuzudevCharuzu

decision-logger

Parse decisions.md to log board decisions and detect conflicts.

Community
Intermediate
Veloxia-agencyVeloxia-agency

decision-logger

Log board meeting decisions into a two-layer memory archive with YAML frontmatter.

Community
Advanced
Fantasia1999Fantasia1999

decision-logger

Manage board meeting decisions with dual-layer memory and conflict detection.

Community
Advanced