To Tickets
Break a plan, spec, grilling summary or conversation into a set of tracer-bullet tickets — thin, end-to-end slices that each work and can be demonstrated on their own — with explicit "blocked by" edges, so the work forms a dependency graph and anyone can pick up a ticket whose blockers are done. Covers vertical vs horizontal slicing (Hunt & Thomas's tracer bullets, Cockburn's Elephant Carpaccio, INVEST), prefactoring first ("make the change easy, then make the easy change"), sequencing a wide refactor as expand-migrate-contract (Parallel Change), sizing a ticket to one session and one pull req
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill to-ticketsgit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/to-tickets ~/.claude/skills/to-ticketsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# To Tickets
Apply this skill when a piece of work is decided but too big to build in one go: a spec, an epic, a grilling summary, a design that spans several layers. The output is a set of tickets, each a **tracer bullet** — a narrow slice that runs through every layer it needs and works on its own — and each naming the tickets that **block** it. Together they form a dependency graph; the **frontier** is every ticket whose blockers are done, and that is what can be picked up next, in parallel.
Use `ticket-writer` for the anatomy of a single ticket; this skill is about the set.
## Core Philosophy
**Slice vertically, not horizontally.** A horizontal slice ("all the database changes", then "all the API", then "all the UI") delivers nothing until the last slice lands, and hides integration problems until then. A vertical slice cuts a thin path through schema, logic, API, UI and tests, so each one can be demonstrated and verified on its own.
**Tracer bullets find the target early.** Hunt and Thomas: build a thin version that connects end to end first, then thicken it. The first ticket should prove the path; later tickets widen it.
**Dependencies are edges, not order.** A numbered list implies a sequence that may not exist. Name for each ticket exactly which tickets must finish first. Everything else can run in parallel.Details
- Skill name
to-tickets- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/to-tickets/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the To Tickets skill do?
Break a plan, spec, grilling summary or conversation into a set of tracer-bullet tickets — thin, end-to-end slices that each work and can be demonstrated on their own — with explicit "blocked by" edges, so the work forms a dependency graph and anyone can pick up a ticket whose blockers are done. Covers vertical vs horizontal slicing (Hunt & Thomas's tracer bullets, Cockburn's Elephant Carpaccio, INVEST), prefactoring first ("make the change easy, then make the easy change"), sequencing a wide refactor as expand-migrate-contract (Parallel Change), sizing a ticket to one session and one pull req
How do I install the To Tickets skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is To Tickets popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Unit Testing Principles
5vnovakovits/claude-skills
Apply Vladimir Khorikov's unit testing framework from "Unit Testing Principles, Practices, and Patterns" (Manning, 2020). Covers the four pillars (protection against regressions, resistance to refactoring, fast feedback, maintainability) and their unavoidable trade-offs, the three styles of unit testing (output-based, state-based, communication-based), observable behavior vs implementation details as the line that separates good and bad tests, mocks vs stubs with strict verification rules, the managed vs unmanaged dependency distinction (the most useful heuristic for deciding what to mock), wh
Testing Skills with Subagents
8Freddy-CHEN-ux/00_claude_skills
Use to validate process documentation. Apply TDD to skill writing: RED (run without skill, document failures) → GREEN (write skill) → REFACTOR (close loopholes). Test under pressure: time constraints, sunk cost, exhaustion, authority.
Verification Before Completion
8Freddy-CHEN-ux/00_claude_skills
Use when finishing any task. Final checklist before marking complete. Ensures nothing forgotten, all tests pass, documentation updated.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.