decisions-log

Maintain an append-only log of operator decisions for session coherence.

20|15|Updated May 7, 2026
One-click install
npx skills add https://github.com/iamasters-academy/iamasters-os --skill decisions-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decisions-log
Source: https://github.com/iamasters-academy/iamasters-os/tree/main/.claude/skills/_meta/decisions-log
Command: npx skills add https://github.com/iamasters-academy/iamasters-os --skill decisions-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that important decisions made by the operator are recorded in a consistent and accessible format, maintaining session coherence and preventing contradictions between sessions.

Core Features & Use Cases

  • Decision Journaling: Keeps an append-only log of critical decisions made by the operator, with a fixed format for easy reference and review.
  • Session Coherence: Prevents contradictions between sessions by recording decisions and their context.
  • Use Case: Ideal for recording strategic decisions that require future reference, such as pricing strategies, marketing decisions, or project milestones.

Quick Start

Record a decision using the 'register-decision' command followed by the decision details.

Frequently Asked Questions about decisions-log

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

FAQPage Schema
How do I maintain a decision log for session coherence across different operator sessions?

A decision log maintains session coherence by using an append-only journal that records critical operator decisions. It reads existing entries at session start to prevent contradictions and requires user confirmation before appending new decisions.

What is an append-only decision journal and why is it needed for operator decisions?

An append-only decision journal is a fixed-format record of critical operator decisions that cannot be altered once saved. It is needed to prevent contradictions between sessions and provide consistent context for strategic choices like pricing or project milestones.

How do I register a new decision in the decision logging system?

To register a decision, use the register-decision command followed by the decision details. The system requires your input for the context and confirms with you before appending the entry to the decision log.

Can I use decision logging for strategic project milestones and marketing decisions?

Yes, decision logging is ideal for recording strategic decisions that require future reference, such as pricing strategies, marketing decisions, or project milestones, ensuring consistent context across sessions.

Does decision logging support modifying or deleting past operator decisions?

No, decision logging uses an append-only format, meaning past operator decisions cannot be modified or deleted. This maintains the integrity of the decision journal and prevents historical contradictions.