to-tickets

Decomposes project specifications into vertical-slice tickets with dependency tracking.

Updated Dec 17, 2025
One-click install
npx skills add https://github.com/Frantss/oxform --skill to-tickets-frantss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/Frantss/oxform/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/Frantss/oxform --skill to-tickets-frantss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of breaking down complex project requirements or vague conversations into manageable, verifiable, and dependency-aware work units.

Core Features & Use Cases

  • Vertical Slicing: Automatically structures work into tracer-bullet tickets that cut through all layers of the stack.
  • Dependency Mapping: Explicitly defines blocking edges to ensure a logical and safe implementation sequence.
  • Use Case: When starting a new feature, use this skill to convert a high-level spec into a series of sequential tickets that keep the codebase in a deployable state throughout the development process.

Quick Start

Use the to-tickets skill 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-slice tickets?

To break down project specifications into vertical-slice tickets, decompose high-level requirements into a sequence of tracer-bullet tickets that cut through all stack layers. This ensures each ticket represents a complete, verifiable unit of work while maintaining a deployable codebase.

What is tracer-bullet ticketing in agile project management?

Tracer-bullet ticketing in agile project management structures work into end-to-end vertical slices that cut through all layers of the stack. This technique ensures each ticket forms a complete, verifiable unit of work to keep the codebase stable throughout implementation.

How do I map dependencies when creating implementation-ready tasks?

To map dependencies when creating implementation-ready tasks, explicitly define blocking edges between vertical-slice tickets. This ensures a logical and safe implementation sequence, preventing structural issues by verifying that foundational tasks precede dependent work.

Can I use vertical slicing to keep a codebase deployable throughout development?

Yes, you can use vertical slicing to keep a codebase deployable throughout development. By structuring work into tracer-bullet tickets with strategic sequencing, each task represents a verifiable unit of work that maintains a stable, deployable state.

Does this ticket decomposition approach work for vague conversational plans?

Yes, this ticket decomposition approach works for vague conversational plans by breaking them down into manageable, verifiable, and dependency-aware work units. It transforms high-level discussions into granular, implementation-ready tasks suitable for the software development lifecycle.