to-tickets

Breaks a grilled specification into dependency-ordered tracer-bullet ticket files with blocking edges.

3|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/MaxWolf-01/agents --skill to-tickets-maxwolf-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/to-tickets
Command: npx skills add https://github.com/MaxWolf-01/agents --skill to-tickets-maxwolf-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished specification into actionable work is error-prone: teams either slice work horizontally by layer (producing nothing demoable) or lose track of which pieces depend on which. This Skill converts a grilled spec into a set of vertical-slice tickets with explicit blocking edges, published as markdown files per the tracker conventions. ## Core Features & Use Cases - Vertical slice drafting: Splits work into tracer-bullet tickets that cut through every layer (schema, API, UI, tests), each sized to fit a single context window and demoable on its own. - Dependency modeling: Assigns each ticket its blocking edges, numbers tickets in dependency order, and routes open questions into decision tickets that block the slices needing their answers. - Spec property disposition: Maps executable spec properties to a shared property-test ticket, stamps reviewed properties as acceptance criteria, and handles wide refactors via expand-contract sequencing. - Use Case: After grilling a feature spec until its frontier is empty, invoke this Skill to produce a numbered set of ticket files (e.g., 01-add-schema.md, 02-build-api.md) with blocked-by edges, ready for dispatch to fresh worker sessions. ## Quick Start Ask the agent to break the grilled spec into tickets and publish them per the tracker conventions.

Frequently Asked Questions about to-tickets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a software spec into implementation tickets?

Run this Skill on a spec whose grilling frontier is empty. It drafts vertical slices that each cut through every layer, assigns blocking edges between tickets, and publishes one numbered markdown file per ticket in dependency order.

What is a tracer-bullet or vertical slice ticket?

A vertical slice is a narrow but complete path through every layer of the stack (schema, API, UI, tests) rather than a horizontal slice of one layer. Each completed slice is demoable or verifiable on its own and sized to fit a single fresh context window.

How are dependencies between tickets handled?

Each ticket declares a blocked-by list of tickets that must complete first, and files are numbered in dependency order with blockers first. A ticket with no blockers can start immediately, and orderings prefer making the feature drivable early.

Can this handle large refactors that break many call sites?

Yes, wide refactors are sequenced as expand-contract instead of vertical slices: add the new form beside the old, migrate call sites in batches sized by blast radius, then delete the old form in a final ticket blocked by every migration batch.

What happens to unanswered questions in the spec?

A question you can phrase but the spec does not answer becomes a decision ticket with status open, and every slice needing its answer is blocked by it. Questions you cannot yet phrase stay in the spec's Fog until sharpened.