Execute plan files by launching multiple parallel subagents to complete tasks simultaneously. Triggers on explicit "/parallel-task" commands.
59
68%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/parallel-task/SKILL.mdThe canonical home for this skill is parallel-task in jdrhyne/agent-skills
Use Orchestration Mode. Parse plan files and delegate tasks to parallel subagents.
Extract from user request:
If sprint not provided, ask user which to run.
## Sprint 1:)### Task 1.1:)For each task, launch subagent with:
If there are multiple unblocked tasks, launch multiple subagents in parallel.
You are implementing a specific task from a development plan.
## Context
- Plan: [filename] - [sprint/phase]
- Goals: [relevant overview from plan]
- Dependencies: [prerequisites for this task]
- Related tasks: [tasks in same sprint]
- Constraints: [risks from plan]
## Your Task
**Task [ID]: [Name]**
Location: [File paths]
Description: [Full description]
Acceptance Criteria:
[List from plan]
Validation:
[Tests or verification from plan]
## Instructions
1. Examine and explore the plan, all relevant files & dependencies. Ensure ambiguities are cleared up.
2. Implement changes for all acceptance criteria
3. Keep work **atomic and committable**
4. For each file: read first, edit carefully, preserve formatting
5. Run validation if feasible
6. Return summary of:
- Files modified/created
- Changes made
- How criteria are satisfied
- Validation performed or deferred
## Important
- Be careful with paths
- Stop and describe blockers if encountered
- Focus on this specific taskAfter subagents complete:
Now, pause and read the whole plan again to see what new tasks are unblocked.
Start back at step 3. Continue launching agents on unblocked tasks in parallel.
Repeat this loop until the plan is done.
Do not stop until the plan is fully completed or you encounter a blocker.
After completing all tasks, validate the plan's success by checking the final state against the original plan. Perform available tests and ensure success. If there are any issues, address them before marking the plan as complete.
After validation, provide a summary of:
/parallel-task plan.md
/parallel-task ./plans/auth-plan.md sprint 2
/parallel-task user-profile-plan.md phase 1# Sprint/Phase Execution Summary
## Tasks Assigned: [N]
### Completed
- Task [ID]: [Name] - [Brief summary]
### Issues
- Task [ID]: [Name]
- Issue: [What went wrong]
- Resolution: [How resolved or what's needed]
### Blocked
- Task [ID]: [Name]
- Blocker: [What's preventing completion]
- Next Steps: [What needs to happen]
## Overall Status
[Completion summary]
## Files Modified
[List of changed files]
## Next Steps
[Recommendations]f4ed46f
Canonical home
since Jan 29, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.