batch-flow

Orchestrate sequential execution of multiple plans with context preservation and crash recovery.

4|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skaisser/blueprint --skill batch-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: batch-flow
Source: https://github.com/skaisser/blueprint/tree/main/skills/batch-flow
Command: npx skills add https://github.com/skaisser/blueprint --skill batch-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute multiple plans sequentially in a single session to avoid repetitive setup and context drift, enabling automated end-to-end plan pipelines.

Core Features & Use Cases

  • Sequential plan execution: runs plan N through M automatically using flow-auto-wt to keep each plan isolated.
  • Context management and crash recovery: preserves context across plans and recovers from interruptions without starting over.
  • Autonomous orchestration: makes all decisions without user prompts, mirroring flow-auto behavior but for multi-plan workflows.

Quick Start

Use the batch-flow skill to execute plans 2 through 6 sequentially in one session.

Frequently Asked Questions about batch-flow

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

FAQPage Schema
How do I execute multiple sequential plans in a single session without losing context?

Use an autonomous orchestration loop to execute sequential plans from N to M in a single session. This approach preserves context across plans and reduces repetitive manual setup, preventing context drift during automated end-to-end workflows.

What is the best way to automate multi-plan workflows autonomously?

Automate multi-plan workflows by applying an autonomous orchestration mechanism that makes all decisions without user prompts. It loops around isolated worktrees for each plan, ensuring sequential execution without manual intervention.

How does crash recovery work during sequential plan execution?

Crash recovery during sequential plan execution preserves the current context and allows the workflow to recover from interruptions without starting over. This ensures completed plans remain intact when resuming an automated pipeline.

Can I chain pull requests together when running multiple plans sequentially?

Yes, you can chain pull requests together when running multiple plans sequentially. The workflow implements per-plan PR-based merge chaining, ensuring each isolated plan contributes to a connected sequence of pull requests.

Does context compaction affect sequential plan isolation?

Context compaction does not break sequential plan isolation. The workflow maintains per-plan isolation using worktrees while compacting context between plans to manage memory and preserve the overall session state.

When should I avoid using an autonomous multi-plan execution loop?

You should avoid using an autonomous multi-plan execution loop if your workflow requires user prompts or manual decision-making between plans. This approach is designed specifically for fully autonomous workflows needing sequential execution without interruption.