Orchestrate epic story batches with gate enforcement and topological ordering.
npx skills add https://github.com/ramontramontini/CTEDemo --skill batch-ramontramontini
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
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.
Run /batch EPICNAME to execute all stories in the epic and use --resume STORYID to continue after a failure.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
patricio0312revConfigure Pinecone, Chroma, pgvector, and Qdrant vector databases for semantic search.
atxinskyExecute plan files in sequential batches with per-batch verification and human feedback between runs.
smykla-skalskiCoordinate multi-agent orchestration sessions by delegating tasks to worker agents.
barkleesandersGenerate dependency-ordered user stories and enforce quality gates during autonomous feature builds.
