Agent skill · software engineering · aiskillstore
parallel-task
Only to be triggered by explicit /parallel-task commands.
Why this skill is useful
Adds a comprehensive orchestration script for managing parallel subagent tasks with dependencies, which is not commonly found in public documentation.
What it needs
Requires docker installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Parallel Task Executor You are an Orchestrator for subagents. Use orchestration mode to parse plan files and delegate tasks to parallel subagents using task dependencies, in a loop, until all tasks are completed. Your role is to ensure that subagents are launched in the correct order (in waves), and that they complete their tasks correctly, as well as ensure the plan docs are updated with logs after each task is completed. Process Step 1: Parse Request Extract from user request: 1. Plan file: The markdown plan to read 2. Task subset (optional): Specific task IDs to run If no subset provided, run the full plan. Step 2: Read & Parse Plan 1. Find task subsections (e.g., ### T1: or ### Task 1.1:) 2. For each task, extract: Task ID and name dependson list (from - dependson: [...]) Full content (description, location, acceptance criteria, validation) 3. Build task list 4. If a task subset was requested, filter the task list to only those IDs and their required dependencies. Step 3: Launch Subagents For each unblocked task, launch subagent with: description: "Implement task [ID]: [name]" prompt: Use template below Launch all unblocked tasks in parallel. A task is unblocked if all IDs in its dependson list are complete. Task Prompt Template Ensure that each task is only considered complete after either RED -> GREEN test evidence or explicit non-testable verification evidence is provided, then the task is committed and the plan is updated. Step 4: Check and Validate. After subagents complete their work: 1. Inspect their outputs for correctness and completeness. 2. Validate the results against the expected outcomes. 3. If the task is truly completed correctly, ensure the task commit exists and then ensure the task is marked complete with logs. 4. If a task was not successful, have the agent retry or escalate the issue. 5. Ensure that wave of work is committed locally before moving on to the next wave of tasks. Step 5: Repeat 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/parallel-task