awareness-ledger

Capture institutional memory in structured incident, decision, pattern, and flow records.

2|1|Updated Feb 8, 2017
One-click install
npx skills add https://github.com/odysseyalive/dotfiles --skill awareness-ledger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: awareness-ledger
Source: https://github.com/odysseyalive/dotfiles/tree/main/.claude/skills/awareness-ledger
Command: npx skills add https://github.com/odysseyalive/dotfiles --skill awareness-ledger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Projects lose valuable context over time: incident analyses, trade-off decisions, recurring patterns, and operational flows are scattered across conversations, commits, and issue threads. This Skill centralizes that institutional memory so teams can consult past findings before making changes, reducing repeat failures and improving planning quality.

Core Features & Use Cases

  • Ledger recording: Create structured incident (INC), decision (DEC), pattern (PAT), and flow (FLW) records with templates and index updates.
  • Consultation & triage: Read the ledger index, match tags against current change context, synthesize relevant records, and escalate to consultation agents when risk overlap warrants deeper analysis.
  • Audit & review: Run health checks for stale or orphaned records, generate statistics, and flag gaps for follow-up.
  • Hooks & capture suggestions: Non-blocking hooks detect capture opportunities during debugging or task runs and prompt user-confirmed recording afterward.

Quick Start

Ask the ledger to consult relevant records for a proposed change by saying /awareness-ledger consult followed by the topic.

Frequently Asked Questions about awareness-ledger

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

FAQPage Schema
How do I capture and consult institutional memory for a software project?

To capture institutional memory, record structured incidents, decisions, patterns, and flows into a centralized ledger. You can consult these historical records during design reviews or incident investigations to reduce repeat failures and improve planning quality.

What is the best way to track historical decisions and incident analyses across development cycles?

Tracking historical decisions and incident analyses is best handled by centralizing context into structured ledger records. This approach makes past trade-offs and recurring patterns discoverable for future planning sessions and pull request evaluations.

How do I record new findings during debugging without modifying unrelated repository files?

You can record new findings during debugging using non-blocking hooks that suggest user-confirmed captures. This mechanism prompts you to log incidents afterward, ensuring only relevant ledger index and record files are updated without altering unrelated code.

Can I detect risk overlap automatically when evaluating a proposed code change?

Yes, risk overlap can be detected automatically by reading the ledger index and matching tags against the current change context. When overlap warrants deeper analysis, the system escalates by spawning consultation agents per protocol.

Does this decision-tracking approach work for auditing stale records and finding knowledge gaps?

Yes, this decision-tracking approach supports auditing by running health checks to identify stale or orphaned records. It generates statistics and flags knowledge gaps for follow-up, ensuring the institutional memory remains accurate and actionable.