landing-plan

Installation
SKILL.md

Landing plan

Landing is part of how fast work ships, and it is usually the slowest part nobody measures. Merging one PR at a time with a full CI cycle per PR pays for every flake serially. Most PRs in a set don't depend on each other. Check them all in parallel, batch the independent ones through the merge queue, and keep strict ordering only for PRs that actually depend on each other. At L2 the hand-off has to include the merge plan, not just a list of PRs.

When to use / not use

Use it:

  • when a stack or set of PRs (usually 3 or more) is ready for its owners or for gated self-merge;
  • when experiment-arms has a composed stack of winners;
  • when someone is about to merge a set of PRs serially.

Don't use it:

  • for a single PR. Use pr-shepherd.
  • for PRs that aren't green on their exact head yet. Finish those first.
  • to merge anything above the level granted in docs/autonomy.md. This skill plans at any level and acts only at the level it has been granted.

Steps

Installs
5
Repository
github/lever
GitHub Stars
279
First Seen
13 days ago