GenAI PM
concept4 mentions· Updated Jul 10, 2026

Compound Engineering

A plugin/pattern used to manage build loops and goal-driven agent workflows. Here it is tied to Codex Desktop and the LFG loop for prototype completion.

Key Highlights

  • Compound Engineering turns one-off agent runs into reusable operational knowledge that improves future AI performance.
  • Its common pattern is a structured loop such as plan, work, assess, and codify rather than ad hoc prompting.
  • Newsletter examples connect it to Claude Code, Codex Desktop, and the LFG loop for faster prototype completion.
  • The concept is especially useful for AI PMs who want repeatable agent workflows and stronger team memory.
  • Real examples include building Printing Press, updating Agent Cookie, and advancing the Turnaround prototype.

At a glance

Category
Developer Tool

Compound Engineering

Overview

Compound Engineering is a concept and workflow pattern for improving AI-assisted building over time by turning each agent run into reusable operational knowledge. In the newsletter coverage, it appears both as a philosophy—capturing prompt lessons, decisions, and working patterns so future agent sessions perform better—and as a practical plugin/command system used in tools like Claude Code CLI and Codex Desktop. Its core idea is that agent output should not be treated as one-off work; instead, teams should codify successful plans, execution steps, assessments, and fixes so the system compounds in effectiveness.

For AI Product Managers, Compound Engineering matters because it offers a structured way to make agentic workflows more reliable, faster, and more repeatable. Rather than relying on ad hoc prompting, it introduces loops such as plan → work → assess → codify, or goal-driven build loops like LFG, that help agents execute against clear objectives while preserving learnings. This makes prototyping, iteration, and internal tool creation more scalable—especially when non-technical or semi-technical operators are coordinating multiple AI systems.

Key Developments

  • 2026-01-11: Jason Shuman's conversation with Dan Shipper frames “compound engineering” as a principle for AI-native organizations: capturing prompt lessons so AI agents improve over time, alongside broader themes like orchestration and the rise of generalists.
  • 2026-02-09: Kieran Klaassen demonstrates a Compound Engineering plugin for Claude Code CLI, using slash-command workflows such as plan, work, assess, and triage to run an iterative planning–coding–assessing–codifying loop. The system stores learnings in local documentation and updates root guidance files so future runs inherit prior lessons.
  • 2026-06-15: Matt Van Horn applies Compound Engineering’s `/c plan` and `/c work` loop to autonomously generate execution plans, reverse-engineer private web APIs via HAR sniffing, and build SQLite-backed CLIs and agent skills such as Printing Press and Agent Cookie with minimal manual code inspection.
  • 2026-07-10: Compound Engineering is cited as the workflow behind a Codex Desktop build session where the LFG loop and goal command helped push the Turnaround prototype—a maintenance-status badge—to roughly 70% completion in a single session.

Relevance to AI PMs

1. Standardizes agent execution for product work. AI PMs can use Compound Engineering-style loops to reduce prompt randomness in prototyping, bug fixing, and feature delivery. A structured plan/work/assess cycle makes outcomes easier to review and delegate.

2. Creates institutional memory for AI workflows. By storing architecture decisions, reusable solutions, and prompt learnings in shared docs, PMs can help teams avoid repeating mistakes and improve agent performance across future tasks.

3. Enables faster validation by non-engineers. The examples show semi-technical builders using command-based workflows to produce prototypes, CLIs, and agent skills quickly. For PMs, this means faster concept testing before allocating full engineering resources.

Related

  • Claude Code: An early environment where Compound Engineering appeared as a plugin-driven workflow using slash commands for planning, coding, and assessment.
  • Codex Desktop: A later environment where Compound Engineering is tied to goal-driven prototype completion, especially through the LFG loop.
  • LFG: A build loop associated with Compound Engineering in Codex Desktop, used to drive prototype progress toward a defined goal.
  • Kieran Klaassen: Demonstrated the plugin form of Compound Engineering and its documentation-centered improvement loop.
  • Matt Van Horn: Showed how Compound Engineering could be used by a non-traditional builder to automate planning and execution for complex agentic tasks.
  • Dan Shipper and Jason Shuman: Helped surface Compound Engineering as a broader organizational concept, not just a tooling pattern.
  • Printing Press: An example of a tool/skill built with Compound Engineering workflows.
  • Agent Cookie: Another example of a product updated and extended through the Compound Engineering loop.
  • Turnaround: A prototype cited as reaching substantial completion in a single build session using Compound Engineering with Codex Desktop.

Frequently asked questions

What is Compound Engineering?

A plugin/pattern used to manage build loops and goal-driven agent workflows. Here it is tied to Codex Desktop and the LFG loop for prototype completion.

What should AI product managers know about Compound Engineering?

