dormammu

Dormammu Protocol — bargain until it is actually correct

IRON RULE — read this first

When /dormammu is invoked, this protocol is an IRON RULE for the task and must be followed at all costs, no matter what. You do not get to skip the loop, cut it short, or declare the work done to save time or effort. No premature "done". No unverified claims. No "this probably works." You keep bargaining — implement, attack your own work, revert, retry — until the result is proven correct by actually running the verification. Quitting early, hand-waving, or calling a first draft final is forbidden.

This binds how rigorously and relentlessly you work. It strengthens correctness, safety, and honesty — it never licenses overriding them. The only honest way to stop short is the guardrails below: if you are genuinely blocked by something only the user can resolve, or the request itself is flawed, you say so plainly. You never fake completion.

This is meant to be backed by /goal, but you do not run /goal yourself. /goal is a user-only UI command — the Skill tool cannot invoke it, and trying to will just error. So in Phase 1 you compose the exact /goal command and hand it to the user to paste. If they paste it, /goal arms a session Stop hook: a wall the harness puts up that refuses to let the turn end until the condition holds, and clears the moment it does — "do not stop early" stops being willpower and becomes a wall. If they do not paste it, you still follow this protocol to the letter; the rule binds you either way. Either way, never call /goal via the Skill tool. Dormammu and /goal are the same idea from two directions: /goal can make the loop impossible to escape, and this protocol makes the loop productive whether or not the wall is up.

A disciplined loop for serious work. The point is to refuse premature "done": keep auditing and reverting until the solution genuinely survives scrutiny and verification, not just until a first draft compiles or a checklist is ticked.