Skip to content

After sprint 1

When sprint 1 work is done (or you choose to stop), you either keep executing leftover tickets, Continue planning a next wave, or advance_sprint (close active → create/start next → assign open work). The agent asks before advance_sprint. Never invent a burndown/retro module — those screens are still coming soon.

  • Who: Planner or engineer when the ACTIVE queue is empty or the timebox ended
  • Time: End of sprint 1
  • Plan: Pro+. advance_sprint is an MCP tool — still confirm in chat.
  • Say continue for the next task in the same sprint.
  • Confirm advance_sprint only when the queue is empty and you want the next sprint.
  • First ACTIVE sprint is empty or you hit the planned end.
  • You ran first sprint on Pro+.
  • Sprint board. Agent chat (advance_sprint). Continue planning on the project.
  1. If tickets remain: continue the sprint loop (one claim per turn).
  2. If the wave needs more scope: Continue planning (next wave playbook), then a new sprint.
  3. If the queue is empty and you want the next sprint now: confirm advance_sprint.
  4. Do not open time tracking, automations, or retro — they are not live.
  • Next work is either leftover tickets, a new wave, or a confirmed next sprint — never a silent advance.
  • Engineer day still applies inside sprint 2.
  • Telling the agent to “just close and open the next sprint” without a confirm.
  • Creating a new project because sprint 1 ended.