What problem does it solve? Large implementation changes are hard to review as one pull request, yet splitting them naively creates broken intermediate states, lost tests, and merge chaos. This Skill decides whether planned vertical work should ship as independent PRs or as an ordered stack, then governs building, reviewing, rebasing, and merging that stack safely. ## Core Features & Use Cases - Stack vs. independent PR decision: Applies explicit gates and two counterfactual tests (trunk and flow lineage) to choose the right delivery topology and records the decision in one sentence. - Stack design and delivery plan: Draws the lineage graph, routes verification by boundary type, checks CI topology (native GitHub stacks vs. unlinked chains, merge queues, merge_group), and produces a Delivery Shape table with a whole-stack gate checklist. - Bottom-up build, review, and merge: Builds each boundary from a known-good parent, keeps fixes in the owning lower branch with cascading rebases, and merges via gh stack merge or manual bottom-up order. - Use Case: A sign-in feature spanning a dormant migration, a repository adapter, and the credential path is too large for one review. The Skill splits it into a three-PR stack where each layer is verified, deployable or dormant, and merged in dependency order. ## Quick Start Ask the assistant to use the stack-pull-requests skill to decide whether your planned implementation slices should ship as independent PRs or a stacked sequence, and to produce the delivery plan.
