righting-software
Installation
SKILL.md
Core Principle
Decompose by what changes (volatility), not by what the system does (functionality).
Every design decision must be justifiable by a specific axis of anticipated change. If you cannot name the volatility being encapsulated, the design is suspect.
The Design Process
Follow this sequence. Do not skip or reorder phases.
Phase 1 — Identify Use Cases
Enumerate all system behaviors as verb-noun pairs: "Place Order", "Approve Loan", "Cancel Subscription".
Phase 2 — Identify Volatility
For each use case ask: what is most likely to change? Least likely?