parallel-task

Parse development plans and execute tasks across subagents in dependency-driven waves.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/samixisme/client-dashboard --skill parallel-task-samixisme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-task
Source: https://github.com/samixisme/client-dashboard/tree/main/.agents/skills/parallel-task
Command: npx skills add https://github.com/samixisme/client-dashboard --skill parallel-task-samixisme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and coordinates execution of tasks across multiple subagents by parsing a plan, resolving dependencies, and orchestrating wave-based launches to ensure correct ordering and traceable progress.

Core Features & Use Cases

  • Parse and interpret development plans to drive task execution.
  • Launch parallel subagents in waves while respecting task dependencies.
  • Update plan documents with execution logs after each completed task.

Quick Start

Provide a plan file path and optional task subset; the orchestrator will begin executing tasks in waves.

Frequently Asked Questions about parallel-task

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

FAQPage Schema
How do I orchestrate parallel subagents to execute a development plan?

You orchestrate parallel subagents by parsing a development plan, resolving task dependencies, and launching waves of subagents to execute tasks in the correct order with traceable progress logging.

What is wave-based task execution for development plans?

Wave-based task execution is a coordination method that launches parallel subagents in sequential groups, ensuring tasks within each wave run concurrently while respecting dependency-driven ordering across waves.

How do I resolve task dependencies before running parallel automation?

You resolve task dependencies by parsing the plan document to identify prerequisite relationships, then grouping tasks into waves so that dependent tasks only execute after their dependencies complete.

Can I run a subset of tasks from a parsed plan file?

Yes, you can provide a plan file path along with an optional task subset, and the orchestrator will execute only those specified tasks while still respecting dependency-driven wave ordering.

What is the best way to ensure traceability during parallel task execution?

The best way to ensure traceability is to update plan documents with execution logs after each completed task, providing atomic commits and explicit logging for every subagent action.

Why does my orchestrated task execution fail when dependencies overlap across waves?

Orchestrated task execution fails when dependency resolution is incomplete, so the orchestrator must strictly parse plan dependencies to guarantee that no wave launches tasks before their prerequisites are fully committed.