decompose-epic

Decompose Linear epic descriptions into actionable sub-tickets with repository assignments.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill decompose-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decompose-epic
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/decompose-epic
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill decompose-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of dissecting large epics into smaller, manageable sub-tickets, streamlining project planning and execution.

Core Features & Use Cases

  • Automated Decomposition: Analyzes epic descriptions to identify distinct workstreams and assign them to appropriate repositories.
  • Sub-ticket Creation: Generates Linear sub-tickets with relevant titles, descriptions, and repo hints.
  • Mode Flexibility: Supports inferring repository ownership (Mode A) or creating tickets for pre-defined repositories (Mode B).
  • Use Case: When a new epic is created in Linear, this Skill can automatically generate a set of child tickets, each focused on a specific component or repository, ensuring all aspects of the epic are addressed.

Quick Start

Use the decompose-epic skill to create sub-tickets for the Linear epic OMN-2000.

Frequently Asked Questions about decompose-epic

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

FAQPage Schema
How do I break down a Linear epic into sub-tickets automatically?

To break down a Linear epic into sub-tickets automatically, use the decompose-epic Skill to analyze the epic description, infer distinct work areas, and generate child tickets assigned to specific repositories.

Can I pre-define which repositories receive sub-tickets when decomposing an epic?

Yes, you can pre-define which repositories receive sub-tickets when decomposing an epic by using Mode B, which creates tickets for explicitly assigned repositories instead of inferring ownership automatically.

What is the best way to automate project planning for new Linear epics?

The best way to automate project planning for new Linear epics is using the decompose-epic Skill to dissect large epic descriptions into manageable, actionable child tickets assigned to relevant repositories.

How does automated repository inference work for issue tracking?

Automated repository inference for issue tracking works by analyzing Linear epic details to identify distinct workstreams and assigning them to appropriate repositories during child ticket creation.

Do I need any dependencies to use decompose-epic for workflow automation?

No, you do not need any external dependencies to use decompose-epic for workflow automation, as the Skill operates independently using its internal scripts and references to generate Linear sub-tickets.

When should I not use automated epic decomposition for issue tracking?

You should not use automated epic decomposition for issue tracking when your project lacks clear epic descriptions or requires manual, highly customized sub-ticket structures that automated repository inference cannot accurately determine.