name: knowledge-management description: Implement Zettelkasten-inspired knowledge management for building and maintaining context libraries with automated cross-referencing. Use when organizing executive knowledge, building context libraries, or implementing knowledge compounding systems.

Knowledge Management

Master knowledge management patterns for building context libraries that compound over time using Zettelkasten principles adapted for AI-assisted executive work.

When to Use This Skill

Building context libraries for organizations or projects
Implementing cross-referencing systems between knowledge nodes
Organizing executive knowledge across multiple contexts
Creating knowledge bases that grow more valuable over time
Migrating from fragmented tools to unified knowledge systems
Setting up automated knowledge maintenance workflows
Establishing patterns for knowledge extraction from conversations

Core Concepts

1. Context Library Architecture

Three-Level Hierarchy

Organization Level: Company-wide knowledge, playbooks, patterns
Project Level: Project-specific context, decisions, research
Conversation Level: Session-specific work, ephemeral notes

Knowledge Node Types

Atomic Notes: Single concept or insight (200-500 words)
Map Notes: Connect related atomic notes, provide structure
Synthesis Notes: Extract patterns across multiple atomic notes
Index Notes: Entry points for specific topics or themes

2. Zettelkasten Principles (AI-Adapted)

Atomicity: Each note captures one idea completely

Makes notes reusable across contexts
Enables precise cross-referencing
Facilitates automated pattern detection

Connectivity: Dense links between related notes

Bidirectional references
Contextual backlinks
Semantic clustering

Progressive Disclosure: Notes reveal complexity gradually

Start with executive summary
Link to detailed analysis
Provide multiple reading paths

3. Cross-Reference System

Link Types

- [[note-id]]: Basic reference
- [[note-id|description]]: Annotated reference
- See: [[note-id]]: Explicit pointer
- Cf: [[note-id]]: Compare/contrast
- Related: [[note-id]]: Thematic connection

Backlink Management

Automated backlink generation
Bidirectional reference validation
Orphan note detection

4. Knowledge Lifecycle

Creation: Extract from conversations/research Refinement: Agent-assisted synthesis Connection: Automated cross-referencing Evolution: Version-controlled updates Pruning: Remove obsolete knowledge

Quick Start

# Initialize context library for a project
/kaaos:init personal

# Structure created:
# organizations/personal/
# ├── context-library/
# │   ├── 00-INDEX.md
# │   ├── playbooks/
# │   ├── patterns/
# │   ├── decisions/
# │   └── references/
# └── projects/

# Create your first atomic note
cd ~/kaaos-knowledge/organizations/personal/context-library

Implementation Patterns

Pattern 1: Atomic Note Creation

---
id: 2026-01-001
type: atomic
tags: [strategy, decision-making, frameworks]
created: 2026-01-12
updated: 2026-01-12
---

# Pre-Mortem Analysis Framework

## Summary
Pre-mortem analysis involves imagining a project has failed and working backward to identify potential causes before project start.

## When to Use
- Before major strategic initiatives
- Prior to product launches
- When team consensus feels premature
- For high-stakes decisions

## Process
1. Assume the project failed catastrophically
2. Each team member writes failure causes (5 min, silent)
3. Share and cluster common themes
4. Identify top 3-5 risks
5. Create mitigation plans for each

## Benefits
- Surfaces concerns people hesitate to voice
- Identifies blind spots in planning
- Builds team psychological safety
- Creates actionable risk mitigation

## Implementation
```bash
# In project kickoff meeting
1. Set timer for 5 minutes
2. "It's [date + 6 months]. Project failed. Why?"
3. Collect responses anonymously
4. Group and discuss

[[2026-01-002|Risk Assessment Frameworks]]
[[2026-01-015|Team Psychological Safety]]
Cf: [[2026-01-003|Post-Mortem Process]]

Sources

Gary Klein, "Performing a Project Premortem"
Personal experience: Applied at 15+ companies

Last synthesized: 2026-01-12 by orchestrator


### Pattern 2: Map Note for Navigation

```markdown
---
id: MAP-strategic-frameworks
type: map
tags: [strategy, frameworks, navigation]
created: 2026-01-12
updated: 2026-01-15
---

