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

Open
#186 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
TypeScript
Stars
25.6k
Forks
2.1k
Avg merge
3h 57m
Merged PRs (30d)
170

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EveryInc/compound-engineering-plugin

All issues in EveryInc/compound-engineering-plugin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.