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

未关闭
#186 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
typescript

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
25.6k
派生
2.1k
平均合并
3 小时 57 分钟
30 天内合并 PR
170

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

EveryInc/compound-engineering-plugin 的其他 Issue

查看 EveryInc/compound-engineering-plugin 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。