knowledge-ops

Manage a multi-layered knowledge system for ingesting, organizing, syncing, and retrieving knowledge across multiple stores. Prefer the live workspace model: When new knowledge needs to be captured: What type of knowledge is it? Check if this knowledge already exists: Write to appropriate layer(s): Update any relevant indexes or summary files. Periodically sync conversation history into the knowledge base: Mirror important workspace configuration and scripts to the knowledge base: When the information affects active execution: Pull knowledge from multiple sources into one place: Before completing any knowledge operation: - code work lives in the real cloned repos - active execution context lives in GitHub, Linear, and repo-local working-context files - broader human-facing notes can live in a non-repo context/archive folder - durable cross-machine memory belongs in the knowledge base, not in a shadow repo workspace - User wants to save information to their knowledge base - Ingesting documents, conversations, or data into structured storage - Syncing knowledge across systems (local files, MCP memory, Supabase, Git repos) - Deduplicating or organizing existing knowledge - User says "save this to KB", "sync knowledge", "what do I know about X", "ingest this", "update the knowledge base" - Any knowledge management task beyond simple memory recall - Sources: GitHub issues, PRs,...