to-tickets

Decompose project plans into dependency-mapped tracer-bullet tickets.

Updated Apr 8, 2026

Search Tags:#workflow #project management #software development #tickets #dependency mapping #tracer bullets

Ready to run

npx skills add https://github.com/tonomb/personal-pnl --skill to-tickets-tonomb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/tonomb/personal-pnl/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/tonomb/personal-pnl --skill to-tickets-tonomb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity and lack of structure in project planning by breaking down high-level goals into granular, verifiable, and dependency-aware vertical slices.

Core Features & Use Cases

Vertical Slicing: Automatically decomposes complex features into tracer-bullet tickets that cut through all layers of the stack.
Dependency Mapping: Explicitly defines blocking edges between tickets to ensure a logical and efficient execution order.
Flexible Publishing: Supports both local file-based tracking and integration with professional issue trackers like GitHub or Linear.

Quick Start

Ask the agent to break the current project plan into a set of tracer-bullet tickets with defined blocking edges.

Frequently Asked Questions about to-tickets

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

FAQPage Schema

How do I break down project specifications into vertical tracer-bullet tickets?▼

Breaking down project specifications into vertical tracer-bullet tickets involves decomposing high-level goals into granular slices that cut through all stack layers. This approach ensures each slice is verifiable and gated by explicit blocking dependencies for logical execution.

What is vertical slicing in software development project management?▼

Vertical slicing in software development is decomposing complex features into tracer-bullet tickets that cut through all layers of the stack. This technique ensures each slice delivers verifiable value across the entire architecture.

How do I map dependencies and blocking edges between development tickets?▼

Mapping dependencies between development tickets requires explicitly defining blocking edges to ensure a logical execution order. This gating mechanism guarantees tasks are properly sequenced and verifiable within the workflow.

Can I use tracer-bullet ticketing with local file systems or issue trackers?▼

Yes, you can manage tracer-bullet tickets across local file systems or integrated issue trackers. This flexible publishing supports professional platforms like GitHub or Linear for development workflow sequencing.

What is the best way to sequence software development tasks with dependency mapping?▼

The best way to sequence software development tasks is using tracer-bullet tickets with explicit dependency mapping. This approach defines blocking edges between slices to ensure efficient, verifiable execution order across the stack.