orchestrator-submit-future

Batch-submitting future chunks to an orchestrator requires validating git status first to prevent uncommitted changes, then querying the orchestrator to avoid duplicate work before pushing committed chunks in one batch.

Chunk submission fails with uncommitted changes because the skill enforces git status checks to prevent partial deployments, ensuring only committed future chunks are pushed to the orchestrator.

To check if chunks are already running, query the orchestrator directly before injection to cross-check status, ensuring you avoid duplicate work and conflicting tasks during batch submission.

The best way to avoid duplicate work is cross-checking committed future chunks against the orchestrator's running tasks before submission, skipping chunks that already exist to support audits and rollback decisions.

You cannot submit future chunks without committing them first, as the skill guards against uncommitted changes by enforcing git status checks to ensure only committed chunks reach the orchestrator.

Skipped chunks during batch submission generate a clear summary report showing which chunks were submitted and which were skipped, supporting audits and rollback decisions for ongoing work visibility.