Understanding how /workflows:compound captures learnings from sub-agent work

Abierto
#186 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
typescript

Línea de trabajo

Read the /workflows:compound and sub-agent workflow definitions in the repository to trace what context and artifacts they consume. Then inspect the relevant instructions for how agents report findings; compare them with the questions raised here. Done means documenting how context loss is handled and whether workflow changes or usage guidance are warranted.

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

Descripción

documentation

Context

I've started using the compound engineering workflow and I'm trying to understand how the compound step works in practice, specifically around sub-agent context and information retention.

What I'm trying to understand

When work happens through sub-agents (via /workflows:work, /lfg, /slfg), each sub-agent has its own context where it may try multiple approaches, hit dead ends, discover codebase quirks, and eventually succeed. The sub-agent then returns a summary to the orchestrator.

By the time /workflows:compound runs at the end, several things may have happened:

  1. Sub-agents compressed their experience into summaries, potentially dropping the failed attempts and unexpected discoveries that are arguably the most valuable things to compound
  2. Multiple sub-agent summaries have accumulated in the orchestrator's context, with early ones potentially losing weight as later tasks push them further back
  3. On longer task lists, compaction may have occurred at least once before the compound step runs, which could mean early sub-agent summaries are gone entirely — not just far back in context, but actually removed

Questions

  1. What does /workflows:compound actually read from? Does it work from the orchestrator's conversation context, the git diff, the PR, the plan file, or some combination?

  2. If it relies on the orchestrator's context, how does it handle the case where compaction has already occurred and early task summaries have been lost?

  3. Do sub-agents currently have any instructions to report failed approaches and unexpected discoveries, or are they primarily reporting outcomes?

  4. Is there a recommended task list size or session structure where the compound step works best? For example, should users be running compound more frequently on long feature branches rather than once at the end?

  5. Has the team observed cases where the compound step produced thin or low-value docs/solutions/ entries, and if so, was context loss a contributing factor?

  6. Would it make sense to compound at the sub-agent level — having each sub-agent capture learnings while its full context is still fresh, right after completing its task? If so, is there a recommended way to achieve this today, or would it require changes to the workflow?

I want to make sure I'm getting full value from the compound step rather than just going through the motions. Any insight into how this actually works under the hood would be really helpful.

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.