What problem does it solve? Coordinating multi-ticket development on GitHub often breaks down: branches drift, PRs merge out of order, dependencies between tickets get lost, and agents merge code without authorization. This Skill defines a disciplined delivery workflow that keeps Issues, Projects, branches, and PRs consistent across a weekly release sprint. ## Core Features & Use Cases - Weekly release sprint model: One sprint maps to one semantic version and one release-x-y-z integration branch, with main protected so only release PRs can land. - Dependency-aware stacked PRs: Tickets with hard dependencies form ordered PR stacks (124 -> 123) pinned to immutable predecessor snapshots, while independent tickets target the release branch directly. - Merge authorization boundary: Agents implement, validate, and reach ready-to-merge state, but must stop and wait for explicit human approval before merging ticket PRs, landing stacks, or merging the release PR to main. - Use Case: A team runs a one-week sprint toward v0.2.0: the agent creates the release branch, opens Draft PRs for each Issue, stacks dependent tickets, rebases downstream PRs when predecessors change, and halts before each merge until the repository owner approves. ## Quick Start Use the github-delivery skill to plan this week's release sprint from our open GitHub Issues and create the release branch with Draft PRs for each ticket.
