write-persistence-scenarios

What problem does it solve? Before designing a relational data model, teams often jump straight to tables without clarifying what business facts must be created, updated, or deleted and why. This Skill turns existing business scenarios and business events into explicit persistence scenarios, so data modeling starts from verified business grounds rather than guesses. ## Core Features & Use Cases - Persistence Scenario Authoring: Writes each scenario with actor, pre-state, business event, conditions, business decision, resulting facts, next state, history, and retention conditions. - Three-Operation Coverage Check: Records create, update, and delete as covered or not-applicable with reasons, distinguishing business cancellation from physical deletion. - Condition Matrix Validation: Pipes a condition matrix JSON via stdin to scripts/scenario_matrix.py, which reports violations as JSON lines with exit codes 0 (clean), 1 (violations), or 2 (unreadable input). - Use Case: Given order placement, cancellation, and refund business scenarios, produce confirmed persistence scenarios that a data modeling step can consume without unverified assumptions. ## Quick Start Using these business events and scenarios, write the persistence scenarios covering create, update, and delete before we start data modeling.