loom-ticketslisted

# loom-tickets Tickets are Loom's atomic execution work orders. A ticket owns one bounded change, live state, `ACC-*` acceptance, scope, current state, evidence links, review posture, durable Ralph context, worker output reconciliation, and one closure claim. It is not a scratchpad, plan, research note, transcript, parking lot, or disguise for unresolved shaping. Create or act from a ticket only when the execution boundary is clear enough that a future agent can continue from the ticket and linked records without chat history. ## Use This Skill When Use this skill for ticket creation, ticket readiness, scoped implementation work, continuation, status updates, acceptance changes, blockers, review state, closure, cancellation, or ticket summaries. Route elsewhere first when the real work is intended behavior, sequencing, tradeoffs, durable policy, architecture, data or state modeling, design coherence, ambiguous intent, evidence, audit, or reusable knowledge. ## Dispatch If creating or shaping a ticket: - read `references/creating-tickets.md` - read `references/ticket-shape.md` - inspect relevant records and source before asking the operator to repeat facts - create the ticket only when scope, acceptance, evidence posture, and first Ralph boundary are concrete - use `templates/ticket.md` If acting from, resuming, updating, reviewing, blocking, closing, or cancelling a ticket: - read the whole ticket - read `references/acting-on-tickets.md` - read or already know re