knowledge-opslisted

# Knowledge Operations Manage a multi-layered knowledge system for ingesting, organizing, syncing, vectorizing, and retrieving knowledge across multiple stores. ## Usage Template **Prompt** ```text Use knowledge-ops to organize this knowledge base. Deduplicate, classify, sync, and prepare semantic retrieval. ``` **Use Case** - Scaling from a small wiki to a multi-layer knowledge system with search, memory, and vector storage. **Expected Result** - The agent proposes or runs organization, deduplication, vector sync, and retrieval steps. **Output Example** - A sync report listing indexed notes, duplicates, skipped files, merge candidates, and retrieval test queries. **Verification Case** - The output reports what was indexed, skipped, merged, or flagged for manual review. **Verified Effect** - A growing wiki becomes searchable, deduplicated, and ready for semantic retrieval. ## When to Use - User wants to "save this to my knowledge base" - Syncing knowledge across systems (wiki, memory, vector DB, git repos) - Deduplicating or organizing existing knowledge - User asks "what do I know about X?" (semantic search) - User says "sync", "organize", "deduplicate", "vectorize" - Knowledge base is growing beyond ~300 nodes and manual navigation is slowing down --- ## Knowledge Layers ### Layer 1: Active Execution Truth - GitHub issues, PRs, Linear tasks — current operational state - Rule: if it affects an active plan or release, put it here first ### Layer 2: Quick Access