To Tickets

Break a plan, spec, or conversation into a set of tickets: tracer-bullet vertical slices, each declaring the tickets that block it.

The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run /setup-repo-skills.

Arguments

Invoke as /to-tickets [source] [slug=<slug>].

• No arguments: use the current conversation.
• An issue number, URL, or path: use that artifact as the source.
• One bare kebab-case token: when the tracker config defines Spec lifecycle operations, treat it as a lifecycle slug and resolve its parent spec; otherwise treat it as a source path or reference.
• A source plus slug=<slug>: use the explicit source and group the published tickets under that lifecycle slug.

Lifecycle slugs are optional and affect only trackers whose config defines Spec lifecycle operations.

Process