to-tickets

Create tickets with dependencies and blocking issues from text input.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/CarbonTails/Di-Vincis-Atelier --skill to-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/CarbonTails/Di-Vincis-Atelier/tree/main/.cursor/skills/to-tickets
Command: npx skills add https://github.com/CarbonTails/Di-Vincis-Atelier --skill to-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of breaking down plans, specifications, or conversations into individual tickets for tracking and managing work in issue trackers.

Core Features & Use Cases

  • Ticket Creation: Automatically generate tickets from text input, specifying dependencies and blocking issues.
  • Integration: Supports various issue trackers, including GitHub, Linear, etc., and allows for custom configurations.
  • Local and Real Tracker Support: Can output ticket information in local Markdown files or publish directly to issue trackers.
  • Use Case: When planning a software project, use this Skill to quickly create a structured set of tickets, each with its dependencies, directly from a project plan.

Quick Start

Run the to-tickets skill with the conversation or plan text to generate tickets and dependencies.

Frequently Asked Questions about to-tickets

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

FAQPage Schema
How do I create tickets from project plans and conversations?

Ticket creation from project plans is automated by parsing text input to identify relevant information, generating individual tickets with defined dependencies and blocking issues for tracking work.

Can I generate tickets with dependencies for issue tracking systems?

Yes, generating tickets with dependencies for issue tracking is supported. The system parses input text to define blocking issues and publishes directly to trackers like GitHub or Linear.

Does this work with GitHub and Linear for work decomposition?

Yes, it works with GitHub and Linear for work decomposition. It supports integration with various issue trackers, allowing custom configurations to publish decomposed work items directly.

What is the best way to output ticket information locally without a tracker?

The best way to output ticket information locally without a tracker is using the Markdown file format. The system can generate and save ticket details and dependencies directly to local Markdown files.

How do I automate work decomposition from specifications into a structured set of tickets?

Work decomposition from specifications is automated by parsing the provided text. It identifies the relevant information to break down plans into a structured set of tickets, each with its own dependencies.

Do I need an issue tracker to manage tickets from specs?

No, you do not need an issue tracker to manage tickets from specs. The system supports local Markdown output, allowing you to generate and manage ticket information and dependencies without publishing to a real tracker.