cohesion-coupling-review

Installation
SKILL.md

High Cohesion / Low Coupling (Review Skill)

Use when

  • A change touches multiple folders/layers/capabilities.
  • You’re tempted to import a file from another capability.
  • “Shared” is being considered for convenience.

Checklist (fast)

  1. Ownership: which capability/bounded context owns the rule/data?
  2. Cohesion: is the logic colocated with its change reason?
  3. Coupling: are dependencies narrow (ports/events) rather than concrete imports?
  4. Public surface: can exports be reduced to the minimal stable interface?
  5. Import hygiene: any deep imports into another capability/layer?
  6. Promotion: does it truly qualify for shared (2+ contexts, no business policy)?
Related skills

More from 7spade/black-tortoise

Installs
10
First Seen
Feb 1, 2026