Compound Engineering turns one-off agent runs into reusable operational knowledge that improves future AI performance. Its common pattern is a structured loop such as plan, work, assess, and codify rather than ad hoc prompting. Newsletter examples connect it to Claude Code, Codex Desktop, and the LFG loop for faster prototype completion.

Explore this topic

Newsletter Mentions (4)

2026-07-10
“Using the compound-engineering plugin’s LFG loop and Codex Desktop’s goal command, the Turnaround prototype—a maintenance-status badge—reached approximately 70% completion in a single build session.”

The newsletter uses compound-engineering as an example of a structured agentic build workflow.

2026-06-15
“Matt Van Horn uses Compound Engineering’s slash C plan/C work loop to autonomously generate step-by-step AI agent plans that reverse-engineer secret web APIs via HAR sniffing and build SQLite-backed CLIs and agent skills like Printing Press—all without manually reading code.”

#5 ▶️ How This Non-Technical Founder Mastered Agentic Engineering in 50 Minutes | Matt Van Horn Peter Yang Matt Van Horn uses Compound Engineering’s slash C plan/C work loop to autonomously generate step-by-step AI agent plans that reverse-engineer secret web APIs via HAR sniffing and build SQLite-backed CLIs and agent skills like Printing Press—all without manually reading code. Compound Engineering’s `/c plan ` command writes a detailed execution plan to prevent agent laziness and `/c work` executes the plan; Matt used this loop to build and update his Agent Cookie tool in minutes without viewing the plan file. Printing Press ingests official CLIs/APIs, HAR-sniffs secret web APIs (e.g., Kayak Direct, Google Flights), incorporates GitHub community wrappers (e.g., Python Domino’s pizza API), and creates an SQLite database with power-user personas to generate a CLI plus Hermes, OpenClaw, Claude Code, and Codex agent skills—e.g., `pp flight goat` returns cheapest long-haul flights like London at $1,200 per passenger. Matt Van Horn authored last30days-skill (#1 trending on GitHub with 40K+ stars), ranks as the #5 human contributor to agent-browser and #3 to Paperclip CLI, and merged a feature proposal into CPython with 739 views and 33 likes that suggests `print` for non-Python syntax.

2026-02-09
“Kieran Klaassen demonstrates his Compound Engineering plugin for Claude Code CLI, using slash commands like workflows plan, workflows work, assess, and triage to run a planning–coding–assessing–codifying loop that captures insights in a local docs directory and iteratively improves generated code.”

#4 ▶️ How to Make Claude Code Better Every Time You Use It (Full System) | Kieran Klaassen Peter Yang Kieran Klaassen demonstrates his Compound Engineering plugin for Claude Code CLI, using slash commands like workflows plan, workflows work, assess, and triage to run a planning–coding–assessing–codifying loop that captures insights in a local docs directory and iteratively improves generated code. The compound-engineering-plugin appends codified learnings as Markdown under /docs/architecture-decisions/ and /docs/solutions/ , and updates the root claude.md so those rules are injected into every new workflows plan prompt. With Opus 4.5 and Playwright, Claude Code auto-generates end-to-end browser tests—logging into Gmail to exercise email signature and draft flows, clicking UI elements, inspecting console logs, and screen-recording a video artifact attached to the pull request. By defining alias CC="claude code --dangerously-skip-permissions" , all interactive permission prompts are suppressed, enabling fully unattended AI-driven sessions for commands like plan, work, assess, and PR creation.

2026-01-11
“Jason Shuman’s conversation with Dan Shipper surfaces key principles for AI-native organizations: the shift from a knowledge economy to an “allocation economy” where orchestration of human and machine intelligence is paramount; the resurgence of generalists with strong taste and direction; and “compound engineering,” capturing prompt lessons to improve AI agents over time.”

Product Management Insights & Strategies Marc Baselga outlines three investor-selection filters for first-time founders: diversify checks among angels to build a supportive network; choose early backers who create positive signals for later rounds; and avoid detractors by backchanneling with founders of failed ventures—ensuring investors add strategic value beyond capital. Jason Shuman’s conversation with Dan Shipper surfaces key principles for AI-native organizations: the shift from a knowledge economy to an “allocation economy” where orchestration of human and machine intelligence is paramount; the resurgence of generalists with strong taste and direction; and “compound engineering,” capturing prompt lessons to improve AI agents over time. AI Industry Developments & News Guillermo Rauch spotlights OpenAI’s GPT-5.2 Pro working with Harmonic to near-autonomously generate a proof for an Erdős mathematical problem—demonstrating how advanced language models are tackling complex reasoning tasks once reserved for human experts.

Stay updated on Compound Engineering

Get curated AI PM insights delivered daily — covering this and 1,000+ other sources.

Subscribe Free