harness-batch

Runs a fixed task list through a 7-stage pipeline sequentially with isolated contexts.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Alan-IFT/harness-kit --skill harness-batch-alan-ift
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-batch
Source: https://github.com/Alan-IFT/harness-kit/tree/main/skills/harness-batch
Command: npx skills add https://github.com/Alan-IFT/harness-kit --skill harness-batch-alan-ift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a decomposed plan or backlog of many tasks one-by-one through a full development pipeline requires repeatedly invoking the pipeline manually, which is tedious and error-prone. This Skill automates sequential batch execution of tasks T-01 through T-NN, each in its own isolated sub-agent context, stopping only on strong failure signals. ## Core Features & Use Cases - Sequential batch orchestration: Parses a BATCH_PLAN.md task table, validates dependencies and schema, builds a topological order, and dispatches each task to a pm-orchestrator sub-agent. - Strong-signal stop conditions: Halts the batch on verify_all FAIL, a FAILED verdict, a STOP intervention, or a safety-hook block, and never auto-retries failed tasks. - Idempotent resume: Re-invoking with the same batch-id skips tasks already marked done or whose delivery doc shows a DELIVERED verdict. - Use Case: After a /harness-plan decomposition produces eight tasks, run the batch once and receive a BATCH_REPORT.md with per-task verdicts, aggregate stats, and the stop reason if any. ## Quick Start Run the batch for batch-id sprint-12 by invoking /harness-batch sprint-12 after creating docs/batches/sprint-12/BATCH_PLAN.md with your task table.

Frequently Asked Questions about harness-batch

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

FAQPage Schema
How do I run multiple tasks through a development pipeline automatically?▼

Create a BATCH_PLAN.md under docs/batches/<batch-id>/ with a task table (ID, Slug, Goal, Mode, Depends on, Status), then invoke the batch with that batch-id. Each task runs sequentially in its own sub-agent context through the full pipeline.

What is the difference between harness-batch and harness-stream?▼

harness-batch runs a frozen, fixed task list and rejects mid-run additions, while harness-stream keeps a living pool you can keep adding tasks to during the run. Use batch for known backlogs and stream for evolving work.

Can I resume a batch after it stops on a failure?▼

Yes, re-invoking with the same batch-id is idempotent. Tasks marked done or whose 07_DELIVERY.md shows a DELIVERED verdict are skipped, and remaining pending or failed tasks are re-evaluated and run.

When should I not use batch task execution?▼

Do not use it for a single task (use the full pipeline directly), for iterating toward a measurable goal, for design vetting, or for research questions. The batch wrapper adds overhead without value in those cases.

Why does the batch refuse to start sometimes?▼

The batch refuses to start if the baseline verify_all already returns FAIL, since per-task regression detection becomes impossible on a broken baseline. It also stops on schema drift, dependency cycles, or a STOP intervention file.