This handles the mechanics of creating dependent pull requests where each PR builds on the previous one, not main. It's overkill for most work, but when you're shipping a complex feature that needs logical separation and parallel review, the numbered branch convention (feature/001-base, feature/002-next) keeps things clear. The real value is in the rebase chain management and PR description templates that explain dependencies. The skill defaults to regular main-based PRs unless you explicitly ask for stacking, which is the right call since stacked PRs require comfort with rebasing and force-pushing. If your team doesn't already do this workflow, the learning curve probably isn't worth it for a one-off feature.
npx skills add https://github.com/bobmatnyc/claude-mpm-skills --skill stacked-prs