Feature: Cross-project knowledge sharing for docs/solutions/

Abierto
#494 4 comentarios 3 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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 of docs/solutions/ into a portable bundle (strip repo-specific file paths, keep patterns and guidance)
  • ce:compound-import — Import a bundle into a new project's docs/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.

Lenguaje dominante
TypeScript
Estrellas
25.6k
Forks
2.1k
Merge medio
3 h 57 min
PR fusionados (30 d)
170

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de EveryInc/compound-engineering-plugin

Todos los issues de EveryInc/compound-engineering-plugin

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.