Compound-engineering-plugin Alternatives

compound-engineering-plugin reviews and mentions

• Ask HN: Are you using Spec Driven Development?
  4 projects | news.ycombinator.com | 12 Jun 2026

  I use https://github.com/EveryInc/compound-engineering-plugin/blob... from https://every.to.

  Here's a readup on it: https://every.to/guides/compound-engineering

• I'm tired of LLM skill slop, so I built mine with regression tests
  2 projects | news.ycombinator.com | 8 Jun 2026

  Claude skills made by other people are typically useless. The exceptions I have found are https://github.com/EveryInc/compound-engineering-plugin which was like an early brainstorm -> plan -> write -> embed knowledge and best practices. Which is a common workflow now.

  I've recently experimented with more lightweight things like https://github.com/mattpocock/skills which are good.

  Most work is just the same 'ask questions step by step to define a spec' , 'make a plan', 'implement using TDD'

• I built a Claude Code plugin that argues with me about architecture. Then it caught me lying to it.
  2 projects | dev.to | 8 May 2026

  archforge is one attempt at the second framing. Pairs naturally with Compound Engineering — CE handles feature-level workflow (Brainstorm → Plan → Work → Review → Compound), archforge handles architectural decisions (Discover → Research → Design → Decide → Document → Review). Architectural decisions feed into CE plans by ADR number; CE compound learnings can produce new ADRs. The integration is materialized by running /archforge:remember-compound-integration once per project.

• CLAUDE.md is not a prompt: starting a Django side project with an agentic AI workflow
  3 projects | dev.to | 8 May 2026

  There's one more piece I'm experimenting with: compound engineering, a philosophy described by Kieran Klaassen and the team at Every in their guide. The core idea is that every unit of engineering work should make subsequent work easier, not harder. Most codebases get worse over time because each feature negotiates with the old ones; compound engineering flips this — features and fixes teach the system new capabilities, and the codebase compounds instead of decaying.

• Superpowers vs Compound Engineering: is the 'vs' even real?
  2 projects | dev.to | 4 May 2026

  Compound Engineering by Every — a 36-skill, 50-agent framework around the idea that "each unit of engineering work should make the next one easier", ~16k stars. Both ship as Claude Code plugins. Both wrap roughly the same surface — brainstorm, plan, work, review. Both have evangelists writing "I 100x'd my output" posts. So the natural question gets asked a lot: which one wins?

• Building WeRemember in Public — Day 1: Django project setup
  1 project | dev.to | 29 Apr 2026

  This was also the first issue closed using Compound Engineering — a workflow built around a Plan → Work → Review → Compound loop.

• Garry Tan's Claude Code Setup
  3 projects | news.ycombinator.com | 17 Mar 2026

  Check out the strats from the Every team: https://github.com/EveryInc/compound-engineering-plugin (I recommend just learning from their builds and doing your own!)

  Simon Willison's blog: https://simonwillison.net/guides/agentic-engineering-pattern...

• Show HN: Praxis, my personal take on Compound Engineering with AI
  2 projects | news.ycombinator.com | 24 Feb 2026

  Hey HN! I really enjoy Every's approach to Compound Engineering (https://every.to/guides/compound-engineering), but their plugin is tightly tied to their project (Cora) and stack (Ruby/Rails). I also found the files too big, and they used more context window than what I would like for my personal use.

  So, with the help of Amp Code CLI, I've built my own take on the compound engineering workflow. I tried to keep it agnostic to project stacks and as efficient as possible, so the context window could be used in the best way. I also wanted it to be extendable (for example, just drop your own subagents for review that are specific to your project). I also wanted to be easy to set up and update, so I made a simple CLI tool that keeps track of files in the `.agents` directory, updates when new versions are found in the repository, and displays a diff in the terminal before overwriting any customisations.

  I feel this matches well with my personal preferences when working with AI agents, but I would love to have feedback from more people.

• Compound Engineering: The AI-native engineering philosophy
  1 project | news.ycombinator.com | 15 Feb 2026
• Claude Code's new hidden feature: Swarms
  13 projects | news.ycombinator.com | 24 Jan 2026

  Have you tried the compound engineering plugin? [^1]

  My workflow with it is usually brainstorm -> lfg (planning) -> clear context -> lfg (giving it the produced plan to work on) -> compound if it didn’t on its own.

  [^1]: https://github.com/EveryInc/compound-engineering-plugin

• A note from our sponsor - SaaSHub
  www.saashub.com | 13 Jun 2026

  SaaSHub helps you find the best software and product alternatives Learn more →