Feature: Cross-project knowledge sharing for docs/solutions/
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- developer-experience
Research direction
Start by reading the learnings-researcher entry point and the ce:compound pipeline that creates and searches docs/solutions/. Compare the proposed configurable paths, import/export, and global directory approaches, then identify how external results should be tagged and adapted. Done means cross-project solutions are discoverable through a defined approach; the issue does not specify files or tests.
Written by the indexing model from the issue text.
Description
Summary
The ce:compound → docs/solutions/ → learnings-researcher → ce:plan/ce:review pipeline builds a valuable knowledge store per repo. But learnings from one project are invisible when working in another project. The learnings-researcher only searches the current repo's docs/solutions/.
For users who work across multiple related projects (e.g., multiple Obsidian vaults with similar agent/skill workflows, a main app + supporting repos, or a monorepo user who splits into multiple repos), lessons learned in one project should be discoverable in the others.
Use Case
I maintain multiple Obsidian vaults with Claude Code skills. Over 40+ documented solutions in one vault cover patterns like:
- Agent/skill design (gate language, delegation, compliance)
- MCP integration patterns (KanBox, Slack, email)
- Token optimization (CLI bypass, subagent delegation, batch pre-computation)
- Enrichment workflow patterns
When I start a new vault or work in a different codebase with similar patterns, none of these learnings are discoverable. The learnings-researcher searches only the local docs/solutions/, finds nothing, and the agent starts from scratch.
Current Workarounds
| Approach | Limitation |
|---|---|
Symlink docs/solutions/ from another repo |
learnings-researcher only searches docs/solutions/, not docs/shared-solutions/ or other paths |
| Copy files on project init | Snapshot in time — diverges immediately, no sync |
User-level ~/.claude/CLAUDE.md with path hint |
Fragile — depends on agent choosing to read an external path |
Symlinked .claude/rules/ |
Rules are loaded into every conversation (context cost), no structured search via frontmatter |
None of these integrate with the compound pipeline — the learnings-researcher doesn't know to look outside docs/solutions/.
Suggested Approaches
Option A: Configurable solutions_paths (lightweight)
Allow AGENTS.md (or CLAUDE.md) to declare additional solution directories the learnings-researcher should search:
# In AGENTS.md or a plugin config
solutions_paths:
- docs/solutions/ # local (default)
- ~/src/other-project/docs/solutions/ # cross-project
The learnings-researcher searches all listed paths. Results from external paths are tagged with their source so the agent knows they may need adaptation.
Option B: ce:compound-export / ce:compound-import (curated)
ce:compound-export— Curate a subset ofdocs/solutions/into a portable bundle (strip repo-specific file paths, keep patterns and guidance)ce:compound-import— Import a bundle into a new project'sdocs/solutions/, adapting references to the local codebase
This is more work but produces cleaner cross-project docs since repo-specific details (file paths, component names) are adapted.
Option C: Global solutions directory (simple)
Support a user-level ~/docs/solutions/ (or configurable path) that the learnings-researcher always searches in addition to the local docs/solutions/. Users manually symlink or copy their most portable learnings there.
Related Issues
- #111 — Project scaffolding for
docs/solutions/(same theme: bootstrapping the knowledge store) - #171 — Closed-loop self-improvement (proposed knowledge seeding, but repo-local)
Impact
Without cross-project sharing, the compound philosophy ("each unit of work makes subsequent units easier") resets to zero at project boundaries. The first project compounds knowledge beautifully; the second project starts from scratch even when the same user has already solved similar problems.
- Dominant language
- TypeScript
- Stars
- 25.6k
- Forks
- 2.1k
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 170
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EveryInc/compound-engineering-plugin
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EveryInc/compound-engineering-plugin#2085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
EveryInc/compound-engineering-plugin#795 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 80/100
EveryInc/compound-engineering-plugin#2084 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2083 ·
Maintainers usually reply within 1 day
-
Host support: DeepSeek Harness (dsh)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2072 ·
Maintainers usually reply within 1 day
All issues in EveryInc/compound-engineering-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
hurttlocker/o8#6535 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
area: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
snapotter-hq/SnapOtter#4856 ·
Maintainers usually reply within 1 day
-
bug follow-up
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spellshift/realm#2509 ·
Maintainers usually reply within 1 day