What problem does it solve?
APED sprint dispatch coordinates parallel story execution so teams can start multiple feature branches at once without breaking ordering, dependencies, or workflow ownership.
Core Features & Use Cases
- Parallel sprint dispatch orchestration: starts multiple story worktrees under a fixed sprint umbrella branch and queues the correct first prompt for each story leader.
- Robust state-driven planning: validates state integrity, computes dependency buckets (ready/blocked), checks capacity, and enforces “exactly one active epic” at a time.
- Ticket-system aware pre-checks and post-dispatch sync: performs read-only ticket validation before dispatch, then assigns and transitions ticket statuses after worktrees exist.
Quick Start
Use aped-sprint when you want to run an APED “parallel sprint” and dispatch ready stories for the currently selected epic into separate worktrees.