ln-1000-pipeline-orchestrator

Automating a story pipeline requires orchestrating task creation, validation, execution, and quality gating. This skill drives individual stories through four distinct processing stages using dedicated workers, managing state persistence via checkpoints and Git operations autonomously.

Kanban board integration for story processing reads and updates board status to track progress and identify available work. The automation reads backlog items, updates story stages through processing, and requires explicit user confirmation before merging completed code to the main branch.

Git rebasing and merging in an automated CI/CD workflow manages branch integration with user-confirmed merges. The pipeline orchestrator handles Git operations autonomously throughout the story lifecycle but escalates to the user for final merge approval to the development branch.

Handling crash recovery in pipeline orchestration systems utilizes state persistence via checkpoints. When processing fails, the system includes retry mechanisms and crash recovery protocols to resume story execution, escalating complex issues to the user when automated retries are exhausted.

Worker lifecycle management for story automation is required to drive tasks through distinct stages. The pipeline orchestrator manages dedicated workers for task creation, validation, execution, and quality gating, ensuring each story processes autonomously without manual intervention between stages.