/knowledge-consolidation

name: knowledge-consolidation
description: Build frameworks from scattered insights across all braindumps and notes
roles: [all]
integrations: []

COG Knowledge Consolidation Skill

Purpose

Transform scattered insights from braindumps, daily briefs, and check-ins into coherent frameworks and "single source of truth" knowledge documents through pattern recognition and systematic synthesis.

When to Invoke

• User wants to consolidate their insights
• User says "consolidate knowledge", "build frameworks", "synthesize insights"
• Time for periodic knowledge base maintenance (weekly, monthly, quarterly)
• User wants to extract patterns from accumulated braindumps
• Before major decisions that could benefit from framework consultation

Agent Mode Awareness

**Check `agent_mode` in `00-inbox/MY-PROFILE.md` frontmatter:**

• If `agent_mode: team` — delegate scanning and pattern extraction to parallel sub-agents (e.g., one per domain: personal braindumps, professional braindumps, project-specific content, daily briefs). Each agent identifies themes and patterns, then a synthesis agent combines findings into frameworks.
• If `agent_mode: solo` (default) — handle all scanning, pattern recognition, and framework building directly. No delegation.

Pre-Flight Check

**Get current timestamp (REQUIRED before generating any files):**

1. Run `date '+%Y-%m-%d %H:%M'` using Bash to get the actual current date and time 2. Store this value and use it for the `created:` frontmatter field 3. NEVER guess or fabricate the time — always use the value returned by the `date` command

Process Flow

1. Data Gathering

**Scan vault for unprocessed or partially processed content:**

• All braindumps since last consolidation:
• `02-personal/braindumps/`
• `03-professional/braindumps/`
• `04-projects/*/braindumps/`
• `00-inbox/braindump-*.md` (mixed domain)

• Daily briefs and check-ins:
• `01-daily/briefs/`
• `01-daily/checkins/`

• Any meeting transcripts or project documents in:
• `04-projects/*/planning/`
• `04-projects/*/resources/`

**Determine scope:**

• Ask user: "What time period should I analyze? (last week, last month, last quarter, all time, or custom range?)"
• Identify unprocessed content (check for `status: "captured"` or missing consolidation metadata)

**Gather statistics:**

• Total documents to analyze
• Breakdown by domain and type
• Date range coverage

2. Pattern Recognition

Apply systematic pattern detection across all content:

Frequency Analysis

**What comes up repeatedly?**

• Identify themes mentioned across multiple documents
• Track topic frequency and clustering
• Recognize persistent questions or concerns
• Spot recurring action items or decisions

Temporal Clustering

**What insights emerged together?**

• Group related insights by time period
• Identify how thinking evolved over time
• Recognize inflection points where thinking shifted
• Map catalysts that triggered changes

Domain Correlation

**What patterns cross domains?**

• Personal insights affecting professional thinking
• Professional learnings applied to projects
• Project experiences informing personal growth
• Strategic themes spanning all domains

Contradiction Analysis

**Where does thinking conflict?**

• Identify contradictory thoughts or approaches
• Recognize evolution vs. inconsistency
• Understand resolution or ongoing tension
• Track perspective shifts over time

Cross-Cutting Patterns

**Meta-patterns across all dimensions:**

• Decision-making approaches
• Problem-solving strategies
• Learning patterns
• Emotional/energy patterns
• Relationship patterns
• Creative processes

3. Framework Development

Synthesize patterns into actionable frameworks:

Identify Core Principles

**From scattered insights to fundamental truths:**

• What patterns reveal deeper principles?
• What rules or heuristics emerge?
• What mental models are forming?
• What strategies are proving effective?

Test Against Evidence

**Validate frameworks with source material:**

• Do source insights support these principles?
• Are there counter-examples or exceptions?
• How confident can we be in this framework?
• What are the boundary conditions?

Define Boundaries

**When does framework apply/not apply?**

• What contexts does this framework serve?
• What are its limitations?
• When should it NOT be used?
• What assumptions does it rely on?

Create Applications

**How to use this framework:**

• Specific use cases
• Decision-making applications
• Problem-solving templates
• Practical implementation steps

4. Knowledge Integration

Update and create knowledge base documents:

Update Existing Frameworks

For each framework that needs updating, use the consolidated-knowledge template in `references/templates.md`.

Save to: `05-knowledge/consolidated/[framework-name]-framework.md`

Create New Frameworks

For newly identified frameworks, use the new-framework template in `references/templates.md`.

Save to: `05-knowledge/consolidated/[framework-name]-framework.md`

Update Pattern Documentation

Document the pattern using the pattern template in `references/templates.md`.

Save to: `05-knowledge/patterns/pattern-[name].md`

Create Timeline Entries

Build the timeline entry using the thinking-evolution template in `references/templates.md`.

Save to: `05-knowledge/timeline/[topic]-evolution-YYYY-MM.md`

5. Generate Consolidation Report

Create the master consolidation document using the report template in `references/templates.md`.

Save to: `05-knowledge/consolidated/consolidation-YYYY-MM-DD.md`

6. Cleanup and Archival

**Mark processed braindumps:** Update frontmatter in processed braindumps:

status: "consolidated"
consolidated_in: "[[consolidation-YYYY-MM-DD]]"
consolidated_date: "YYYY-MM-DD"

**Archive outdated content:** Move superseded frameworks or insights to: `00-inbox/archive/[filename]-archived-YYYY-MM-DD.md`

Add note exp