to-ticketslisted

# To Tickets Break a ready spec into vertical slices that can be implemented in fresh sessions without losing requirements. Use the tracker configured by `/setup-matt-pocock-skills`; its documentation controls physical paths, issue relationships, labels, and where the coverage artifact lives. Verify `/delivery-proof` and `/grilling` are installed before starting. If a companion is missing, name it; embedded proof rules remain binding and consequential unresolved choices must not be guessed. ## 1. Load and validate the source Read the complete spec or plan, its comments, linked decisions, prototypes, and research. Do not ticket a `draft` or `blocked` spec as if it were ready. If a legacy artifact has no status, audit it against `/to-spec` and `/delivery-proof`; preserve history and record missing readiness work. If either companion skill is not installed, apply the readiness and proof rules embedded here rather than skipping the gate. Do not change, reinterpret, or weaken source criteria while slicing. Proposed changes go back to the source artifact and its authorized owner. ## 2. Build the requirement ledger Before choosing slices, inventory every source ID: - outcomes, stories, invariants, and acceptance criteria; - decisions and their provenance; - dependencies and `OBL-*` delivery obligations; - rollout, compatibility, cutover, rollback, and outcome-verification needs. Record the original wording. This ledger is the denominator for coverage; an omitted requirement