Multitask Parallel Developer FAQs

Question 1

How does this skill prevent file conflicts during parallel work?

Accepted Answer

Each task runs in a completely separate clone of the repository within the /tmp directory, ensuring that concurrent workstreams never interfere with each other's file systems.

Question 2

What is the advantage of using Recipe Runner over standard prompts?

Accepted Answer

Recipe Runner uses Python-controlled YAML workflows that enforce strict step ordering. This makes it impossible for the agent to skip mandatory steps like testing, linting, or documentation.

Question 3

How do I monitor the progress of multiple tasks?

Accepted Answer

You can watch real-time logs for individual tasks in /tmp/amplihack-workstreams/ or check the final REPORT.md for a summary of all PR numbers and success statuses.

Question 4

Does this skill consume a lot of disk space?

Accepted Answer

Each workstream requires a full git clone (typically ~1.5GB). The skill includes a built-in disk monitor that warns you before launching tasks if space is low and provides cleanup helpers.

Question 5

Can I use custom workflows for different tasks?

Accepted Answer

Yes, you can specify different recipes (like investigation, verification, or auto-workflow) for each task within a JSON configuration file.

Multitask Parallel Developer

Key Features

Use Cases

Multitask Parallel Developer

Key Features

Use Cases