# The Era of Compound Engineering — Kieran Klaassen, Every/Cora

Source: [AI Engineer](https://www.youtube.com/watch?v=_ehJyfHg1Vk)  
Feed7 permalink: https://feed7.dev/p/the-era-of-compound-engineering-kieran-klaassen-every-cora-053chml  
Published: 2026-08-20T15:00:06.000Z  
Trust: Source Linked (source_linked)

## Why Included

Compound engineering treats each agent mistake and product judgment as reusable context. The useful discipline is to invest in memory and review so the next feature becomes easier, not merely faster.

## Source Summary

Kieran Klaassen describes a solo loop for shipping Cora: brainstorm, plan, execute, review, polish, and compound the learning. His operating rule assigns **50% of the effort** to delivering the feature and **50%** to teaching the system what should improve next time.

## Practical Implication

Capture decisions, postmortems, product taste, and repeated corrections in agent-readable files or skills. Keep human judgment at the start and end of the loop, while letting agents handle implementation only after planning, tests, and review are dependable.

## Agent-Ready Context

Kieran Klaassen describes a solo loop for shipping Cora: brainstorm, plan, execute, review, polish, and compound the learning. His operating rule assigns **50% of the effort** to delivering the feature and **50%** to teaching the system what should improve next time.

Capture decisions, postmortems, product taste, and repeated corrections in agent-readable files or skills. Keep human judgment at the start and end of the loop, while letting agents handle implementation only after planning, tests, and review are dependable.

The claim that implementation is mostly solved comes from one builder's workflow, not comparative evidence. Long autonomous runs still depend on strong evaluation, and accumulated memory can become noise unless lessons remain specific, current, and retrievable.

## Connected Context

Feed7 judgment across 545 accumulated Signals:

This provides the operating philosophy behind compound-engineering toolkits: delivery is only half the work, while reviewed decisions and corrections become maintained input for later runs. It reinforces human judgment at planning and acceptance boundaries and narrows autonomy to workflows with dependable tests and review. Against broader skill systems, its key constraint is curation—memory must stay specific, current, retrievable, and evaluated rather than merely accumulate.

- [EveryInc/compound-engineering-plugin](https://feed7.dev/p/compound-engineering-plugin-06exf60) — The plugin turns Klaassen’s brainstorm-to-review loop and captured learning into a concrete, reusable six-stage repository workflow.
- [SkillProx: Self-Evolving Agent Skills via Proximal Textual Gradient Descent](https://feed7.dev/p/2608-07449v1-1co8km3) — SkillProx supplies measured retries, rollback, and pruning for the exact risk Klaassen identifies: accumulated lessons becoming noisy, stale, or harmful.
- [Coding Agents Don't Scale Themselves. Neither Do Your Teams. — Patrick Debois, Tessl](https://feed7.dev/p/coding-agents-don-t-scale-themselves-neither-do-your-teams-patrick-deboi-1tkeyjb) — Debois extends this solo compounding loop to organizations, where shared registries, evaluations, guardrails, and accountable platform owners are needed to maintain reusable context.
- [Prototyping as Leadership: How a CTO Ships with AI Agents — Hursh Agrawal, The Browser Company](https://feed7.dev/p/prototyping-as-leadership-how-a-cto-ships-with-ai-agents-hursh-agrawal-t-1f1csz2) — The leadership workflow reinforces Klaassen’s human-at-the-boundaries model through prepared context, bounded overnight execution, and personal testing and review before wider adoption.

## Context Map

- Layer: agent
- Domains: coding
- Topics: agent-memory, harness-engineering, skills

## Uncertainty

- The claim that implementation is mostly solved comes from one builder's workflow, not comparative evidence. Long autonomous runs still depend on strong evaluation, and accumulated memory can become noise unless lessons remain specific, current, and retrievable.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.