Feature: Cross-project knowledge sharing for docs/solutions/
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- TypeScript
- 星标
- 25.6k
- 派生
- 2.1k
- 平均合并
- 3 小时 57 分钟
- 30 天内合并 PR
- 170
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
EveryInc/compound-engineering-plugin 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
EveryInc/compound-engineering-plugin#2085 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
EveryInc/compound-engineering-plugin#795 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 80/100
EveryInc/compound-engineering-plugin#2084 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
EveryInc/compound-engineering-plugin#2083 ·
维护者通常 1 天内回复
-
Host support: DeepSeek Harness (dsh)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 3/5 1-2 天 新手友好度 48/100
EveryInc/compound-engineering-plugin#2072 ·
维护者通常 1 天内回复
查看 EveryInc/compound-engineering-plugin 的全部 Issue
相似的 Issue
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
难度 2/5 1-3 小时 新手友好度 72/100
elastic/kibana#306401 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
agentes-chat/agentes-chat#927 ·
维护者通常 1 天内回复
-
comp/desktop P2 type/bug
难度 2/5 1-3 小时 新手友好度 78/100
NousResearch/hermes-agent#157702 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
e2e-failure ready-to-code
难度 1/5 1 小时以内 新手友好度 72/100
redhat-developer/rhdh-plugin-export-overlays#4794 · 1 条评论 ·
维护者通常 1 天内回复