What problem does it solve? When a feature spec is sliced into tickets by visible behavior, two tickets can adopt opposite assumptions about the same database field, each passing its own review and tests, with the defect surfacing only later at high cost. This Skill adds the orthogonal pass between spec writing and ticket slicing: it maps which flows write to each shared field and resolves writer conflicts up front in an ADR. ## Core Features & Use Cases - Shared-state mapping: Lists the tables and columns a stage touches and names every writer per field, classified by flow (synchronous request, webhook, scheduled scan, migration). - Conflict resolution in ADR: For fields with multiple writers, decides who wins on disagreement and what each writer does when the value is unknown, recording the decision in docs/adr/. - Glossary enforcement: Invokes domain modeling to reconcile vocabulary, ensuring condemned terms are either migrated out of the code or reinstated as the winner. - Use Case: Before slicing a 64-ticket stage, run the gate to discover that seven tickets share writer conflicts on a handful of columns, and capture the resolution in an ADR that every downstream ticket cites. ## Quick Start Run /ticket:estado-compartilhado with the path to your stage spec after /to-spec and before /to-tickets to map shared state writers and record conflicts in an ADR.
