agentsclimarketplace
Sign in

To tickets

Skill uluserdar/claude-ecosystem/skills/to-tickets

Breaks a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring the tickets that block it, then publishes them (as GitHub issues if the target project has a GitHub remote, otherwise as local markdown files). ALWAYS trigger on explicit phrases like "break this into tickets", "turn this spec into tickets", "make me some tickets for this", "split this into tracer-bullet tickets", "ticket this out". Do NOT trigger for writing the spec itself (that's to-specs), creating a brand-new release plan from scratch (that's create-plan), or when the user just wants a single ad-hoc issue with no breakdown.From its SKILL.md

Install
npx -y skills add uluserdar/claude-ecosystem --skill to-tickets

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

to-tickets

This skill's only job is to hand off to the ticket-writer subagent, which breaks a plan/spec/conversation into tracer-bullet tickets with blocking edges and publishes them. Do not draft the ticket breakdown yourself, do not decide blocking edges yourself, and do not write or publish any tickets yourself.

Instructions

  1. Invoke the ticket-writer subagent via the Agent tool, passing along:
    • Everything relevant that's been discussed in this conversation so far (the breakdown is synthesized from this — never re-ask the user to restate it).
    • Any explicit reference the user made to a spec, release-plan step, or existing issue this breakdown is for, if mentioned.
    • Model: read agentModel["ticket-writer"] from .claude/claude-ecosystem-settings.json, falling back to agentModel.default; pass whichever resolves as the model parameter, or omit model entirely if neither is set.
  2. ticket-writer owns codebase exploration, vertical-slice breakdown, blocking-edge assignment, user confirmation, and publishing (as GitHub issues or local files) end to end — do not duplicate or second-guess its work.
  3. Once ticket-writer finishes, relay its summary (file paths and/or issue URLs) back to the user.
<constraints> - This skill delegates 100% of ticket-breakdown and publishing work to `ticket-writer`. It has no standalone ticketing logic of its own beyond routing. - This skill runs standalone only — it is never invoked by, and never invokes, `to-specs` or `create-plan`, even though the user may feed it a spec or plan produced by either of those. - This skill does not interview the user for what the work should be — it only breaks down what's already known into tickets. </constraints>

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.