I don't want to turn this into an, oh look at mine.
It's just always been very behind the curve. I don't think you should use anyone's honestly. You should create your own shell base, and point to skills you find might add value, and add them. Then as you learn things about the shape of how things work, what you end up doing is rewriting them to follow your rules from what you learned.
What you'll find is, you'll have significantly better skills and systems.
It's great for feature development. It queries you about you intentions, creates a spec for you to review and modify, creates a plan for it to follow, then farms out the work to subagents.
Crap on it all you want, but it makes LLM work predictable.
It does not make LLM work predictable. Try it on the same type of project twice and see. You think you're saving time but youd accomplish similar results with 2 or 3 skills.
I think this depends a lot on two things: how well-defined your requirements are up front, and how well-defined the problem space/domain are.
If there's some clarity and structure with clear expectations, it seems to produce fairly reliable, consistent results, and the process of validating specs with Claude can yield all kinds of unexpected dead-ends or holes in the idea you had. I find this very helpful.
But I'm curious too, what are the skills you'd use instead? superpowers are just skills themselves.
How is an implementation spec that helps it author a plan to follow not considered predictable? What are these skills you are referring to specifically?
I'll correct myself. 1 Skill for helping refine your plan/spec with propositional yes/no questions. After that no more skills needed to emulate superpowers honestly. Workflows do the rest and claude will do that for you. ultracode is 90% of superpowers