csdlc-shipit

To autonomously ship an epic, you can use a workflow that coordinates sub-agent work, builds a dependency graph, and automates PR merges. This process groups stories into batches for execution, review, and integration testing to minimize manual handoffs.

Automated PR merging during epic execution works by merging completed pull requests after verifying successful builds. The workflow resolves conflicts, runs post-merge QA, and generates a handoff to your knowledge layer environment to ensure integration stability.

The best way to manage dependencies for a multi-story epic is by building a dependency graph. This identifies foundation, parallel, and serial stories, allowing you to group work into controlled batches and dispatch them to sub-agents for isolated execution.

Yes, autonomous epic execution provides abort safeguards when failures exceed defined thresholds. If post-merge QA or build verifications fail repeatedly, the workflow halts to prevent broken code from merging into the main branch.

To start autonomous epic delivery, provide the path to your epic design document within your Foundry environment. Running the workflow initiates the process, analyzing the document to detect foundations and dispatch work to sub-agents.

Yes, you can use sub-agent orchestration for batch-based execution and integration testing. The workflow dispatches isolated stories to sub-agents in controlled batches, verifying successful builds before merging to ensure all dependencies integrate correctly.