ship-foreman

Automated build orchestration dispatches specialized builder agents to execute task manifests and enforces mandatory review checkpoints after every build round to prevent skipped steps. It standardizes the build process by running strict checks for wiring errors, orphaned components, and schema mismatches.

Preventing merge drift during automated build pipelines involves proactively merging upstream main branch changes at regular intervals, specifically every 3 build rounds. This automated drift prevention reduces merge conflicts and ensures the working branch stays synchronized before reaching the pull request stage.

Task manifest execution handles complex schema migrations and cross-domain seams by supporting model escalation for high-complexity work. Specialized builder agents are dispatched to manage these difficult tasks, ensuring cross-layer plumbing validation and compliance checking are maintained.

You cannot skip UI auditing, quality reviews, or context mapper checks during the build orchestration process. The system enforces a strict no-skip policy for any mandatory review checkpoint, ensuring all wiring verification and compliance checks pass before code reaches review.

Automated build orchestration prevents repeating past bug patterns by checking an internal knowledge base for high-severity lessons during the build process. This proactive bug prevention mechanism identifies historical issues and applies those lessons to stop similar deviations before code reaches a pull request.

You need to provide the path to your task manifest file and the path to your worktree directory to start build pipeline automation. These inputs allow the system to execute tasks, dispatch builder agents, and enforce review checkpoints within your engineering workflow.