to-tickets

Decomposes specs and plans into structured vertical-slice tickets with dependency mapping for GitHub or Linear.

63|9|Updated Jun 15, 2025
One-click install
npx skills add https://github.com/willdady/platypus --skill to-tickets-willdady
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/willdady/platypus/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/willdady/platypus --skill to-tickets-willdady

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of translating high-level plans, specs, or unstructured conversations into a structured, manageable set of technical tasks with clear dependency chains.

Core Features & Use Cases

  • Vertical Slicing: Automatically breaks down complex requirements into tracer-bullet tickets that cut through all layers of the stack.
  • Dependency Mapping: Identifies and defines blocking edges between tickets to ensure a logical execution order.
  • Integration: Supports publishing to local files or native issue trackers like GitHub and Linear.
  • Use Case: Use this when you have a complex feature spec and need to generate a sequence of development tasks that are ready for an agent to implement one by one.

Quick Start

Invoke the to-tickets skill to analyze the current conversation and generate a list 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 a project specification into agile development tickets?

To break down a project specification into agile development tickets, this Skill decomposes high-level plans and conversational specs into structured, vertical-slice tickets with explicit dependency mapping. It organizes tasks into logical execution sequences ready for implementation.

What is tracer-bullet task breakdown in agile project management?

Tracer-bullet task breakdown in agile project management automatically slices complex requirements into tickets that cut through all layers of the stack. This technique defines blocking edges between tickets to ensure a logical execution order for agentic implementation.

Can I publish dependency-mapped tickets to GitHub or Linear issue trackers?

Yes, you can publish dependency-mapped tickets to GitHub or Linear. This Skill supports integration with native issue trackers like GitHub and Linear, as well as local file-based task management, to maintain state and blocking relationships.

How do I map dependencies and blocking relationships for development tasks?

To map dependencies and blocking relationships for development tasks, this Skill identifies and defines blocking edges between generated tickets. It ensures a logical execution sequence by organizing the vertical-slice tasks according to their dependency chains.

Do I need an issue tracking system to generate vertical-slice tickets from conversations?

No, an issue tracking system is not strictly required to generate vertical-slice tickets from conversations. While it supports publishing to GitHub and Linear, you can also use local file-based task management to maintain state and blocking relationships.