Skip to content

cedricfarinazzo/agile-sprint-drain

v0.21.2MIT

Alternate implementation and merge workflows until an active sprint is drained or blocked.

agile-sprint-drain

Runs the active sprint to the end in one watched session. It alternates the build queue (agile-10-implement) and the merge queue (agile-11-merge-train) until every ticket is Done and merged, or only human-blocked work is left.

Part of agile-skills. Needs the Atlassian MCP and gh, and both agile-execution and agile-merge-review installed.

What you get

SkillWhat it doesSay
agile-sprint-drainLoops build then merge, recomputed from the live board each pass, to a fixed point"drain the sprint", "run the sprint to completion", "implement and merge until done", "clear the whole board", "ship the sprint"
ArgumentDefaultEffect
concurrency=Nmax-build-concurrency, else 1WIP limit on the whole chain: tickets started but not merged, plus open PRs
dispatch=phase|sessionphasesession runs each pass in a build session and a fresh merge session (Dispatch modes)
max-merges=NunboundedStop as PAUSED after N merges; re-invoke to continue

A drain, pass by pass

Why it exists: a ticket blocked by another can be built only once the blocker is Done and its PR is merged. So each merge pass can unlock new build work, and someone has to alternate them.

Install

/plugin marketplace add cedricfarinazzo/agile-skills
/plugin install agile-execution@agile-skills
/plugin install agile-merge-review@agile-skills
/plugin install agile-sprint-drain@agile-skills
/reload-plugins

Run /agile-sprint-drain:agile-sprint-drain. On Codex, run $agile-sprint-drain; everything runs inline and every dispatch value is treated as inline.

How it ends

End stateMeaningYou
DRAINEDAll tickets Done and PRs merged, and the audit trail is complete. The only healthy stopRun agile-sprint-close
STUCKEvery remaining item needs a personWork the list it prints, then re-invoke
PAUSEDmax-merges reached with work leftRe-invoke to continue from the ledger

DRAINED and STUCK each send one push notification (PushNotification) at the top level. What STUCK reports and why a quiet pass is not a stop: States.

Configuration

KeyDefaultUse
session-batch1Max tickets per build-session under dispatch=session

Everything else is inherited from both orchestrators' ## Skill configuration in the repo's CLAUDE.md or AGENTS.md: cloudId, status names, base-branch, repo / repo-component-map, lint and test commands.

Run state lives in .git/agile-drain/ (context.md, ledger.md) and is never committed. For a long sprint, /loop /agile-sprint-drain max-merges=N runs each chunk in a fresh context.

It does not

  • Write Done, open PRs or merge. It sequences the two orchestrators, so every invariant they enforce holds.
  • Bypass their pauses. A parked critical decision parks that one ticket and the rest keep going.
  • Run agile-sprint-close. On DRAINED it hands off.

More

PageCovers
StatesThe loop, the actionable-work guard, DRAINED / STUCK / PAUSED
Dispatch modesphase vs session, the two session agents, the trade-off
ReferenceEligibility, merged signal, WIP limit, ledger, CI waits

agile-mods shows each drain pass, its cost and cache hit rate on a Drain tab.

Where it fits

Between agile-execution plus agile-merge-review, which it drives, and agile-sprint-close, which it hands off to. Full cycle: root README.