to-tickets

Convert plan documents into issue tracker tickets with tracer-bullet vertical slices and blocking dependencies.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/B4rz99/fidy --skill to-tickets-b4rz99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/B4rz99/fidy/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/B4rz99/fidy --skill to-tickets-b4rz99

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of converting plans, specifications, or product requirements into individual, manageable tickets for an issue tracker, improving project workflow and team collaboration.

Core Features & Use Cases

  • Ticket Breakdown: Automate the segmentation of project plans into individual tickets based on specific criteria.
  • tracer-bullet Vertical Slices: Generate tickets that encompass end-to-end functionality across various layers (schema, API, UI, and tests).
  • Blocking Tickets: Create tickets that clearly state dependencies and ensure the right sequence of work.
  • Integration with Issue Trackers: Supports publishing tickets directly to issue trackers with the necessary details and labels.

Quick Start

Break down the product requirements document 'requirements.docx' into tickets for the issue tracker using the to-tickets skill.

Frequently Asked Questions about to-tickets

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

FAQPage Schema
How do I convert a product requirements document into issue tracker tickets?

Converting a product requirements document into issue tracker tickets is done by breaking down plans into individual tickets using tracer-bullet vertical slices. This automates segmentation while establishing explicit blocking dependencies to sequence the work.

What are tracer-bullet vertical slices in issue tracking?

Tracer-bullet vertical slices in issue tracking generate tickets that encompass end-to-end functionality across schema, API, UI, and test layers. This ensures each ticket delivers functionality spanning the full software development stack.

How do I create tickets with explicit blocking dependencies for project management?

Creating tickets with explicit blocking dependencies involves generating individual tickets from specifications that clearly state their dependencies. This ensures the right sequence of work by enforcing blocking relationships between issued tickets.

Can I use this to break down software development specifications into manageable tickets?

Breaking down software development specifications into manageable tickets is supported by segmenting project plans into individual tickets based on specific criteria. It applies to workflows requiring structured issue tracking with clear dependencies.

Does this Skill require any dependencies to generate tickets from plans?

Generating tickets from plans requires no external dependencies. It operates independently using internal scripts to transform plan or specification documents into individual tickets for your issue tracker.