To Tickets

To Tickets is an Automation skill for Claude Code, published by stevesolun in ctx.

578 stars71 forkson stevesolun/ctxAdded 2026/08/25+1% in starsRepository updated 2026/08/24

agentsai-agentsanthropicautomationclaudeclaude-codecontext-managementdeveloper-toolsharnessknowledge-graphllmllm-wikimcpmicro-skillsobsidianreal-timerecommendation-engineskill-managementskillswiki

Install in seconds

Install To Tickets

Copy To Tickets into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-tickets ~/.claude/skills/to-tickets

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/stevesolun/ctx.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .agents/skills/to-tickets/SKILL.md in stevesolun/ctx
Installs to: ~/.claude/skills/to-tickets
Collection: One of 25 skills cataloged from this repository
Category: Automation — 1523 skills

What To Tickets does

To Tickets breaks a plan, spec, or conversation into dependency-aware tickets with clear acceptance criteria. Use it when work needs to be sliced for local planning or an issue tracker.

To Tickets is cataloged under Automation on DirSkills. To Tickets comes from a repository tagged agents, ai-agents, anthropic, automation and claude.

Documentation

README

Excerpt

Create tickets

Read the source plan, spec, issue, or conversation and inspect enough of the repository to avoid fictional boundaries. Use the project's established domain language and preserve relevant architectural decisions.

Prefer narrow vertical slices that deliver observable behavior and can be verified independently. Size work for the actual team and risk rather than a fixed context-window rule. Use horizontal or mechanical slices when the change cannot remain coherent vertically.

Model only real blocking edges. Tickets without blockers form the available frontier and may proceed concurrently. For a broad compatibility migration, consider an expand–migrate–contract sequence so intermediate states remain usable.

Each ticket should communicate:

This is the opening of the README. Read the full README on GitHub.

Frequently asked about To Tickets

What else does stevesolun publish alongside To Tickets?
To Tickets is one of 25 skills that DirSkills catalogs from stevesolun/ctx, the repository it ships in. Its siblings there include Ask Matt, Code Review and Codebase Design. Each one is a separate skill with its own page in this directory, installs the same way To Tickets does, and is maintained by stevesolun in that same repository. The rest of the collection is listed on the stevesolun/ctx page.
How does To Tickets compare to other Automation skills?
To Tickets ranks #1248 by stars among the 1523 Automation skills in this catalog. The most-starred ones next to it are Autonomous Loops, Autonomous Agent Harness and Automation Audit Ops. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of To Tickets against them. Open each page to compare what they document and how they install.