stacked-delivery
Installation
SKILL.md
Stacked Delivery
Some queues cannot merge independently — each change depends on the last — so they ship as one stacked chain: PR 2 branches on PR 1, PR 3 on PR 2. The chain makes review sequential and landing strictly bottom-up; this skill keeps that honest.
When to use
- changes depend on each other and the user chose stacking over independent PRs
- review gating means only the bottom PR can actually merge at a time
When not to use
- changes are independent — parallel PRs merge faster and fail smaller
- the user wants everything in one PR — that is
executewith a bigger brief