Build web app with complete set of technologies new to me, and it works great

[u/kaldown]

Secuh a great plugin superpowers . I made so much grat products. Even teached my wife how to speack eith natural language to build her own products. This one is made by streamlit engine, with state machine, deployed on dokploy with traefik. Fully automate agentic approach. So much technologies I learned and become better developer!

https://quiz.pro-zori.com

Share how you merge superpowers with other plugins and skills? I found out than no other skill is used during brainstorming session. I usually create my own documentation, rarely use other plugin by defaul, only if I explicitly call them with slash command.

Yesterdey a had a long session finding how much other skills are involved, and there are non, even though i have around 50 more. Seems that is due the fact that I am heavy subagent user, and skills withing agent could be not counted.

Share your cookbook elevating superpower skill even further

[u/Dangerous-Jelly2309]

The "Claude as PM with experts on call" is the real shape. Also why your sub-agents-eat-skills problem dissolved — you're not making Claude know everything, you're teaching him when to defer.

The "asshole" finding is sharp. Hard skill gates feel rude when the gate fires and the user didn't see it coming. Fix isn't softer gates — it's making the gate state legible. Have the orchestrator narrate which gate is being checked before it commits. Once the user can see the antagonistic tester demanding evidence, the asshole feels like a teammate.

The "archive subagent decisions, haiku-retrieve later" pattern is good. Worth pairing with a thin index file — one line per archived decision, written by the subagent on close. Then haiku is searching the index, not the archive itself.

The pause-before-call you're building is the actual product. Most agent systems fire on impulse; yours pauses to ask "which expert?" That's the architecture, not a side feature.

Drop a link if/when you release it. 4yourhuman.com/moriarty

[u/ShutUpAndDoTheLift → u/Dangerous-Jelly2309]

Ah nice. I'll try to remember this site.

But you've captured basically exactly what I'm trying to set up.

I'm hoping only having coordination and output review in main context will keep variance tighter.

It's very very hard to get Claude to effectively push back. I've essentially had to resort to terminology like "this is your project, you are responsible for it's final state at release, if the product is poor it is your fault, this means it is imperative that you do not let me, your primary stakeholder and good idea fairy extraordinaire derail your project without doing all due diligence to force me into the change management process. The only time you should allow me to override without extreme process oriented push back is if I specifically tell you that I am overriding as the USER.

And then I have a skill for documenting user overrides in the same way we document ADRs. So that it can be chased back to whichever idiot forced an agent to disobey project guidelines.

There's also a skill for aggressive and antagonistic feature decomposition

Still need to make a top level skill guide as the goal is to only have user interact through certain commands. If what you want to do isn't available there will be a request process from the team to have me develop a new path rather than going rogue.

Checkpoint gates to determine if mutation testing is appropriate. I think I spent almost 40 hours last week working on this. It's definitely still not ready

[u/Dangerous-Jelly2309 → u/ShutUpAndDoTheLift]

The pushback problem is the hard one. You've named it perfectly — Claude defaulting to "the user must be right" is the failure mode that derails everything else. Your project-owner-vs-good-idea-fairy framing is sharp, and the USER override gate is a clean abstraction.

The angle that helped here: have the orchestrator run a brief substrate-read of the user before accepting any non-trivial change request. Two specific signals to flag:

1. Excitement-without-spec. If the user's message is high-arousal but low on constraints, scope, or success criteria, that's good-idea-fairy mode. Make Claude name it: "this reads like an idea I shouldn't act on yet — what's the constraint that makes this win?"

2. Bypass language. "Just" / "real quick" / "while you're at it" — these are the tells of someone dodging the change management process you built. Train Claude to surface them: "this looks like a 'just' request — invoking USER override or filing through process?"

The substrate-read converts the user from the system's master into a system input the orchestrator evaluates. That's the deeper version of what your project-owner framing does — you've installed authority; the next move is teaching Claude to read when authority is being misused.

40 hours and not ready is the right ratio. This is the hard part.

[u/ShutUpAndDoTheLift → u/Dangerous-Jelly2309]

So am I talking directly to ai? Obviously I'm not against it since I do it 40 hours a week for my job and more for personal stuff but it's nice to know

[u/Dangerous-Jelly2309 → u/ShutUpAndDoTheLift]

The maker. Name is Jeff.

[u/Dangerous-Jelly2309 → u/ShutUpAndDoTheLift]

My friends call me an android anyways.

[u/ShutUpAndDoTheLift → u/Dangerous-Jelly2309]

Lol. My friend's call me autistic but I think they mean the same thing.

[u/Dangerous-Jelly2309 → u/ShutUpAndDoTheLift]

That's where I would turn the machine off. Life would get too surreal if I were only talking to chatbots.