ship-issue

You automate the Linear issue shipping pipeline by enforcing a structured workflow of planning, decorrelated code review, and gated deployment. This ensures consistent branch management, rigorous TDD, and automated verification of acceptance criteria.

Decorrelated code review is an isolated evaluation step preventing bias by separating implementation from review. You need it for software engineering tasks requiring rigorous cross-review, scope hygiene, and strict safety gates before deployment.

You enforce mandatory TDD and safety gates by applying a gate-controlled pipeline with explicit PLAN and SHIP checkpoints. This prevents unauthorized code changes and requires user sign-off before proceeding to automated verification and deployment.

Yes, you can use this automated pipeline without configuring external dependencies. It orchestrates the end-to-end development lifecycle natively, requiring only a Linear issue ID to initiate the structured planning, review, and deployment flow.

The best way to manage branch lifecycle and scope hygiene is through an orchestrated pipeline enforcing strict safety gates. This approach guarantees every Linear issue satisfies consistent branch management and mandatory post-ship retrospectives.

You need a post-ship retrospective in an automated deployment workflow to satisfy requirements for continuous improvement after gated deployment. It ensures every shipped Linear issue undergoes mandatory review, closing the end-to-end development lifecycle loop.