I’ve been using Claude Code on a side project (indie game in Godot) and kept running into the same problem: Claude would just start hacking away at code before it had any kind of plan. Cue me rolling back changes and saying “no, stop, think about this first” for the 400th time. I was already using Obra’s Superpowers plugin, which is genuinely great! The episodic memory and workflow tools are solid. But Claude kept treating the workflow as optional. It’d acknowledge the process, then just… do whatever it wanted anyway. The instructions were there, Claude just didn’t care enough to follow them consistently. “Just use plan mode”: yeah, plan mode stops Claude from making edits, but it’s a toggle, not a workflow. You flip it on, Claude thinks, you flip it off, Claude goes. There’s no structured brainstorming phase, no plan approval step, no guardrails once you switch back to normal mode. My hooks enforce a full pipeline: brainstorm, plan, get sign-off, then execute, AND Claude can’t skip or shortcut any of it. So I built ironclaude on top of Superpowers. It keeps everything I liked especially the episodic memory but makes the workflow mandatory through hooks. Claude can’t skip steps even if it wants to. Then I bolted on an orchestrator that runs through Slack: it spawns worker agents that all follow the same workflow. Think of it as a “me” that can run multiple Claude sessions in parallel, except it actually follows the rules I set. And because it’s learning from episodic memory, by the time you trust it to orchestrate, it’s already picked up how you direct work. Repo: https://github.com/robertphyatt/ironclaude Happy to answer questions. Tear it apart, tell me what’s dumb, whatever. Just figured other people might be hitting the same problems I was. submitted by /u/HighGate2025
Originally posted by u/HighGate2025 on r/ClaudeCode