← All notes

Add a compound step

Try adding a Compound step to the end of your agent pipeline. You save the entire context window, then get another agent to review it along with the unstaged git changes, and save anything useful to AGENTS.md or a folder to reference later.

It's there so you don't hit the same issue again and again. Say logging into a browser keeps slowing down the coder because it gets stuck every time. The compound step can do something to automate that.

I also read that a Brainstorm step before planning can be good, so a pipeline looks like this, with each step being a separate agent:

Brainstorm -> Plan -> Implement -> Review -> Compound

For now I'm keeping it simple and just asking the agents to write to AGENTS.md what they struggled with and what the solution was.