← All skills
decision-logger
Use when logging decisions after a board meeting, reviewing past decisions, or checking overdue action items—invoked automatically after boardroom approvals.
About this skill
Use when logging decisions after a board meeting, reviewing past decisions, or checking overdue action items—invoked automatically after boardroom approvals.
SKILL.md
decision-logger.SKILL.mdPlace it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review the contents and run it in a controlled environment first.
--- name: decision-logger description: Use when logging decisions after a board meeting, reviewing past decisions, or checking overdue action items—invoked automatically after boardroom approvals. category: C-Level Advisory version: 1.0.0 tools: [] --- # Decision Logger Two-layer memory system. Layer 1 stores everything. Layer 2 stores only founder-approved decisions. Future meetings read Layer 2 only—prevents hallucinated consensus bleeding into new deliberations. ## Quick 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:** ~/.syntic/decisions/raw/YYYY-MM-DD-<slug>.md - Full Phase 2 contributions, Phase 3 critique, Phase 4 synthesis, all debates - NEVER auto-loaded; only on explicit founder request - Archive after 90 days ### Layer 2 — Approved Decisions **Location:** ~/.syntic/decisions/approved/ - ONLY founder-approved decisions, actions, and corrections - Loaded automatically in future deliberations - Append-only; never deleted, only superseded ## Decision Entry Format **Decision:** [Clear statement.] **Owner:** [One person — accountable.] **Deadline:** [YYYY-MM-DD] **Review:** [YYYY-MM-DD] **Rationale:** [Why this over alternatives.] **Rejected:** - [Proposal] — [reason] [DO_NOT_RESURFACE] **Action Items:** - [ ] [Action] — Owner: [name] — Due: [YYYY-MM-DD] **Supersedes:** [DATE of previous decision] ## Conflict Detection Before logging, check for: 1. **DO_NOT_RESURFACE violations** — new decision matches rejected proposal 2. **Topic contradictions** — two active decisions on same topic with different conclusions 3. **Owner conflicts** — same action assigned to different people When found, surface for founder resolution before logging. ## Marking Actions Complete Never delete completed items. History is the record. - [x] [Action] — Owner: [name] — Completed: [DATE] — Result: [one sentence] ## File Structure ~/.syntic/decisions/ ├── raw/YYYY-MM-DD-<slug>.md (Layer 1: full transcript) ├── raw/archive/YYYY/ (after 90 days) ├── approved/YYYY-MM-DD-<slug>.md (Layer 2: approved record) └── approved/decisions.md (Layer 2 index: append-only)
Install
Syntic App
- 1Create a dedicated folder for this skill in your local skills library.
- 2Place SKILL.md into that folder.
- 3Restart Syntic and invoke this skill on matching tasks.
Syntic Code (CLI)
- 1Save SKILL.md in your local Syntic Code skills directory.
- 2Keep related files in the same skill folder.
- 3Run in a safe environment and validate outputs.