skills.rest
OntoLedgy
OntoLedgyOFFICIAL
Explore all skills by this author →
GitHub

epic-executor

Automate epic execution with dependency-aware scheduling across JIRA, Linear, and Azure DevOps.

Updated Aug 27, 2026
Search Tags:#git worktree#task delegation#delivery reporting#epic execution#dependency scheduling#parallel orchestration#tracker integration
One-click install
npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill epic-executor-ontoledgy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-executor
Source: https://github.com/OntoLedgy/ol_ai_context_library/tree/main/skills/epic-executor
Command: npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill epic-executor-ontoledgy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually executing large epics with dozens of dependent tickets is time-consuming, prone to human error, and difficult to coordinate across parallel workstreams, leading to missed dependencies, merge conflicts, and inconsistent status tracking.

Core Features & Use Cases

  • Tracker-Agnostic Discovery: Automatically finds all child stories and subtasks under an epic across JIRA, Linear, Azure DevOps, or local filesystem trackers.
  • Dependency-Aware Scheduling: Builds a dependency graph from tracker links and schedules tickets into conflict-free parallel waves using topological sorting.
  • End-to-End Orchestration: Delegates each ticket to task-executor for implementation, code review, and status updates, then rolls up results into a full epic delivery summary. Use Case: A product team with a 25-ticket feature epic can use this skill to automatically run parallel work in isolated git worktrees, handle blockers gracefully, and get a complete report of shipped, blocked, and skipped tickets without manual coordination.

Quick Start

Use the epic-executor skill to run the full delivery of epic TI-100 using the jira tracker with default parallelism settings.

Frequently Asked Questions about epic-executor

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

FAQPage Schema
How do I automate epic execution for JIRA or Linear tickets with dependencies?▼

Automate epic execution by automatically discovering child stories across JIRA, Linear, or Azure DevOps, building a dependency graph, and scheduling tickets into conflict-free parallel waves using topological sorting.

What is wave-based parallel scheduling for software epics?▼

Wave-based parallel scheduling is a method that uses topological sorting on a ticket dependency graph to execute independent tickets simultaneously across isolated git worktrees, maximizing parallelism while preventing conflicts.

Can I use git worktree to run parallel workstreams for a large feature epic?▼

Yes, you can use isolated git worktrees for parallel workstreams. The system delegates each ticket for implementation and code review, handling blockers gracefully and rolling up results into a delivery summary.

Does dependency-aware scheduling handle blocked tickets during epic orchestration?▼

Dependency-aware scheduling handles blockers gracefully during epic orchestration by identifying dependencies from tracker links, ensuring blocked tickets are skipped or delayed without halting the entire parallel execution wave.

What's the best way to track epic delivery status across multiple parallel workstreams?▼

Track epic delivery status across parallel workstreams by rolling up individual ticket results into a complete epic delivery summary report, which details all shipped, blocked, and skipped tickets without manual coordination.

Do I need a specific tracker to run dependency graph construction for epics?▼

No specific tracker is needed. Dependency graph construction is tracker-agnostic, supporting ticket discovery and link parsing from JIRA, Linear, Azure DevOps, or local filesystem trackers.

Related Skills

Explore More Software Engineering Skills→
levnikolaevichlevnikolaevich
534

ln-410-story-executor

Orchestrate end-to-end Story execution with task delegation and quality gates.

Community
Advanced
Clyra-AIClyra-AI
12

branches-clean

Delete non-main local and remote Git branches one-by-one with safety checks.

Official
Advanced
ed3daied3dai
5

executing-an-implementation-plan

Execute implementation plans phase-by-phase with subagent task dispatch and code review.

Official
Advanced
tmalcolm-0607tmalcolm-0607

mad-parallel

Orchestrate wave-based parallel feature implementation across isolated git worktrees.

Community
Advanced