# Strategic Frameworks Map

Navigation hub for strategic decision-making frameworks and methodologies.

## Risk & Uncertainty

**Before Decisions**
- [[2026-01-001|Pre-Mortem Analysis]] - Identify failure modes
- [[2026-01-005|Red Team Analysis]] - Challenge assumptions
- [[2026-01-008|Scenario Planning]] - Model futures

**During Execution**
- [[2026-01-010|Weekly Risk Review]] - Track emerging risks
- [[2026-01-012|Early Warning Signals]] - Detect problems early

## Decision-Making

**Strategic Choices**
- [[2026-01-020|One-Way vs Two-Way Doors]] - Decision reversibility
- [[2026-01-021|OODA Loop]] - Rapid decision cycles
- [[2026-01-023|Eisenhower Matrix]] - Prioritization

**Operational Decisions**
- [[2026-01-025|Decision Logs]] - Track decision rationale
- [[2026-01-026|Delegation Matrix]] - Authority levels

## Planning

**Timeframes**
- [[2026-01-030|Quarterly OKRs]] - 90-day objectives
- [[2026-01-031|Annual Strategy]] - Yearly planning
- [[2026-01-032|3-Year Vision]] - Long-term direction

## Related Maps
- [[MAP-leadership-practices]]
- [[MAP-execution-patterns]]
- [[MAP-team-dynamics]]

---
*Auto-updated: 2026-01-15*

Pattern 3: Synthesis Note from Pattern Detection

---
id: SYNTH-2026-Q1
type: synthesis
period: 2026-Q1
tags: [synthesis, patterns, insights]
created: 2026-03-31
---

# Q1 2026 Pattern Synthesis

Agent-extracted patterns from 47 notes created this quarter.

## Emerging Patterns

### 1. Decision-Making Under Uncertainty
**Frequency**: 12 references across 8 projects
**Pattern**: Teams default to analysis paralysis when facing high uncertainty

**Key Insights**:
- [[2026-01-001|Pre-mortems]] reduce time-to-decision by ~40%
- [[2026-01-020|Two-way door thinking]] enables faster reversible decisions
- [[2026-02-015|Small bet portfolios]] outperform single big bets

**Recommendation**:
Create playbook combining pre-mortems + two-way doors + portfolio approach

**Related Notes**: [[2026-01-001]], [[2026-01-020]], [[2026-02-015]], [[2026-02-018]]

### 2. Remote Team Dynamics
**Frequency**: 8 references across 4 organizations
**Pattern**: Async communication clarity directly correlates with execution velocity

**Key Insights**:
- Written decision logs reduce confusion by ~60%
- Daily async standups > weekly sync meetings for distributed teams
- Explicit context sharing reduces back-and-forth by 50%

**Playbook Created**: [[PLAY-remote-async-excellence]]

**Related Notes**: [[2026-01-042]], [[2026-02-008]], [[2026-02-033]]

## Cross-Organization Learnings

### Successful Practices Reapplied
1. **Weekly Review Cadence** (Personal → Company X → Company Y)
   - Adopted across 3 orgs with 95%+ consistency
   - Average 2.5 hours saved per week per leader

2. **Context Library Structure** (Company X → Personal)
   - Reduced context-switching friction
   - Knowledge retrieval time: 5 min → 30 sec

### Failed Experiments
1. **Daily Deep Work Blocks** - Worked for 2/5 contexts
   - Success factors: Control over calendar, team timezone alignment
   - Document learnings: [[2026-03-010]]

## Recommended Actions

1. **Create Playbooks**
   - [ ] Decision-making under uncertainty playbook
   - [ ] Remote async excellence playbook
   - [ ] Context switching optimization playbook

