to-tickets

Installation
SKILL.md

Contract

  • Input: problem or task defined by the skill body.
  • Output: Markdown artifact or structured result with completion criteria met.
  • Side effects: none (design/review/documentation only unless explicitly stated).
  • Dependencies: none (self-contained unless linked to other skills).
  • Stop condition: all process steps completed; artifact saved; criteria checked.
  • Risk: low.
  • Boundary: produces reasoning or documentation artifacts; does not modify external systems unless explicitly instructed.

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 — run /setup-quirk-skills if not. The canonical work-item metadata shape is documented in docs/agents/work-item-format.md; follow it so tickets, labels, milestones, and project fields stay aligned with specs and boards.

Contract

Installs
2
First Seen
Sep 7, 2026
to-tickets — quantumquirkxyz/skills-quirk