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

オープン
#186 コメント 4 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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分
マージ済み PR(30日)
170

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

EveryInc/compound-engineering-plugin のほかの issue

EveryInc/compound-engineering-plugin の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。