orchestrating-parallel-tasks

Decompose epic requirements into independent subtasks for parallel agent execution.

1|Updated Jan 31, 2026

Search Tags:#workflow #planning #epics #orchestrate #parallelism #task-slicing

Ready to run

npx skills add https://github.com/yu-iskw/coding-agent-skills --skill orchestrating-parallel-tasks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrating-parallel-tasks
Source: https://github.com/yu-iskw/coding-agent-skills/tree/main/skills/orchestrating-parallel-tasks
Command: npx skills add https://github.com/yu-iskw/coding-agent-skills --skill orchestrating-parallel-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down epic-level requirements into independent subtasks that can be executed in parallel by multiple agents, reducing coordination overhead and delivery time.

Core Features & Use Cases

Vertical slicing across UI, API, and data layers to deliver end-to-end value.
Interface-first development to lock in contracts before implementation.
Mutual exclusivity enforcement to prevent conflicting edits and rework.
Clear sub-task definitions with acceptance criteria and MVP slices.
Validation and phased rollout to ensure alignment and quality.

Quick Start

Provide an epic-level goal and the involved teams; the system will generate non-overlapping sub-tasks ready for parallel execution.

Frequently Asked Questions about orchestrating-parallel-tasks

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

FAQPage Schema

How do I split epic requirements into parallel tasks for multiple agents?▼

To split epic requirements into parallel tasks, the system decomposes large cross-layer work into independent subtasks using vertical slicing and mutual exclusivity enforcement. This allows multiple agents to execute work concurrently without conflicting edits.

What is vertical slicing for parallel task orchestration across UI and API layers?▼

Vertical slicing for parallel task orchestration cuts across UI, API, data, and infra layers to deliver end-to-end value. It creates independent subtasks with interface-first contracts, ensuring multiple agents can build separate features without overlapping.

How do I prevent conflicting edits when executing parallel subtasks?▼

To prevent conflicting edits during parallel subtask execution, the system enforces mutual exclusivity and establishes interface-first contracts. This defined dependency graph locks in boundaries, eliminating rework from overlapping modifications.

Can I use this for large cross-layer tasks spanning UI, API, data, and infra?▼

Yes, this approach is specifically designed for large cross-layer tasks spanning UI, API, data, and infra. It reduces cycle time by generating non-overlapping subtasks with explicit acceptance criteria ready for parallel delivery.

What do I need to provide to generate non-overlapping subtasks for parallel delivery?▼

You need to provide an epic-level goal and the involved teams. The system then generates non-overlapping subtasks defined by a dependency graph, interface-first contracts, and MVP slices ready for parallel execution.

When should I avoid orchestrating parallel tasks for epic decomposition?▼

You should avoid orchestrating parallel tasks for epic decomposition when work cannot be sliced into mutually exclusive verticals. If subtasks require heavy sequential dependencies or lack clear interface contracts, parallel execution will cause integration conflicts.