| name | awareness-ledger |
| description | Institutional memory for your project. Commands: record, consult, review. Usage: /awareness-ledger [command] [args] |
| allowed-tools | Read, Glob, Grep, Write, Edit, Task, TaskCreate, TaskUpdate, TaskList, TaskGet |
Awareness Ledger
Institutional memory for this project โ captures incidents (INC), decisions (DEC),
patterns (PAT), and flows (FLW) so diagnostic findings and architectural decisions
survive across sessions and teammates.
Quick Commands
| Command | Action |
|---|
/awareness-ledger record [type] | Record a new INC / DEC / PAT / FLW entry |
/awareness-ledger consult [topic] | Consult the ledger before a plan/change (agent-assisted) |
/awareness-ledger review | Health check: stale entries, missing links, statistics |
Directives
Auto-Consultation (READ)
During research and planning โ before formulating any plan, recommendation, or
code change proposal โ automatically consult the ledger:
- Index scan โ Read
ledger/index.md and match tags against the files,
directories, and components under discussion. This is free โ the index is small.
- Record review โ If matching records exist, read the full record files.
Incorporate warnings, known failure modes, and relevant decisions into your
thinking before presenting any plan.
- Agent escalation โ If high-risk overlap is detected (matching INC records
with active status, or multiple record types matching the same change area),
spawn consultation agents proportionally per
references/consultation-protocol.md.
Skip auto-consultation for: changes to .claude/ infrastructure files; trivial
edits (typos, formatting, comments); areas with no tag overlap in the index.
Auto-Capture Suggestion (WRITE)
When the current conversation produces institutional knowledge, suggest recording
it after resolving the immediate issue โ never interrupt active problem-solving.
Suggest capture when you encounter:
- Bug investigation with timeline/root cause/contributing factors โ INC
- Architectural decisions with trade-offs discussed and option chosen โ DEC
- Recurring patterns confirmed by evidence โ PAT
- User/system flows traced step-by-step with code paths โ FLW
Capture is always user-confirmed. Agents suggest, the user decides. Directives are
sacred โ never auto-record.
record Command
- Determine record type (INC/DEC/PAT/FLW) from the argument or the conversation.
- Read the matching template in
references/templates.md.
- Generate an ID
TYPE-YYYY-MM-DD-slug and write the filled record to the matching
ledger/<incidents|decisions|patterns|flows>/ subdirectory.
- Update
ledger/index.md (By Tag, By Status, Relationship Map, Statistics).
consult Command
Follow references/consultation-protocol.md: triage the topic โ spawn agents
proportionally (one match โ one agent, multiple โ full panel, empty ledger โ skip)
โ synthesize into the Consultation Briefing โ suggest capture if warranted.
review Command
Scan all records for: stale active entries, broken Related: links, tag drift,
and proposed records never confirmed. Report statistics and recommended cleanups.
Grounding
references/templates.md โ record formats (INC/DEC/PAT/FLW), status lifecycle, index rules
references/consultation-protocol.md โ triage, proportional agent spawning, synthesis
references/capture-triggers.md โ conversation signals that warrant a record vs. auto memory