2. **Prune Knowledge**
   - [ ] Archive 5 obsolete meeting notes from Dec 2025
   - [ ] Consolidate 3 overlapping framework notes

3. **Fill Gaps**
   - [ ] Document hiring process patterns
   - [ ] Create board communication templates

---
*Generated by synthesis-agent on 2026-03-31*
*Review scheduled: 2026-04-15*

Pattern 4: Index Note (Entry Point)

---
id: INDEX-00
type: index
tags: [index, navigation, start-here]
created: 2026-01-12
updated: 2026-03-31
---

# Context Library Index

**Start here** for navigating this organization's knowledge base.

## Quick Access

### Most Referenced
1. [[2026-01-001|Pre-Mortem Analysis]] (47 references)
2. [[2026-01-020|One-Way vs Two-Way Doors]] (33 references)
3. [[PLAY-weekly-review|Weekly Review Playbook]] (28 references)

### Recently Updated
- [[2026-03-025|Q1 Board Update Template]] (2026-03-30)
- [[SYNTH-2026-Q1|Q1 Pattern Synthesis]] (2026-03-31)
- [[2026-03-015|Remote Team Hiring]] (2026-03-28)

### By Topic

#### Strategy & Planning
- [[MAP-strategic-frameworks|Strategic Frameworks Map]]
- [[MAP-okr-system|OKR System Map]]
- [[MAP-quarterly-planning|Quarterly Planning Map]]

#### Operations & Execution
- [[MAP-execution-patterns|Execution Patterns Map]]
- [[MAP-meeting-formats|Meeting Formats Map]]
- [[MAP-delegation-system|Delegation System Map]]

#### People & Culture
- [[MAP-leadership-practices|Leadership Practices Map]]
- [[MAP-hiring-system|Hiring System Map]]
- [[MAP-team-dynamics|Team Dynamics Map]]

#### Knowledge Management
- [[how-to-use-context-library|How to Use This Library]]
- [[context-library-maintenance|Maintenance Guidelines]]
- [[cross-referencing-guide|Cross-Referencing Guide]]

## Statistics

- **Total Notes**: 127
- **Atomic Notes**: 89
- **Map Notes**: 12
- **Synthesis Notes**: 4
- **Playbooks**: 22
- **Orphaned Notes**: 2 (see [[maintenance-log]])

## Archive
- [[archive/2025-Q4|2025 Q4 Archive]]
- [[archive/2025-Q3|2025 Q3 Archive]]

---
*Auto-updated by maintenance-agent*
*Last update: 2026-03-31*

Cross-Referencing Strategies

Manual Cross-Referencing

# When creating a new note
1. Identify 3-5 related existing notes
2. Add forward references in "Related" section
3. Add backlink comments in related notes

# Example addition to existing note:
# Related: [[2026-03-045|New AI Strategy Note]] - extends this framework

Automated Cross-Referencing

# Maintenance agent adds backlinks automatically
def add_backlinks(new_note_id, referenced_notes):
    """Add backlink section to referenced notes."""
    for ref_note in referenced_notes:
        backlink = f"\n## Backlinks\n- [[{new_note_id}]]"
        append_to_note(ref_note, backlink)

Semantic Clustering

# Maintenance agent groups notes by semantic similarity
clusters:
  - name: "decision-frameworks"
    notes: [2026-01-001, 2026-01-020, 2026-01-021, 2026-02-015]
    similarity_threshold: 0.75

  - name: "remote-work"
    notes: [2026-01-042, 2026-02-008, 2026-02-033]
    similarity_threshold: 0.80

Knowledge Extraction from Conversations

Post-Conversation Processing

# After each work session
1. Review conversation for extractable insights
2. Identify: decisions, frameworks, patterns, learnings
3. Create atomic notes for significant insights
4. Link to relevant existing notes
5. Update index if new topics emerged

