EveryInc/compound-engineering-plugin

I use https://github.com/EveryInc/compound-engineering-plugin/blob/main/plugins/compound-engineering/README.md from https://every.to . Here's a readup on it: https://every.to/guides/compound-engineering

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'

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

I think there is some good middle ground between spec driven development and iterations, like Compound Engineering. https://github.com/EveryInc/compound-engineering-plugin

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-patterns/