skills.rest
Yassimba
YassimbaCOMMUNITY
Explore all skills by this author →
GitHub

to-tickets

Breaks plans and specs into tracer-bullet tickets with blocking edges published to an issue tracker.

9|Updated Jul 17, 2026
Search Tags:#planning#issue tracker#task breakdown#github issues#tickets#dependency graph#vertical slice
One-click install
npx skills add https://github.com/Yassimba/loom --skill to-tickets-yassimba
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/Yassimba/loom/tree/main/skills/to-tickets
Command: npx skills add https://github.com/Yassimba/loom --skill to-tickets-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an agreed plan or spec into actionable work items is error-prone: tickets end up as horizontal layer slices, dependencies are implicit, and nothing is demoable until the end. This Skill converts a plan, spec, or conversation into vertical tracer-bullet tickets, each declaring exactly which other tickets block it, and publishes them to your configured issue tracker. ## Core Features & Use Cases - Vertical slice breakdown: Each ticket cuts a complete path through schema, API, UI, and tests so it is demoable on its own and fits in a single context window. - Blocking edge modeling: Every ticket declares its blockers, published as text in a local ai-docs/tickets.md file or as native blocking links on GitHub, Linear, or another real tracker. - Wide refactor handling: Mechanical changes with large blast radius are sequenced as expand-migrate-contract instead of being forced into a tracer bullet. - Use Case: After agreeing on a spec for a CSV export feature, run this Skill to draft five tracer-bullet tickets with dependency edges, review the breakdown interactively, then publish them to GitHub Issues with native blocking links. ## Quick Start Use the to-tickets skill to break the approved spec in ai-docs/specs/export.md into tickets and publish them to the configured 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 spec into tickets for an issue tracker?▼

Pass the spec path or issue reference to the to-tickets skill. It drafts vertical tracer-bullet tickets with blocking edges, asks you to approve the breakdown, then publishes them to your configured tracker in dependency order.

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

A vertical slice ticket cuts a narrow but complete path through every layer — schema, API, UI, and tests — so it is demoable on its own. This contrasts with horizontal slices that cover only one layer and deliver nothing verifiable alone.

Does to-tickets work with GitHub Issues and Linear?▼

Yes. When a real tracker is configured via loom init, it publishes one issue per ticket using the platform's native blocking or sub-issue relationships. Without a tracker, it writes a local ai-docs/tickets.md file with text-based blocking edges.

How are large refactors handled when slicing tickets?▼

Wide refactors with large blast radius are sequenced as expand-contract: add the new form beside the old, migrate call sites in batches that keep CI green, then delete the old form in a final ticket blocked by every migration batch.

What happens if no issue tracker is configured?▼

The skill checks ai-docs/agents/issue-tracker.md for configuration. If missing, it suggests running /loom to initialize, falling back to Beads when the br tool is installed or to a local Markdown tickets file otherwise.

Related Skills

Explore More Software Engineering Skills→
simplyblocksimplyblock
4

brainstorming

Explores product ideas and classifies them into spike, bounded, or architectural paths before any design work.

Official
Intermediate
ArcReelArcReel
4.3k

wayfinder

Plan large efforts as decision tickets tracked on an issue tracker.

Official
Advanced
X0x888X0x888
3

review-hard

Review a specified codebase area for bugs, regressions, and unsafe assumptions.

Community
Basic
magisphmagisph

pm-agent

Decompose complex requirements into prioritized JSON plans and task-board.md files with API contracts.

Community
Advanced