ln-1000-pipeline-orchestrator

Automating your git workflow from a kanban board to merge involves orchestrating a multi-stage pipeline that manages task creation, validation, execution, and quality gating using AI agent teams. This Skill processes software Stories through planning, validation, execution, and quality gate stages, ultimately squash-merging completed stories to the develop branch after passing automated checks.

Processing multiple kanban stories in parallel is supported to speed up developer productivity. The pipeline orchestrator drives up to 3 Stories concurrently using dedicated workers, enabling parallel task execution and dependency management while maintaining automated quality gating before merging.

Setting up end-to-end pipeline orchestration for software stories requires managing a 4-stage pipeline: planning, validation, execution, and quality gate. You can trigger the orchestrator to process all stories currently in the backlog, automatically creating tasks, executing code, running checks, and merging successful items.

Automated pipeline orchestration handles git operations like squash-merging. After a Story passes the quality gate checks, the orchestrator automatically squash-merges the completed work to the `develop` branch, reducing manual intervention and ensuring consistent integration.

You should not use an automated dev workflow orchestrator for stories requiring complex problem-solving or manual architectural decisions outside standard task execution. The pipeline is designed for automating routine task creation, validation, and code execution, freeing developers to focus on complex problem-solving rather than manual pipeline management.