Parnas Partition

The decomposition criterion from Parnas 1972 - a module boundary is judged by the design decision it HIDES, never by the processing step it performs, so every proposed module must name its secret or the split is rejected. Reach for it when an agent proposes a new module, package, or file split, when a repartition plan comes back from interrogating the agents about structure, or when someone says "split this module", "where should the boundary go", "decompose by secrets", "what does this module hide", or "why does one change touch six files". Differentiator - this island owns only the question that decides WHERE a boundary goes; depth vocabulary and the deletion test, interface token economics, cohesion sizing, and duplicate-fact detection all live on neighbouring islands.

Island-Dev-Crew Updated 4 repo stars
Uncle Bob Skills — human intent, agent work, evidence, and human decision

File contents

Island-Dev-Crew/uncle-bob-skills commit 0d29fd71b6

Frequently asked questions

npx get-skill add island-dev-crew/parnas-partition