execute-batch-parallel

Executes independent stories concurrently via scoped sub-agents with single-writer board reconciliation.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill execute-batch-parallel-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-batch-parallel
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/execute-batch-parallel
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill execute-batch-parallel-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a batch of independent stories one at a time is slow, but naive parallel execution risks corrupted shared state, colliding ADR/BUG numbers, and half-flipped story statuses. This Skill fans out one scoped sub-agent per Ready story in parallel, then reconciles all results on the main thread in a single serialized pass, so a batch of independent stories clears in one chat without breaking the board's gate contract. ## Core Features & Use Cases - Safety gate before fan-out: Verifies every story is DoR-ready and runs a static batch-check proving the batch is file-disjoint; any conflict, unknown, or script error falls back to serial execute-batch. - Scoped parallel sub-agents: Each sub-agent owns exactly one story and its testplan, is forbidden from touching MONITOR.md/ACTIVE.md, and returns a structured handoff instead of writing shared state. - Single-writer reconciliation: The main thread assigns sequential ADR/BUG numbers at write time, runs the per-story DoD gate, applies atomic status flips, writes the board once, and commits per story. - Honest partial-failure handling: Failed or crashed sub-agents leave their stories recoverable as in-progress or blocked, while succeeded stories still ship, with a shipped-vs-not report. - Use Case: Given CHAT-02 in an execution strategy with four file-disjoint Ready stories, invoke the command to implement and test all four concurrently, then fold results onto the board in one pass. ## Quick Start Run /tandem:execute-batch-parallel with a chat id such as CHAT-02 to execute that chat's Ready stories concurrently and reconcile the board.

Frequently Asked Questions about execute-batch-parallel

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

FAQPage Schema
How do I run multiple stories in parallel with Claude Code?

Invoke /tandem:execute-batch-parallel with a chat id like CHAT-02. The skill verifies every story is DoR-ready and file-disjoint, then dispatches one scoped sub-agent per story concurrently and reconciles all results on the main thread in one serialized pass.

What is the difference between execute-batch and execute-batch-parallel?

execute-batch runs a chat's stories one at a time serially, while execute-batch-parallel fans out one sub-agent per story concurrently. Parallel mode is opt-in and only runs when the batch is provably file-disjoint; otherwise it falls back to the serial execute-batch.

When does parallel story execution get refused?

Fan-out is refused if any story fails the DoR precheck or if the batch-check finds a file conflict, an unknown overlap, or exits non-zero for any reason. The gate fails closed, so an unprovable batch is treated as unsafe and runs serially instead.

Can sub-agents update the project board or create ADRs?

No. Sub-agents are forbidden from reading or writing MONITOR.md and ACTIVE.md, and cannot create or number ADR/BUG files. They return structured handoffs with proposed ADR/BUG bodies, and the main thread assigns sequential numbers and writes the board once.

What happens if one parallel sub-agent fails or crashes?

A failed or crashed sub-agent's story is flipped to in-progress or blocked and left recoverable, with its proposed BUG filed by the main thread. Succeeded stories still finalize to done and commit, and the run reports which stories shipped versus which did not.

Does parallel execution raise the work-in-progress limit?

No. The SOP WIP limit of two in-progress stories is preserved unchanged. Fan-out consumes zero WIP slots because sub-agents never flip board status; stories stay ready until the serialized reconciliation flips them one at a time.