How do I install the Develop Like Every skill?

Run npx skillmds@latest add marcusrbrown/develop-like-every in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Develop Like Every safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Develop Like Every?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Develop Like Every free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Develop Like Every?

marcusrbrown (@marcusrbrown) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Develop Like Every by marcusrbrown — Agent Skill

Name: Develop Like Every
Author: marcusrbrown

Develop Like Every

Develop the way Every (the company) does: compound engineering, plan-first 80/20, boring Rails under aggressive AI leverage. Use when the user wants Every-style engineering decisions, code review in Every's voice, or asks to "develop like Every". Profiled 2026-07-11 from public sources.

marcusrbrown 90f0e1e 5 files · 8.0 KB Updated Sep 17, 2026

File contents

Develop like Every

Profiled as of 2026-07-11 · consent tier: self-published · full bibliography in references/sources.md. Cultures drift — if this is more than ~6 months old, re-run /dev-like every to refresh.

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].

Principles

Plan-first, 80/20 — most effort before code [guide]
Compound every unit of work into reusable repo knowledge [CEP]
Simplify as an explicit pipeline step, not an afterthought [CEP]
One person + agents ≈ a team; design workflows for that ratio [podcast transcript]
Boring stack, radical process [SF Ruby keynote]
Agent-native parity — if a human can run tests, read logs, or open a PR, the agent should be able to as well [guide]
Safety nets over gatekeeping — trust comes from tests, automated review, monitoring, and rollback, not line-by-line babysitting [guide]
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]

Workflow

Execute these checkpoints before and during the task. Treat them as required actions, not background description:

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].

See references/stack.md for the stack and references/workflow.md for workflow detail.

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.

Want a reviewer/pair persona in Every's voice? See personas/every-developer.md — it's reference material. Claude Code users can copy it to .claude/agents/ to run it as a first-class subagent; other harnesses may need their own harness-specific metadata.

---name: develop-like-everydescription: Develop the way Every (the company) does: compound engineering, plan-first 80/20, boring Rails under aggressive AI leverage. Use when the user wants Every-style engineering decisions, code review in Every's voice, or asks to "develop like Every". Profiled 2026-07-11 from public sources.license: MIT---# Develop like Every> Profiled as of 2026-07-11 · consent tier: self-published · full bibliography in [references/sources.md](references/sources.md). Cultures drift — if this is more than ~6 months old, re-run `/dev-like every` to refresh.## Core principle"Each unit of engineering work should make subsequent units easier — not harder"[[CEP README]](https://github.com/EveryInc/compound-engineering-plugin). Roughly 80% of effortgoes to planning and review, 20% to execution[[guide]](https://every.to/guides/compound-engineering).## Principles1. Plan-first, 80/20 — most effort before code [[guide]](https://every.to/guides/compound-engineering)2. Compound every unit of work into reusable repo knowledge [[CEP]](https://github.com/EveryInc/compound-engineering-plugin)3. Simplify as an explicit pipeline step, not an afterthought [[CEP]](https://github.com/EveryInc/compound-engineering-plugin)4. One person + agents ≈ a team; design workflows for that ratio [[podcast transcript]](https://every.to/podcast/transcript-how-two-engineers-ship-like-a-team-of-15-with-ai-agents)5. Boring stack, radical process [[SF Ruby keynote]](https://sfruby.com/)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]](https://every.to/guides/compound-engineering)7. Safety nets over gatekeeping — trust comes from tests, automated review, monitoring, and rollback, not line-by-line babysitting [[guide]](https://every.to/guides/compound-engineering)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]](https://github.com/EveryInc/compound-engineering-plugin/blob/main/skills/ce-compound-refresh/SKILL.md)## WorkflowExecute these checkpoints before and during the task. Treat them as required actions, notbackground description:Run the six-step loop: **brainstorm → plan → work → simplify → review → compound**[[CEP]](https://github.com/EveryInc/compound-engineering-plugin). Use the four-beat core cycle— **plan → work → review → compound → repeat** — and keep `simplify` as the extra gate theplugin inserts [[guide]](https://every.to/guides/compound-engineering). 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]](https://github.com/EveryInc/compound-engineering-plugin/blob/main/docs/skills/ce-compound.md).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]](https://github.com/EveryInc/compound-engineering-plugin).See [references/stack.md](references/stack.md) for the stack and [references/workflow.md](references/workflow.md) for workflow detail.## 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.Want a reviewer/pair persona in Every's voice? See [personas/every-developer.md](personas/every-developer.md) — it's reference material. Claude Code users can copy it to `.claude/agents/` to run it as a first-class subagent; other harnesses may need their own harness-specific metadata.

Frequently asked questions