# Example extraction
Conversation insight: "We decided to use two-week sprints with async planning"
→ Creates: [[2026-03-050|Sprint Cadence Decision]]
→ Links to: [[2026-02-020|Agile Practices]], [[PLAY-remote-async-excellence]]
→ Updates: [[MAP-execution-patterns]]

Git Hook Integration

# .git/hooks/post-commit
#!/bin/bash
# Automatically extract insights from commits

COMMIT_MSG=$(git log -1 --pretty=%B)

# Check if commit contains extractable knowledge
if [[ $COMMIT_MSG =~ "Decision:" ]] || [[ $COMMIT_MSG =~ "Insight:" ]]; then
    # Trigger extraction agent
    kaaos extract-from-commit HEAD
fi

Context Library Maintenance

Daily Maintenance (Automated)

tasks:
  - validate_links:
      check: broken references
      action: log and report

  - update_backlinks:
      scan: new notes created today
      action: add backlinks to referenced notes

  - detect_orphans:
      threshold: 0 references
      action: flag for review

Weekly Maintenance (Semi-Automated)

tasks:
  - semantic_clustering:
      min_cluster_size: 3
      similarity_threshold: 0.75
      action: suggest new map notes

  - pattern_detection:
      window: past 7 days
      min_frequency: 3
      action: suggest synthesis notes

  - pruning_candidates:
      criteria: not_accessed_90_days AND outdated
      action: suggest archival

Monthly Maintenance (Human + Agent)

tasks:
  - comprehensive_synthesis:
      agent: synthesis-agent
      scope: month
      output: synthesis note

  - knowledge_gaps:
      agent: gap-detector
      check: missing documentation
      output: gap report

  - structure_optimization:
      review: folder structure
      suggest: reorganization if needed

Migration Strategies

From Existing Tools

From Notion:

# Export Notion workspace to Markdown
# Run migration script
python migrate_notion.py \
  --input ~/Downloads/notion-export \
  --output ~/kaaos-knowledge/organizations/company-x \
  --preserve-links \
  --create-index

# Post-migration cleanup
# 1. Review auto-generated atomic notes
# 2. Add cross-references where Notion links existed
# 3. Create map notes for major sections
# 4. Run maintenance agent to validate structure

From Obsidian:

# Obsidian uses markdown, simpler migration
cp -r ~/Obsidian-Vault/* ~/kaaos-knowledge/organizations/personal/context-library/

# Standardize frontmatter
python standardize_frontmatter.py \
  --path ~/kaaos-knowledge/organizations/personal

# Generate index
kaaos maintenance --generate-index

From Email/Slack/Docs:

# Extract knowledge from communication tools
kaaos extract \
  --source gmail \
  --date-range 2025-01-01:2025-12-31 \
  --filter "from:ceo OR from:board" \
  --extract-decisions

# Review extracted notes
# Agent creates drafts, human reviews and approves

Best Practices

Atomic Notes: Keep notes focused on single concepts
Rich Links: Add context to references, not just IDs
Bidirectional: Always create backlinks
Progressive: Start with summary, link to details
Timestamped: Track creation and updates
Tagged: Use consistent tagging taxonomy
Maintained: Regular automated + human review
Versioned: Git tracks all changes

Common Pitfalls

Over-Structuring: Don't create complex taxonomies upfront
Under-Linking: Isolated notes lose value
Duplicate Notes: Use search before creating new notes
Stale Content: Set up automated staleness detection
Missing Context: Always explain "why" this note matters
Tool Obsession: Focus on content, not perfect tooling

Resources

references/context-library-patterns.md: Detailed architectural patterns
references/cross-referencing-system.md: Advanced linking strategies
references/knowledge-extraction.md: Automated extraction techniques
references/maintenance-workflows.md: Ongoing maintenance processes
assets/context-library-template.md: Ready-to-use template
assets/atomic-note-template.md: Atomic note structure
assets/map-note-template.md: Map note structure
assets/migration-scripts/: Tool migration scripts

knowledge-management

SKILL.md