arc-batch

Automates sequential batch arc runs across multiple plan files with crash recovery.

6|3|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/vinhnxv/rune-plugin --skill arc-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arc-batch
Source: https://github.com/vinhnxv/rune-plugin/tree/main/plugins/rune/skills/arc-batch
Command: npx skills add https://github.com/vinhnxv/rune-plugin --skill arc-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates running multiple arc plans in a controlled batch with crash recovery and progress tracking, reducing manual orchestration.

Core Features & Use Cases

  • Seamless batch orchestration of multiple /rune:arc plans using a Stop hook, enabling crash-safe, sequential execution.
  • Per-plan status tracking, progress summaries, and optional auto-merge handling across PRs.
  • Shard-aware ordering and plan-sorting support ( Phase 0 and Phase 1.5 ) to reduce merge conflicts.
  • Dry-run capability and explicit confirmation flow before execution.

Quick Start

Prepare your plan files and run /rune:arc-batch to process them in sequence.

Frequently Asked Questions about arc-batch

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

FAQPage Schema
How do I automate running multiple plan files sequentially in Claude Code?

Batch processing of plan files is automated using a Stop hook pattern in Claude Code to trigger sequential arcs. It initializes a batch state, guards against concurrent batches, and manages per-plan statuses for crash recovery.

What is a Stop hook pattern for multi-agent orchestration?

A Stop hook pattern for multi-agent orchestration triggers the next sequential task automatically upon completion of the previous one. In batch arc runs, it manages per-plan statuses and produces summaries for crash recovery.

How do I recover a batch processing workflow if Claude Code crashes mid-execution?

Crash recovery for batch workflows is managed through per-plan status tracking and progress summaries. The batch state guards against concurrent batches and allows sequential execution to resume safely after an interruption.

Can I reduce merge conflicts when batch processing multiple feature development plans?

Merge conflicts during batch processing are reduced using shard-aware ordering and plan-sorting support for Phase 0 and Phase 1.5. This sequencing minimizes overlapping changes when executing multiple feature development plans.

Does batch orchestration support a dry-run before executing multiple arcs?

Batch orchestration supports a dry-run capability with an explicit confirmation flow before execution. This allows you to verify the planned sequence and shard-aware ordering of arcs without applying changes.