Auto-Play: execute an entire Epic overnight
An Epic with 12 child tickets used to mean 12 separate execution cycles. Open ticket, write prompt, execute, review diff, approve, create PR. Repeat. For each one.
Auto-Play changes the math.
How Auto-Play works
- Open the parent Epic or Story
- Click Auto-Play in the execution panel
- JuhJuh queues all child tickets ordered by priority
- Each ticket executes sequentially in its own isolated worktree
- Context from completed tickets passes to the next in the queue
The key difference: sibling context. When ticket #5 executes, it knows what tickets #1 through #4 changed. File modifications, naming conventions, and architectural decisions all feed into the next prompt.
When to use Auto-Play
Auto-Play works best when child tickets are related but independent. A refactoring Epic that touches 10 modules. A feature that requires changes across frontend, backend, and shared libraries. A batch of similar tickets that follow the same pattern.
It works less well for tickets with complex dependencies where the order of execution matters beyond simple priority. In those cases, execute tickets individually and use the diff review step to verify each change before moving on.
Monitoring and control
Auto-Play is not fire-and-forget. The dashboard shows real-time progress for every ticket in the queue. You can pause the queue at any point to review completed work before continuing. If a ticket fails, Auto-Play stops and waits for your input.
The overnight workflow
Start Auto-Play before you leave for the day. JuhJuh processes each child ticket sequentially, building context as it goes. By morning, your Kanban board shows a column of tickets with PRs ready for review. Your team's first task of the day: code review, not code writing.
That is the juju.
See this in action.
The features described in this post are live in JuhJuh. Get started and explore the pipeline yourself.
Get started