Honey × Superpowers

Honey is turned on by the session's SessionStart hook — which lives in your (the orchestrator's) context. Superpowers dispatches fresh subagents with isolated context; they never inherit the hook. So every implementer, reviewer, and fixer runs Honey-off: full-fat code (Lever 1 dark) and verbose reports (Lever 2 dark) — multiplied per dispatch. That's the leak. Close it by pasting the directive into the dispatch prompt itself.

The two skills already pull cost the same way Honey does — cheap model per task, file handoffs over pasted text, one-line narration. Don't fight them; stack on top. Honey adds what they don't: less code in the worker, terser reports both ways.

When it fires

Any time you are about to dispatch a subagent under a Superpowers-style workflow: