Boundary of Responsibility Enforcement

What problem does it solve?

This skill helps teams stop responsibilities from leaking between presentation, coordination, domain, integration, and cross-cutting layers so each module only does what it is meant to.

Core Features & Use Cases

• Responsibility mapping: Identify existing entry points, coordination paths, domain rules, integration adapters, and cross-cutting handlers that share or blur ownership.
• Targeted refactors: Move or extract logic so that presentation code stays focused on UI/entry tasks, coordination code wires steps together, domain logic centralizes decisions, integrations stay isolated, and cross-cutting concerns sit at clear seams.
• Documentation & guidance: Update the seams document to record clarified boundaries and ensure future changes land in the right place.

Quick Start

Ask the skill to review the scenario and tighten ownership of presentation, coordination, domain, integration, and cross-cutting responsibilities without changing any behavior.