project

To automate batch ticket workflows, you provide a batch of ticket descriptions or IDs to start the orchestration, which then plans, executes, and validates each ticket autonomously using a shared project branch and per-ticket topic branches.

The branching strategy for coordinated project orchestration uses a single shared project branch as the integration point, with individual topic branches created and merged for each specific ticket within the batch.

You apply quality assurance passes by running cross-cutting workflows like /refactor and /doc-review after all batch tickets are implemented and merged, ensuring code quality before final human review.

Yes, autonomous execution runs the /iterate workflow for each ticket with pre-loaded requirements, automating commits and reporting progress without requiring manual intervention during the implementation phase.

The best way to manage a sprint-like scenario with multiple tickets is using a coordinated orchestration workflow that plans the project, executes tickets autonomously on topic branches, and validates merges against a shared project branch.

No, the workflow performs post-merge verification automatically, producing a comprehensive summary and branch state for human decision-making on the final integration.