batch

Orchestrate epic story batches with gate enforcement and topological ordering.

Updated Apr 7, 2026

Search Tags:#automation #workflow #orchestration #ci-cd #batch #epic #gate-keeper

Ready to run

npx skills add https://github.com/ramontramontini/CTEDemo --skill batch-ramontramontini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: batch
Source: https://github.com/ramontramontini/CTEDemo/tree/main/.claude/skills/batch
Command: npx skills add https://github.com/ramontramontini/CTEDemo --skill batch-ramontramontini

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Batch-mode orchestration of epic stories with enforced quality gates and dependency ordering, accelerating downstream delivery and ensuring upstream ceremony is completed before work proceeds.

Core Features & Use Cases

Topological execution order derived from story dependencies to prevent conflicts and ensure deterministic runs.
Inline upstream ceremony for skeleton (specifying) stories via /spec when needed, with status re-queries to confirm readiness.
Gate-driven lifecycle including batch-scoped signaling and per-story transitions from planned to done, including resumption after failures.

Quick Start

Run /batch EPICNAME to execute all stories in the epic and use --resume STORYID to continue after a failure.

Frequently Asked Questions about batch

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

FAQPage Schema

How do I automate epic story orchestration with dependency ordering and quality gates?▼

Epic story orchestration automation applies batch-mode execution with deterministic topological ordering derived from story dependencies, enforcing quality gates to prevent conflicts and accelerate downstream delivery.

What is the best way to run a batch of epic stories with upstream ceremony enforcement?▼

Executing a batch of epic stories with upstream ceremony enforcement requires triggering batch-mode execution on stories with specifying or ready_to_pull statuses, applying inline /spec commands and status re-queries to confirm readiness before proceeding.

Can I resume a batch orchestration workflow after a specific story execution failure?▼

Yes, you can resume a batch orchestration workflow after a specific story execution failure by using the --resume flag with the specific STORYID to continue the deterministic topological execution from the point of failure.

Do I need hub-client API access to enforce gate-keeper conventions in CI-CD batch execution?▼

Yes, hub-client API access is required to enforce gate-keeper conventions in CI-CD batch execution, as it coordinates upstream and downstream gates to manage planning, execution, and completion transitions.

How does topological execution order prevent conflicts during automated epic story batching?▼

Topological execution order prevents conflicts during automated epic story batching by deriving a deterministic sequence from story dependencies, ensuring upstream tasks complete before downstream work begins.

What are the limitations of batch-running epic stories with inline upstream ceremony?▼

Batch-running epic stories with inline upstream ceremony is limited to stories with specifying or ready_to_pull statuses and depends on strict upstream/downstream gate conventions to successfully transition stories from planned to done.