to-tickets

Break plans and specs into tracer-bullet tickets with declared blocking edges.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill to-tickets-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill to-tickets-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tasks end up as horizontal layer slices that cannot be demoed, dependencies stay implicit, and tickets go stale with file paths and code snippets. This Skill converts any plan into vertical-slice tickets with explicit blocking relationships, published to your configured tracker. ## Core Features & Use Cases - Tracer-bullet slicing: Breaks work into narrow but complete vertical slices spanning schema, API, UI, and tests, each demoable on its own and sized for a single context window. - Dependency mapping: Every ticket declares its blocking edges, published as text references in local files or as native blocking links on GitHub, Linear, or similar trackers. - Wide-refactor handling: Recognizes expand-contract refactors that cannot be vertically sliced and sequences them as expand, migrate, and contract tickets. - Use Case: After drafting a feature spec for a new dashboard, ask the agent to break it into tickets; it proposes a numbered breakdown, quizzes you on granularity and dependencies, then publishes approved tickets with a ready-for-agent label. ## Quick Start Ask the agent to break the current plan or a referenced spec file into tracer-bullet tickets and publish them to the configured issue tracker.

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 feature spec into tickets?▼

Provide the spec path, issue URL, or work from the current conversation, and the Skill drafts vertical-slice tickets with blocking edges. It quizzes you on granularity and dependencies, then publishes the approved breakdown to your configured tracker.

What is a tracer-bullet or vertical-slice ticket?▼

A vertical slice cuts a narrow but complete path through every layer, including schema, API, UI, and 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 context window.

Can I publish tickets to GitHub or Linear?▼

Yes, the Skill publishes one issue per ticket in dependency order using the platform's native blocking or sub-issue relationships where available. Without a real tracker, it writes one markdown file per ticket under .scratch with blocking edges listed as text.

How are large refactors handled in ticket breakdowns?▼

Wide refactors that cannot stay green in a vertical slice are sequenced as expand-contract: add the new form beside the old, migrate call sites in blast-radius-sized batches, then delete the old form in a final contract ticket.

Why does the Skill say the tracker is not configured?▼

The issue tracker and triage label vocabulary must be provided beforehand by running the setup-matt-pocock-skills command. Without that configuration, the Skill cannot know where or how to publish tickets.