execute-batch

Executes a batch of stories from an implementation strategy with atomic per-story finalisation and failure recovery.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a group of planned stories one by one in a fresh session risks losing progress mid-batch, leaving stories half-flipped between statuses, and exhausting context before the batch finishes. This Skill runs one chat (batch) from an Implementation Strategy end to end with atomic per-story finalisation, a context-budget guard, and a clean failure-recovery contract. ## Core Features & Use Cases - Sequential story loop: Composes execute-story, run-testplan, and close-out-story for each story in the chat, respecting lane ordering and DoR/DoD gates. - Atomic finalisation and recovery: Each story commits and flips to done before the next starts; on abort, completed stories stay done, the in-flight story is marked blocked, and remaining stories stay ready. - Context-budget guard: Aborts cleanly before starting a story that would push context utilisation above roughly 80 percent, so the batch can resume in a new session. - Use Case: After running /tandem:execution-strategist, invoke /tandem:execute-batch CHAT-01 to implement, test, and close every ready story in that chat, then flip the chat's executed flag and regenerate the dashboard. ## Quick Start Ask the assistant to run /tandem:execute-batch with a chat id such as CHAT-01 from the latest execution strategy.

Frequently Asked Questions about execute-batch

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

FAQPage Schema
How do I execute a batch of stories from an implementation strategy?

Invoke /tandem:execute-batch with a chat id such as CHAT-01. The skill loads the latest EXECUTION-STRATEGY JSON, runs each ready story through execute-story, run-testplan, and close-out-story in sequence, and marks the chat executed when all stories reach done.

What happens if a batch execution fails partway through?

Completed stories stay done because each finalised atomically with a commit. The in-flight story is flipped to blocked with an explanatory note, remaining stories stay ready, and the summary reports what to resume in a new session.

Can execute-batch run stories that are not marked ready?

No. A mandatory DoR precheck stops the run if any story in the chat has ready set to false. You must run /tandem:refine-backlog on those stories first, or explicitly drop them from the run.

Does execute-batch run stories in parallel?

No. Parallel lanes are executed sequentially, one story at a time, which also keeps the WIP limit of one in-progress story. Concurrent fan-out is tracked as a separate backlog item and is out of scope.

How does execute-batch avoid running out of context mid-batch?

Before each story it estimates remaining context and aborts cleanly if the next story would push utilisation above roughly 80 percent. Completed stories are already committed and done, so the batch resumes safely in a fresh chat.