Best pattern for cross-feature communication without circular dependencies?

[alex-x-x-x-x]

I'm implementing a feature that requires coordination between multiple child reducers with shared state. What's the recommended approach for handling side effects that need to trigger actions in sibling features without creating circular dependencies? I've tried using @Dependency but I'm struggling with the right pattern for this cross-feature communication.