Decompose large initiatives into dependency-aware tickets with acceptance criteria.
npx skills add https://github.com/nexus-a1/claude-skills --skill epic-nexus-a1
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
Break down multi-faceted initiatives into manageable, dependency-aware tickets to enable phased delivery and risk management.
Invoke /epic with your description to start breaking down a large initiative into tickets.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
epieczkoGenerate structured Agile Epic Markdown documents from initiative details.
OmexITConvert PRD or design docs into epics, tickets, and acceptance criteria.
7a336e6eDecompose system architecture into atomic work packages with agent assignments and dependency graphs.
am-willOrchestrate parallel subagents to execute development plan tasks in waves.
