epic

Name: epic
Availability: InStock
Author: nexus-a1

Decompose large initiatives into dependency-aware tickets with acceptance criteria.

Updated Mar 29, 2026

Search Tags:#planning #epic #parallel-work #dependency-graph #ticketing #wave-planning

Ready to run

npx skills add https://github.com/nexus-a1/claude-skills --skill epic-nexus-a1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: epic
Source: https://github.com/nexus-a1/claude-skills/tree/main/skills/epic
Command: npx skills add https://github.com/nexus-a1/claude-skills --skill epic-nexus-a1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down multi-faceted initiatives into manageable, dependency-aware tickets to enable phased delivery and risk management.

Core Features & Use Cases

Structured epic-to-ticket decomposition with explicit dependencies and waves.
Parallelizable work where possible, with clear sequencing across tickets.
Per-ticket specs and validation steps to guide implementation.

Quick Start

Invoke /epic with your description to start breaking down a large initiative into tickets.

Frequently Asked Questions about epic

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

FAQPage Schema

How do I break down a large initiative into executable tickets with dependencies?▼

To break down a large initiative into executable tickets, you decompose the work into structured tasks with explicit dependencies, wave sequencing, and per-ticket acceptance criteria. This creates a dependency graph distinguishing database, backend, and integration work.

What is wave planning for parallel work in ticketing?▼

Wave planning for parallel work is sequencing tickets into execution waves based on their dependency graph. It identifies parallelizable work across database, backend, and integration tasks to enable phased delivery and structured risk management.

How do I structure epic-to-ticket decomposition for phased delivery?▼

You structure epic-to-ticket decomposition by capturing epic-level context, constraints, and risks to guide ticket generation. Tickets are then grouped into executable waves with clear sequencing and per-ticket validation steps to ensure phased delivery.

Can I capture epic-level risks and constraints when generating tickets?▼

Yes, you can capture epic-level risks and constraints when generating tickets. The decomposition process uses this captured context to guide ticket generation, sequence the dependency graph, and distinguish between database, backend, and integration work.

Does ticket decomposition separate database, backend, and integration work?▼

Yes, ticket decomposition separates database, backend, and integration work. During epic-to-ticket decomposition, the scope explicitly distinguishes between these technical layers to structure parallelizable work and map dependencies accurately.

What are the limitations of manual epic decomposition without a dependency graph?▼

Manual epic decomposition without a dependency graph limits parallelizable work and obscures ticket sequencing. It risks missing critical constraints and per-ticket acceptance criteria needed to distinguish database, backend, and integration work for phased delivery.