skills.rest
OmexIT
OmexITCOMMUNITY
Explore all skills by this author →
GitHub

ticket-breakdown

Convert PRD or design docs into epics, tickets, and acceptance criteria.

13|4|Updated Feb 20, 2026
Search Tags:#planning#epics#agile#prd#product-management#design-doc#ticket-breakdown
One-click install
npx skills add https://github.com/OmexIT/claude-skills-pack --skill ticket-breakdown-omexit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-breakdown
Source: https://github.com/OmexIT/claude-skills-pack/tree/main/skills/ticket-breakdown
Command: npx skills add https://github.com/OmexIT/claude-skills-pack --skill ticket-breakdown-omexit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts a PRD or design doc into a structured set of epics and engineering tickets, each with acceptance criteria, dependencies, sequencing, and rollout steps to align teams and ensure a smooth delivery.

Core Features & Use Cases

  • Automatically decompose a spec into epics and tickets with clear acceptance criteria and defined dependencies.
  • Generate a rollout sequence and prioritization to minimize risk and maximize early value.
  • Produce templates ready for import into project management tools (e.g., Jira, Linear) and aid handoff to execution teams.

Quick Start

Provide a ticket breakdown from a PRD or design doc by outlining epics, tickets, acceptance criteria, dependencies, and rollout sequencing.

Frequently Asked Questions about ticket-breakdown

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

FAQPage Schema
How do I break down a PRD into actionable agile tickets?▼

To break down a PRD into actionable agile tickets, the skill automatically decomposes a spec into structured epics and engineering tickets, each with clear acceptance criteria, defined dependencies, and rollout sequencing.

What is the best way to generate epics and acceptance criteria from a design doc?▼

Generating epics and acceptance criteria from a design doc involves mapping the spec to a structured ticketing workflow that aligns with agile planning boards and ensures smooth project delivery.

Can I create a rollout sequence and prioritization for project planning from a spec?▼

Yes, you can create a rollout sequence and prioritization from a spec to minimize risk and maximize early value, producing templates ready for import into project management tools like Jira or Linear.

Does ticket-breakdown work without external dependencies for project management?▼

Ticket-breakdown works without external dependencies to convert a PRD or design doc into a structured set of epics and tickets, aiding handoff to execution teams and project boards.

How do I map a structured ticketing workflow to an agile project board?▼

You map a structured ticketing workflow to an agile project board by specifying epics, tickets, acceptance criteria, and rollout sequencing from your PRD, ensuring alignment and smooth delivery across teams.

Related Skills

Explore More Product & Management Skills→
lluppesmslluppesms

breakdown-epic-pm

Generate a structured Markdown Epic PRD from epic idea and target user input.

Community
Intermediate
faionfaionfaionfaion
4

faion-pm-agile

Guide agile project management with Scrum, Kanban, SAFe, and Jira.

Community
Intermediate
ConnectiveTCSConnectiveTCS

sprint-planner

Plan sprints with story estimation, capacity planning, and goal definition.

Community
Intermediate
OzeroHAXOzeroHAX
32

project-standart-epic

Decompose product requirements and architecture into prioritized epics with dependency mapping and acceptance criteria.

Community
Intermediate