To Tickets

Turns a confirmed spec into real tracked issues — not a markdown list that lives only in the chat. Read CONTEXT.md's "## Engineering Setup" section first for the tracker, repo, and labels (run setup-krit-skills if missing).

Steps

1. Slice the spec into vertical slices. Each ticket should deliver a thin, independently-testable piece of end-to-end behavior — not a horizontal layer ("write the DB schema" as its own ticket with no working behavior attached). A good test: could this ticket ship alone and demonstrably work? If not, it's too thin or badly cut.