From compound-knowledge
Retrieves institutional knowledge from past YAML solution files for debugging, feature planning, error resolution, design decisions, and unfamiliar code exploration.
npx claudepluginhub joshuaoliphant/claude-plugins --plugin compound-knowledgeThis skill is limited to using the following tools:
Surface institutional knowledge from past solutions and engineering principles before starting work. Prevent repeated mistakes by searching YAML-frontmatter solution files captured by compound-capture.
Capture knowledge — solutions, context docs, learnings, and principles. Use after fixing non-trivial bugs, creating context for AI, or discovering patterns worth preserving. Triggers: compound, document solution, capture fix, save solution, knowledge compound, document this, save this fix, context, create context, update context, build context, learn, save learning, remember this.
Coordinates parallel subagents to document recently solved problems into searchable YAML-frontmatter Markdown files in docs/solutions/. Offers full research/cross-reference mode or lightweight single-pass.
Searches project memory via progressive filtering with MEMORY.md index and grep for task-relevant patterns before non-trivial work; stores structured problem-solution insights after completion.
Share bugs, ideas, or general feedback.
Surface institutional knowledge from past solutions and engineering principles before starting work. Prevent repeated mistakes by searching YAML-frontmatter solution files captured by compound-capture.
compound-knowledge:knowledge-researcher — Haiku-powered subagent that performs fast, parallel grep-based retrieval across solution files. Designed for speed (<30s).{project_root}/knowledge/solutions/~/.claude/compound-knowledge-registry.md. Enables searching other projects' knowledge bases when local results are thin.Resolve the solutions directory before any operation. First match wins:
{project_root}/.claude/compound-knowledge.local.md — extract solutions_path value~/.claude/compound-knowledge.local.md — extract solutions_path value{project_root}/knowledge/solutions/If the resolved directory does not exist:
"Solutions directory not found at
{solutions_path}. Run/compound-knowledge:setupto initialize it."
Load any stored feedback preferences before starting:
python ${PLUGIN_ROOT}/scripts/feedback_manager.py compound-knowledge show-feedback
If feedback entries exist, apply them:
Follow the Path Resolution algorithm from Context. Store as {solutions_path}.
Spawn the subagent for fast parallel search:
Agent(
subagent_type="compound-knowledge:knowledge-researcher",
model="haiku",
prompt="Search for solutions related to: {task_description}. Project: {project_name}. Keywords: {extracted_keywords}. Solutions path: {solutions_path}. Registry path: ~/.claude/compound-knowledge-registry.md",
description="Search past solutions"
)
The researcher reads the registry to identify other knowledge bases for cross-project search when primary results are thin (<3 hits).
The knowledge-researcher returns:
critical-patterns.mdSurface the top results to the user and incorporate insights into your approach:
A concise summary of relevant past solutions and principles, presented to the user with: