Every

Consent tier: self-published · Kind: org · Sources: 11 · Updated: 2026-07-11

Install: npx dev-like every

Prebuilt skill: SKILL.md

Identity

~15-person company running five products (Cora, Monologue, Sparkle, Spiral, every.to), each with roughly one-person engineering teams whose engineers “write virtually zero code” Lenny’s. Their practice is codified in the Compound Engineering Plugin (CEP), ~23k stars CEP.

Core principle

“Each unit of engineering work should make subsequent units easier — not harder” CEP README. Roughly 80% of effort goes to planning and review, 20% to execution guide.

Workflow shape

Run the six-step loop: brainstorm → plan → work → simplify → review → compound CEP. Use the four-beat core cycle — plan → work → review → compound → repeat — and keep simplify as the extra gate the plugin inserts guide. At the compound step (/ce-compound), write learnings to docs/solutions/ and use them to ground the next loop — make knowledge accrete in the repo, not in heads ce-compound. For the fully autonomous pipeline (/lfg), plan → work → review → PR → watch CI until green. Keep reviewer personas as skill-local prompt assets (29 skills, 0 standalone agents post-migration) CEP.

Stack

“Boring Rails”: Ruby on Rails + Turbo/Stimulus/ERB + Tailwind; RubyLLM, StepperMotor, Ahoy, pgvector for the AI layer (Cora) SF Ruby keynote. Boring, well-understood building blocks under aggressive AI leverage.

Principles (cited)

1. Plan-first, 80/20 — most effort before code guide
2. Compound every unit of work into reusable repo knowledge CEP
3. Simplify as an explicit pipeline step, not an afterthought CEP
4. One person + agents ≈ a team; design workflows for that ratio podcast transcript
5. Boring stack, radical process SF Ruby keynote
6. Agent-native parity — if a human can run tests, read logs, or open a PR, the agent should be able to as well guide
7. Safety nets over gatekeeping — trust comes from tests, automated review, monitoring, and rollback, not line-by-line babysitting guide
8. Make institutional knowledge discoverable — solved problems live in docs/solutions/, and instruction files must surface that store so future agents find it ce-compound-refresh

Tensions

• CEP’s layout migrated twice in ~6 months (agents folded into skills) — mimic the principles, expect the mechanics to drift.
• “Engineers write virtually zero code” is the honest ceiling of the claim; the punchier “100% AI-written” framing outruns the evidence. Repo history shows human review is the load-bearing step. Treat the ratio as directional.